Project completion proves that an intervention ended; it does not prove that the organisation became better.
A project team can complete every deliverable, close every contract, hand over every asset and still leave the enterprise with little of the value that justified the investment.
This is not a contradiction. It reflects the difference between a temporary organisation and the permanent organisation it is intended to change.
The supplied MPM416 material makes that distinction explicit. Permanent organisations use resources and assets through operations to produce products, services, benefits and performance. Temporary organisations such as projects are created to deliver change because they can be more focused and flexible than the permanent structure. Portfolio management helps select which changes should be undertaken.
The strategic failure occurs when leaders govern the temporary organisation closely but treat the permanent organisation as a passive recipient.
The Strategic Context
Most transformations require two systems to work at the same time.
The delivery system must design, build, procure, configure, test and hand over the change.
The adoption system must alter behaviour, capability, process, decision rights, incentives and operating routines so that the new condition produces value.
Project management is naturally strong at the first system. Its temporary structure creates focus, authority, milestones and resources. That is precisely why organisations use projects to implement change.
But the second system lives largely outside the project. Benefits are generated after people use the new capability in ongoing operations. If the permanent organisation cannot absorb, operate or sustain what the project delivers, the formal project may succeed while the transformation fails.
The course material on implementing change reinforces the point through themes such as communicating the need for change, creating a guiding coalition, developing vision and strategy, enabling action, creating short-term wins and anchoring new approaches in organisational culture. These activities are not simply communication tasks added to a project plan. They are mechanisms for changing the permanent system.
What Leaders Commonly Misread
The first misread is that handover transfers responsibility for value automatically. A signed acceptance certificate can transfer custody without transferring capability.
The second is that training equals adoption. Training can explain how a new system or process works. It does not guarantee that roles, incentives, workload, local procedures or management behaviour will support its use.
The third is that resistance is primarily a communications problem. Sometimes people resist because they do not understand the change. But they may also resist because the proposed change increases workload, removes autonomy, conflicts with local targets, threatens expertise or fails to solve the operational problem they actually face.
The fourth is that project closure is the natural endpoint of transformation governance. In many cases, closure is the point at which the hardest benefits work begins.
Reframing the Issue
A transformation should be viewed as a chain:
strategic need → selected change → project output → operational adoption → changed performance → realised benefit.
Every arrow is a dependency.
If leaders govern only the project-output step, they are governing the most visible portion of the chain rather than the whole value system.
Related article: The Iron Triangle Does Not Measure Strategic Success
Strategic Analysis: The Permanent Organisation Owns the Benefit
Projects create assets and capabilities; operations create results
A new production line does not create productivity by existing. Productivity depends on process design, maintenance, scheduling, material flow, operator competence, quality control and demand.
A new digital platform does not create service improvement by being deployed. Improvement depends on adoption, data quality, process redesign, user behaviour and management use of the information.
The project can influence those conditions, but it cannot permanently own them.
Organisational interfaces are where value leaks
The supplied diagram of projects as temporary organisations highlights the interface between project resources, delivery and outputs on one side, and operational resources, operations, benefits and performance on the other.
That interface is often treated as a handover event. It should be treated as a transition system.
A mature transition defines who owns the future process, what capabilities must exist, what old practices must stop, what measures will prove adoption and what operating conditions must be achieved before the change is considered embedded.
Change capacity is finite
The source material emphasises that change may require new or differently used human, physical, budget and time resources. That means the permanent organisation has absorption limits.
A portfolio can approve more strategically attractive change than the enterprise can implement successfully. Each initiative may look viable in isolation while collectively overloading the same managers, subject-matter experts, operators or enabling functions.
This is where transformation becomes a portfolio problem. Capacity must be allocated not only to build projects but to absorb the changes they create.
Related article: Capacity Is a Strategic Constraint: Match Ambition to What the Organisation Can Absorb
Anchoring matters because systems revert
The supplied change material warns that new approaches can slip away if they are not anchored in organisational practice. This is consistent with a systems view: old behaviours often exist because incentives, structures, skills or workflows reinforce them.
If the project changes the visible process but not the reinforcing conditions, the organisation may revert after project attention disappears.
Sustainable change therefore requires leaders to identify what system produced the old behaviour and redesign enough of that system to make the new behaviour easier to maintain.
Decision Framework
Before a transformation project is approved, require five ownership decisions.
| Ownership question | Evidence required |
|---|---|
| Who owns the operational outcome? | Named accountable role outside the temporary project |
| What behaviour or process must change? | Observable future-state practices |
| What capability is required? | Skills, systems, resources and local management support |
| How will adoption be measured? | Leading measures before financial benefits appear |
| When is transition complete? | Operational readiness and stabilisation criteria |
Then separate three kinds of success:
Delivery success: the agreed output was produced.
Adoption success: the permanent organisation is using the output as intended.
Benefit success: measurable performance changed in the direction that justified the investment.
These can occur at different times and should have different owners.
From Strategy to Execution
Immediate action: For active transformation projects, identify the operational benefit owner and test whether that person has authority, capacity and measures for adoption. If ownership begins only at handover, move it earlier.
Medium-term capability: Add transition readiness to governance. Review workforce capacity, process changes, data, training, operating procedures, maintenance, support and management routines before declaring the organisation ready.
Long-term positioning: Manage enterprise change as a portfolio of interventions affecting one operating system. Track collisions where multiple projects require behaviour change from the same functions or where one project's future state conflicts with another's assumptions.
Signals to Monitor
- project completion is celebrated before adoption evidence exists;
- operational leaders sign acceptance but do not own benefit measures;
- training completion is used as the principal adoption metric;
- old processes continue in parallel indefinitely;
- workarounds increase after go-live;
- benefits are expected from teams whose capacity was not included in the business case;
- repeated transformation programs target the same problem because earlier changes did not become embedded.
Questions for the Leadership Team
- Who owns each major benefit after the project team leaves?
- What operational behaviour must change for that benefit to exist?
- Are we funding the permanent organisation's transition effort or only the temporary project's delivery effort?
- Which parts of our portfolio compete for the same organisational change capacity?
- What would cause the organisation to revert to the old way of working?
- Do our closure criteria prove completion, adoption or benefit realisation?
Source References
- University of South Australia, MPM416 Week 1 teaching materials on temporary and permanent organisations and project-enabled change.
- University of South Australia, Study Notes: Tailoring Project Management and Change, supplied course material.
Closing Perspective
Projects are powerful because they concentrate resources around change. That strength becomes a weakness when leaders assume the temporary structure can also sustain the new operating condition indefinitely.
The enterprise must eventually carry the change itself.
A transformation is therefore complete only when the permanent organisation has absorbed the new capability, changed the relevant behaviour and can produce the intended benefit without depending on project scaffolding.
Finishing the project is an event. Making the change real is an operating condition.