5.1 Organisational & Project Ecosystems
Key Takeaways
- PRINCE2 7 elevates people to a core element of the method, recognising that projects succeed or fail through people, not just process.
- The organisational ecosystem is the existing set of organisational elements and the external relationships that influence how work gets done.
- The project ecosystem is the slice of the business involved in or impacted by the project, plus the users and suppliers who contribute or receive its outputs.
- The Organising practice's five-step ecosystem technique guides the project from understanding the organisation through designing, developing, managing and finally transitioning the ecosystem back into business-as-usual.
- Transition back at closure is not optional: the project ecosystem is deliberately dissolved so its relationships, resources and ways of working are absorbed into the organisational ecosystem.
Why people are a core element
Earlier versions of PRINCE2 were sometimes caricatured as a "process-only" method. PRINCE2 7 corrects that by making people one of the five integrated elements of the method (alongside principles, practices, processes and the project context). The reasoning is pragmatic: every process is operated by people, every decision is taken by people, and most project failures trace back to people issues long before they trace back to a missing template.
The element deliberately covers two populations:
- People working on the project — the Project Board, Project Manager, team members and suppliers who deliver the work.
- People affected by the project — users, operational staff, sponsors and other stakeholders who live with the outcomes whether or not they ever attended a project meeting.
Two ecosystems
PRINCE2 7 distinguishes two related ecosystems that the Project Manager needs to keep in view.
| Ecosystem | Definition | What it contains |
|---|---|---|
| Organisational ecosystem | The existing organisational elements and the external relationships that shape how the business operates | Leadership culture, reporting lines, shared services, regulators, partner organisations, legacy systems |
| Project ecosystem | The parts of the business involved in or impacted by the project, plus the users and suppliers | Project Board, team, user representatives, supplier teams, subject-matter experts, affected operational units |
A project does not float free of its organisation. Project success depends heavily on how well the project ecosystem fits the organisational ecosystem — a project that cuts across established reporting lines, incentives or cultural norms will meet resistance no matter how well its plans are written.
The five-step ecosystem technique
The Organising practice provides a five-step technique for working with ecosystems. You should be able to recognise each step in a scenario and, importantly, identify when a step is being skipped.
- Understand the organisational ecosystem. Before designing the project, map the existing organisation: who holds authority, where budgets sit, which external relationships matter, what the prevailing culture rewards. This is situational awareness, not project planning.
- Design the project ecosystem. Decide which parts of the organisation and which external parties need to be inside the project, in what roles, with what decision rights. This is where the project management team structure and stakeholder map take shape.
- Develop it. Bring the ecosystem to life — brief the people, build the relationships, establish ways of working. The ecosystem is not real until the people in it understand their part.
- Manage changes to it. Projects are dynamic: stakeholders leave, suppliers merge, scope shifts. The Project Manager actively maintains the ecosystem rather than treating the original design as fixed.
- Transition it back into the organisational ecosystem. At closure, the project ecosystem is deliberately dissolved. Its people, knowledge and ways of working are handed back to the organisation so that the deliverables can be operated and supported.
What "transition back" really means
The fifth step is the one candidates most often misread. Transition back is not simply "hand over the product." It is the re-absorption of the project's human relationships and ways of working into business-as-usual. If the project has created a strong cross-functional team, that team is disbanded and its members return to their permanent roles — but the working relationships and knowledge they built need to survive the dissolution. A project that closes without this step leaves operational teams struggling to adopt outputs they never felt part of.
Exam angle: A scenario that describes a Project Manager at closure handing over a product but ignoring the team disbandment, knowledge transfer or relationship re-absorption is illustrating a missing fifth step.
Ecosystem fit as a success criterion
A useful way to read ecosystem scenarios is to ask: does this project fit the organisation it sits in? A project that imports a fast-moving agile culture into a regulated, risk-averse environment will generate friction at every stage gate. A project that imports heavy governance into a small charity will suffocate delivery. Neither failure is a process failure — both are ecosystem fit failures, and the five-step technique exists precisely to surface them before they become stage failures.
The technique also cuts the other way: a strong project can improve the organisational ecosystem by introducing relationships, ways of working or tools that the organisation later adopts more widely. This is a legitimate outcome, but it only happens if step five is handled well — the new practice has to be transitioned deliberately rather than left to evaporate when the project closes.
Common exam traps
- Treating "design the project ecosystem" as a one-off org-chart exercise. It is not: step four (manage changes) exists because the design keeps moving.
- Confusing the project ecosystem with the project team. The ecosystem includes users, suppliers and affected operational units — people who are not on the team chart but whose support the project needs.
- Assuming "transition back" means deploying the product. Deployment is a product activity; transition is a people and relationship activity.
A Project Manager spends the first two weeks of a new engagement interviewing senior managers about reporting lines, cultural norms and key external partnerships before designing the project team structure. Which step of the ecosystem technique is this?
At project closure, the Project Manager hands the finished product to operations and disbands the team the same week. Operational staff report they do not understand how to support the product and the cross-functional relationships have evaporated. Which ecosystem step was missing?