Projects create temporary capacity to change the organisation; value appears only when the permanent organisation can operate differently afterwards.
A project reaches practical completion. The system is installed. Training has been delivered. The new process is documented. The project team closes actions, hands over to operations and reports success.
Six months later, workarounds have returned, adoption is uneven, expected benefits are disputed and operating teams still rely on the old system whenever pressure rises.
The project may have finished. The change did not.
The Strategic Context
One of the most useful ideas in the supplied material is the distinction between the temporary organisation of the project and the permanent organisation that must live with its outputs.
The source diagram, adapted in the course notes from Silvius and colleagues, depicts project resources producing project outputs while the permanent organisation uses resources and assets through operations to create benefits and performance. Strategic management sets goals and evaluates performance; portfolio management helps select the changes that should be pursued.
This exposes a fundamental management boundary.
Projects are effective vehicles for focused change because they can assemble dedicated resources, work across functional lines and create a temporary structure around an objective. But projects are not usually the long-term owner of the benefits. The permanent organisation is.
That is why transformation cannot be governed solely through the project lifecycle.
What Leaders Commonly Misread
The first misread is equating installation with adoption. A system can be technically available without becoming the normal way work is performed.
The second is equating adoption with benefit. People may use the new process while expected productivity, service, safety or strategic outcomes fail to materialise.
The third is treating change management as communications and training. The supplied change material goes further. It emphasises realistic resources, stakeholder involvement, implementation, reinforcement and evaluation. Change requires operating conditions that support the new behaviour.
The fourth is assuming that resistance is the main reason change fails. Sometimes the organisation is resisting because the new design creates real operational friction: unclear roles, inadequate staffing, poor interfaces, conflicting incentives, missing data or targets that cannot be met in practice.
The fifth is keeping accountability inside the project for too long. If benefit ownership does not transfer clearly to operational leadership, the organisation can reach an ambiguous state where the project claims delivery and operations claims the solution was never viable.
Reframing the Issue
The right question is not, “Has the project delivered its outputs?”
It is:
Has the permanent organisation acquired the capability, behaviours and operating conditions required to produce the intended benefits?
That reframing changes both program design and governance.
The project becomes one part of a transition system. Technical delivery, process redesign, organisational roles, workforce capability, incentives, data, governance and operational ownership must converge around the same future state.
A transformation is complete only when the new system can perform without extraordinary project support.
Strategic Analysis: The Four Gaps Between Output and Outcome
1. The capability gap
A project can deliver equipment, software or procedures without delivering organisational capability. Capability includes people who know how to use the new system, supervisors who can manage it, maintenance arrangements, data, supplier support, governance and the ability to solve problems after the project team leaves.
Leaders should therefore ask what the organisation must be able to do repeatedly, not only what the project must produce once.
2. The behavioural gap
Change becomes real when everyday choices change. If performance measures, incentives and leadership behaviour continue to reward the old way of working, training alone will not sustain the new way.
This is why reinforcement matters. The change material highlights the need to communicate the reason for change, involve stakeholders, generate visible progress and embed new approaches into organisational practice. These are not cosmetic activities. They help create the social conditions in which the new operating model can persist.
3. The ownership gap
Benefits need an owner with authority over the operating system that produces them. Project managers can coordinate delivery, but long-term outcomes often depend on line leaders, service owners, product owners or functional executives.
Ownership should therefore move before project closure, not after it. The operational leader should participate in acceptance criteria, readiness decisions and benefit measures while there is still time to change the solution.
4. The absorption gap
Organisations have finite capacity to absorb change. New systems compete with existing workloads, other initiatives, operational crises and limited management attention. Even individually sensible projects can collectively exceed the organisation's ability to adopt them.
This is a portfolio issue as much as a project issue.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
Decision Framework
A useful transition test considers five layers.
| Layer | Question before closure |
|---|---|
| Output | Has the promised product, service or result been delivered to an acceptable standard? |
| Capability | Can the organisation operate, support and improve it? |
| Adoption | Are intended users consistently working in the new way? |
| Benefit | Are leading indicators showing movement toward the intended outcome? |
| Sustainability | Can performance continue without exceptional project resources? |
A project should not be held open indefinitely waiting for every benefit to mature. But closure should not sever accountability either.
A stronger model separates project closure from benefit closure. The project can close after agreed outputs, transition and readiness conditions are satisfied, while benefit ownership continues through operational governance.
Decision rights also need to be explicit. Who can delay go-live if the solution is technically complete but operationally unready? Who owns remediation after handover? Who decides whether a benefit shortfall means poor adoption, weak design or a flawed business-case assumption?
These questions should be answered before the final month of the project.
From Strategy to Execution
Immediately, identify the operational owner for each material benefit and require that owner to accept both the outcome measure and the transition conditions.
Over the medium term, integrate technical delivery and organisational change into one transition plan. This means that system readiness, workforce readiness, process readiness, data readiness, support readiness and governance readiness are considered together rather than in separate workstreams with separate definitions of “green”.
Over the long term, make post-project benefit review part of normal management rather than a special project-management exercise. Benefits belong in operating performance discussions because that is where they are actually generated.
For major transformations, leaders should also plan for a temporary stabilisation period after implementation. The goal is not to keep the project alive but to ensure that early operational problems are resolved quickly enough that the organisation does not revert to old behaviours.
A useful discipline is to treat the first operating period as evidence, not celebration. Early defects, workarounds, queue growth, support demand and unexpected behaviours reveal whether the designed future state works under real pressure. Leadership should decide in advance which problems are normal stabilisation issues and which indicate that the operating model, resourcing or benefit assumptions need to be reopened. This prevents teams from normalising poor performance simply because the implementation date has passed.
Related article: Business Cases Are Investment Hypotheses, Not Permission Slips
Signals to Monitor
A change is at risk when:
- operational leaders are absent from design decisions;
- training completion is treated as proof of adoption;
- users maintain parallel spreadsheets or informal workarounds;
- performance initially improves only while project specialists are present;
- supervisors continue measuring teams against old targets;
- benefit owners cannot explain the causal link between the project output and expected performance;
- multiple transformations compete for the same employees at the same time;
- project closure criteria are purely technical or administrative.
The strongest warning signal is a handover conversation dominated by documents rather than operating capability.
Questions for the Leadership Team
- Who owns the benefit after the project team leaves?
- What must operations be able to do repeatedly that it cannot do today?
- Which behaviours must change for the new system to create value?
- Are incentives, measures and management routines aligned to those behaviours?
- What other changes are competing for the same organisational capacity?
- Which readiness condition could justify delaying implementation even if technical delivery is complete?
- How will we know six months later whether the change worked?
References
Silvius, G, Schipper, R, Planko, J & Planko, MJ 2012, Sustainability in Project Management, Routledge, Farnham.
Graetz, F & Smith, A 2010, organisational change perspectives as cited in the supplied course material. [SOURCE DETAILS REQUIRED]
Closing Perspective
Projects are powerful because temporary organisations can concentrate effort around change. Their weakness is equally clear: they eventually disappear.
Enterprise value therefore depends on the quality of the bridge between temporary delivery and permanent operation. Leaders who govern only to completion will repeatedly celebrate outputs and later wonder where the benefits went. Leaders who govern to capability, adoption and ownership create a much stronger possibility that the change will survive the project that introduced it.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.