7.2 Organising: 5-Step Ecosystem Technique
Key Takeaways
- PRINCE2 v7's Organising technique works through five steps that move from understanding the organisational ecosystem to transitioning the project ecosystem back at closure.
- The technique ties directly to the People element by distinguishing the permanent organisational ecosystem from the temporary project ecosystem created to deliver the work.
- Step 1 (understand) and Step 5 (transition back) are the bookends that connect the project to the wider organisation; Steps 2–4 design, develop, and manage the project ecosystem during delivery.
- The technique is iterative — changes to the project ecosystem during the project trigger a return to the design and develop steps rather than a one-off linear pass.
PRINCE2 v7 pairs the Organising practice with a five-step ecosystem technique that connects the project's accountability structure to the wider organisation. The technique is the bridge between the People element — which recognises that projects are delivered by people inside an organisational context — and the concrete roles, reporting lines, and support functions the project needs. It treats the organisation as a living organisational ecosystem (the permanent environment of departments, culture, reporting lines, and tools) and the project as a temporary project ecosystem created within it.
The Five Steps
| Step | Name | Purpose | Key Output |
|---|---|---|---|
| 1 | Understand the organisational ecosystem | Map the permanent environment the project sits in — culture, structures, existing projects, PMO, tools, and constraints | A shared picture of the organisational context |
| 2 | Design the project ecosystem | Decide what roles, reporting lines, collaboration tools, and decision forums the project needs, tailored to its scale and risk | The project's role map and collaboration model |
| 3 | Develop the project ecosystem | Build what was designed — appoint people to roles, set up tools, establish the Project Board and support functions | An operational project ecosystem with people in roles |
| 4 | Manage changes to the project ecosystem | Respond to people joining or leaving, restructures, new teams, or changing ways of working during the project | Updated role assignments and ways of working |
| 5 | Transition the project ecosystem back into the organisational ecosystem | At closure, hand over the products, disband the project roles, retain lessons, and return people to the permanent organisation or to new work | A clean closure with knowledge captured and people released |
Step 1 — Understand the Organisational Ecosystem
Before designing anything, the project must understand the environment it enters. This means looking at the culture, the existing project landscape, the PMO or support functions already in place, the tools the organisation uses, and any constraints (such as a mandated corporate method or a fixed supplier). Step 1 is where the PM and Executive gather context that will shape tailoring decisions later. Skipping this step is a common cause of a project ecosystem that fights the organisation — for example, introducing a collaboration tool the organisation will not adopt.
Step 2 — Design the Project Ecosystem
Designing the project ecosystem is where the role map from the Organising practice is tailored. A small, low-risk internal project may combine the Senior User and Senior Supplier roles and use a lightweight Project Support function from the corporate PMO. A large, high-risk programme may need multiple Senior Suppliers, a dedicated Project Assurance team, and a full Project Support office. The design step produces the role map and the collaboration model — who meets whom, when, and through which reports.
Step 3 — Develop the Project Ecosystem
Developing means putting the design into effect: appointing named individuals to each role, standing up the Project Board, configuring the tools, and establishing the reporting cadence. This is where the ecosystem becomes operational. The People element is explicit here: the technique recognises that putting a person into a role is not enough — they need induction into the project's ways of working and clarity on the boundaries of their role.
Step 4 — Manage Changes to the Project Ecosystem
Projects rarely keep the same people throughout. A Senior Supplier may leave, a team may be restructured, or a new regulatory requirement may force a new assurance role. Step 4 treats the ecosystem as something that must be actively managed. When a change occurs, the PM returns to the design step to decide whether the existing structure still works, then updates role assignments and ways of working. The technique is therefore iterative, not a one-off linear pass.
Step 5 — Transition Back into the Organisational Ecosystem
Closure is not just 'stop work'. Step 5 requires the project to hand over the products to the operational organisation, disband the project roles, retain lessons learned, and release people back to their permanent roles or to new projects. This step is the one most often skimped on in practice, and the exam likes to test it. The transition back is what distinguishes a PRINCE2 closure from simply running out of budget: the project ecosystem is deliberately retired, and the knowledge it generated is captured for the organisational ecosystem.
Exam Scenario Patterns
Three scenario types appear regularly. The first asks what happens at 'transition back' — the correct answer always involves handover of products, disbanding of project roles, and capture of lessons; distractors often describe starting a new project or extending the project ecosystem. The second asks for the sequence of the five steps — remember that 'understand' comes before 'design', and 'transition back' is the final step. The third asks what happens when the ecosystem changes mid-project — the answer is to return to the design step and then update the develop step, because the technique is iterative.
At project closure, the Project Manager is told to 'keep the project team running for a few weeks in case operational users need help'. Which step of the Organising technique is being ignored?
A restructure halfway through a project removes the Senior Supplier and replaces them with someone from a different division. According to the 5-step ecosystem technique, what should the Project Manager do next?