Project Management · Method
Project Management Phases: The 4 Phases – and Where Impact Is Actually Won
Every project runs a lifecycle, from the first idea to formal sign-off. Phase models divide that lifecycle into legible sections. They give structure, create a shared vocabulary, and make progress visible.
This article explains the four classic project phases – idea, planning, execution, closing – in plain terms and with concrete examples. It then adds the framing most guides omit: roughly 90 percent of a project's duration sits in a single phase. And it is precisely where the classic phase model ends as a checklist that the real work begins.
01
The four project phases at a glance
Most project management methods split a project into four phases. The labels vary; the logic is the same everywhere.
| Phase | Guiding question | Output |
|---|---|---|
| 1. Idea | What do we want to achieve, by when, on what budget? | Project charter, goals, scope |
| 2. Planning | Who does what, with which resources, in what order? | Work breakdown structure, initiatives, schedule |
| 3. Execution | Are we turning the plan into impact, and are we steering? | Realized progress, ongoing controlling |
| 4. Closing | Did we hit the goals, and what do we learn from it? | Sign-off, plan-versus-actual, lessons learned |
How many phases a model lists is a question of granularity, not of substance. KPMG typically works with four phases; McKinsey sometimes structures in five. Iterative frameworks such as the PDCA cycle (Plan, Do, Check, Act) or DMAIC (Define, Measure, Analyze, Improve, Control) arrange the same sequence into a repeatable loop. The four phases are the shared backbone of all these models.
02
The four phases in depth
The labels vary between methods; the work behind them does not. Four phases, one of which carries almost the entire project duration.
Idea
What should the project achieve, by when, on what budget?
The project charter and goal definition take shape here. A goal must be broad enough that everyone shares it, and precise enough that you can later verify whether it was reached. Skip this phase and it costs you twice.
Planning
Who does what, with which resources, in what order?
The goal becomes a plan: work packages, initiatives, owners, cost, and a sequence. Good planning states the what and the by when unambiguously, and leaves room in the how, with plan and capacity side by side.
Execution ~90% of duration
Are we turning the plan into impact, and are we steering?
The plan turns into impact; progress is measured and reconciled against the plan in regular cycles. This phase covers more than 90 percent of the entire project duration. It is where value is created or destroyed, and exactly where the classic phase model stops being useful.
Closing
Did we hit the goals, and what do we learn?
Results are checked against the original parameters of time, budget, and quality. The most important step, and the one most often skipped, is the debrief: failed initiatives in particular carry the most valuable organizational learning.
03
Where the phase model ends – and steering begins
The four-phase model is an excellent map. But a map is not the drive. It shows that execution follows planning; it does not steer the execution.
Most tools in project management follow the phase logic precisely, and stop where they ought to begin. They keep the work breakdown structure and the milestones clean. But the moment the 90-percent phase is live, hundreds of initiatives running in parallel, status shifting daily, several org levels to coordinate, steering falls back into spreadsheets, status slides, and weekly consolidation rounds. The phase model has done its duty; the value at risk, though, sits in the phase it describes least.
On large, multi-track initiatives this becomes the real problem. A restructuring, a post-merger integration, an EBITDA program: many workstreams across many levels, and a steering committee that, in case of doubt, decides on last week's numbers. Industry research has shown a constant picture for years: more than 70 percent of all large transformations miss their goals or even destroy value.1 The cause is almost never the strategy. It is the execution.
04
The ChangeMaker lifecycle: a grid for the 90-percent phase
This is where ChangeMaker® comes in. The platform divides the execution phase into four recurring working modes that run as the lifecycle of every initiative. They do not replace the classic project phases; they sit over their longest phase and make it steerable.
Design
How is the program structured, and who is involved?
Visualize goals and initiatives in a hierarchical PerformanceMap®; grant rights precisely and inherit them downward.
Work
How do the people involved act on it day to day?
Workbooks, personal dashboard, reminders, and a mobile app; feedback and alignment in the work context.
Report
Where do we really stand, live, not from last week?
Automatic reports at every level: status, maturity level, and milestones; KPIs current in the platform or via Excel plug-in.
Manage
Where is something going off track, and what do we do?
Spot problems at a glance, reach the root cause in a few clicks, and trigger a countermeasure in context.
The difference from a plain phase checklist is the shift from a single pass to a running loop. Status and financial impact roll up the structure automatically, so manual consolidation falls away. The question "where do we stand?" is answerable at any time, not only in the next reporting cycle.
05
Maturity level: confidence, not finished tasks
An initiative marked "done" in the plan says little about whether it actually delivers impact.
This is exactly where the maturity level workflow comes in: it carries every initiative
through defined maturity stages, from idea through concept and implementation to realized impact.
This makes progress impossible to flatter.
06
Why execution fails on people, not on phases
There is a deeper reason the 90-percent phase tips over so often. Phase models and classic tools treat execution as a pure coordination problem: the right tasks, to the right people, at the right time. Coordination is necessary. It is not sufficient.
The behavioral science behind ChangeMaker® describes three success factors in any execution, the 3C method: Concerns, Competencies, Coordination.
| Dimension (3C) | Question in execution | Does the phase model address it? |
|---|---|---|
| Coordination | Is everyone pulling in the same direction, in sync? | Yes. Every project plan does this. |
| Concerns | Do the people involved actually associate with the initiative? | No. The plan assumes buy-in; it does not create it. |
| Competencies | Can they implement the initiatives at all? | No. The plan names the task but builds no capability. |
A plan on a slide changes no behavior. When the people involved do not feel the goal is their own, or lack the ability to implement an initiative, the best work breakdown structure stays a well-formatted statement of intent.
The evidence backs this up. A McKinsey analysis of 60 listed companies shows that transformations with the highest active workforce involvement (21 to 30 percent) delivered roughly +67 percent higher excess return over the sector benchmark across 24 months than programs with minimal involvement.2 Involvement is Concerns, not Coordination. A phase model alone does not reach it.
07
Project phases in practice: a customer example
08
From phase model to realized impact
The four project phases remain the right backbone. Idea, planning, execution, closing give every project structure and a shared vocabulary. Run them cleanly and you avoid the most common early mistakes. But the map is not the drive: more than 90 percent of a project's duration, and nearly all of the value at risk, sit in execution, the phase the classic model describes most briefly.
ChangeMaker® makes exactly that phase steerable. The lifecycle of Design, Work, Report, and Manage turns execution into a running loop; the maturity-level workflow forces maturity over ticked-off tasks; and the 3C method addresses the human side where most initiatives fail. Initiatives link directly to P&L, balance-sheet, and cash KPIs. For EU customers, data processing and storage take place in Germany (AWS Frankfurt), and the ISMS is certified to ISO 27001.3
09
A project rarely fails on the wrong phase. It fails on what goes unsteered in the longest one.
Make change. Not plans.
Frequently asked questions about project phases
How many project phases are there?
What are the 4 phases of a project?
Which project phase is the most important?
How do PDCA, DMAIC, and the four project phases relate?
Why do projects fail despite a clean phase model?
What tool supports the execution phase of large projects?
Sources
- Cross-industry transformation research has reported for years that more than 70% of large transformations miss their goals (McKinsey and BCG among others). Treated here as established consensus rather than a citation to a single study.
- McKinsey & Company, “Seven percent solution? How many employees should be involved in your transformation?” (2021). n = 60 listed companies; excess total shareholder return over 24 months against a representative sector and region index; highest excess return at 21 to 30% actively involved workforce. To be read as a correlation, not a guaranteed causal effect.
- First-party data from ChangeMaker® / Principia Mentis (knowledge base, product and training materials): consolidation and reporting effort reduced by up to 85%, an average of roughly 8 days saved per initiative; ISMS certified to ISO 27001, data processing and storage for EU customers in Germany (AWS Frankfurt). Figures from documented customer programs, not an independent study.
Make the 90-percent phase steerable
In a short demo, we show how ChangeMaker® turns execution into a running loop, with live data, the maturity-level workflow, and the 3C method, on your specific program.