Delivery creates the possibility of change; the permanent organisation decides whether that possibility becomes normal practice.
A project team can install a system, relocate a facility, redesign a process or launch a new operating model and still leave the organisation substantially unchanged. The deliverable exists, the milestones are complete and the project is closed—but people continue using old workarounds, managers restore familiar routines, data quality deteriorates or the intended benefits never become part of operating performance.
This gap between project completion and organisational change is one of the most important governance failures in transformation.
The supplied study material repeatedly treats projects as temporary organisations used to create change in permanent organisations. It also emphasises that planning the technical change is not enough: leaders must plan the introduction and transition of the change to stakeholders, supported by preparation, communication, participation and resources.
The Strategic Context
Temporary organisations are useful precisely because they can concentrate expertise, authority and attention on a defined change. Their weakness is equally clear: they are designed to end.
The permanent organisation, by contrast, must live with the result. Its people operate the new process, maintain the asset, own the customer relationship, sustain the data, comply with the new control and generate the benefit.
That creates a structural handover problem. Project teams are often rewarded for delivery. Operational teams are rewarded for continuity and current performance. The transition period can therefore create conflicting incentives: the project wants adoption; operations wants stability; users want competence before abandoning familiar practices; executives want benefits quickly.
If governance treats handover as the moment responsibility ends, the change is exposed precisely when it needs reinforcement most.
What Leaders Commonly Misread
The first misread is confusing communication with adoption. Telling people that a new process will begin on Monday does not mean they understand it, can perform it or believe it is better than the old method.
The second is treating resistance as irrational behaviour. People may resist because the change creates real operational risk, threatens valued capability, conflicts with incentives, increases workload or has not been designed with sufficient local knowledge. Leadership should distinguish obstruction from useful information.
The third is underestimating transition resources. The supplied change notes identify human, physical, budget and time resources as necessary for implementation. A project can fund the new technology while failing to fund backfill, training, data cleansing, supervision or temporary productivity loss during transition.
The fourth is declaring victory at go-live. Kotter's change model, as represented in the supplied study material, ends not with launch but with anchoring new approaches in organisational culture. The logic is important: without institutionalisation, people can revert to old and comfortable ways once project attention disappears.
Reframing the Issue
Change should be governed as a transition of operating capability, not as a transfer of deliverables.
A useful distinction is:
Output: what the project creates.
Capability: what the organisation becomes able to do.
Behaviour: what people consistently do in practice.
Benefit: the performance improvement that follows.
Projects can deliver outputs directly. They influence the other three but rarely control them alone.
This is why benefit ownership should normally sit in the permanent organisation. The project team can prepare the conditions for value; the operational owner must sustain those conditions after closure.
Related article: Why the Iron Triangle Is Too Small for Strategic Project Success
Strategic Analysis: Change Needs Both Momentum and Institutionalisation
The supplied material presents Kotter's eight-stage change model: establish urgency, create a guiding coalition, develop vision and strategy, communicate the change vision, empower broad-based action, generate short-term wins, consolidate gains and produce more change, and anchor new approaches in culture.
The value of this model is not that every transformation must follow eight perfectly sequential steps. The same study notes cite Appelbaum and colleagues' 2012 review and position Kotter's model as a useful implementation-planning reference that should be complemented by tools responsive to context.
That is the more practical executive interpretation.
Urgency explains why remaining unchanged is unacceptable. Without it, change competes poorly against daily operational pressure.
Coalition recognises that authority is distributed. A sponsor alone cannot redesign every workflow or influence every stakeholder.
Vision and communication reduce ambiguity about what is changing and why.
Empowerment removes structural obstacles such as conflicting procedures, missing authority or lack of capability.
Short-term wins provide evidence that effort is producing value.
Consolidation prevents early progress from being mistaken for completion.
Anchoring converts the change from a project initiative into the way the organisation operates.
The model becomes particularly powerful when linked to program governance. Different projects may create technology, process, data, infrastructure and training components, but the program must coordinate them into one transition state that operations can actually absorb.
Decision Framework
A practical CHANGE-to-CAPABILITY framework can be used at each transition.
| Dimension | Executive test |
|---|---|
| Case | Is the reason for change still compelling and understood? |
| Ownership | Is there a permanent leader accountable for the operating outcome? |
| Readiness | Are process, people, data, technology, suppliers and controls ready together? |
| Capability | Can users perform the new way of working without project-team dependence? |
| Incentives | Do measures, targets and local priorities reinforce the new behaviour? |
| Evidence | Are early results showing that the change works in the real operating environment? |
| Reinforcement | What will stop regression after project attention moves elsewhere? |
A project should not pass from implementation into closure merely because technical acceptance is complete. It should also have a credible transition plan defining support ownership, unresolved risks, competence, benefits, operating measures and the period of intensified post-implementation monitoring.
This does not mean keeping project teams alive indefinitely. It means designing the exit so that the permanent organisation can succeed without them.
From Strategy to Execution
Immediate action is to move transition planning earlier. Handover should be designed during planning, not assembled near the end. Identify the permanent owner, required capabilities and likely barriers before major implementation decisions become irreversible.
Medium-term capability building should create a repeatable operating-readiness discipline. For significant transformations, use readiness reviews covering process, people, technology, data, physical environment, controls, suppliers and customer impacts. A green technology status should not override a red people or process status.
Long-term positioning requires leaders to develop transformation capability inside the permanent organisation. If every major change depends entirely on external consultants or a central project team, the organisation repeatedly rents change capability without building it.
Leaders should also protect operational knowledge. The source material's pluralistic perspective is relevant here: organisations contain multiple groups with legitimate interests and different information. Frontline employees often understand failure modes that the design team cannot see from a project office. Participation is therefore not merely a morale intervention; it is a source of system intelligence.
A hypothetical manufacturing example makes this visible. Suppose a project automates a manual line and achieves its commissioning target. If standard work, maintenance capability, material replenishment, escalation routines and operator training remain aligned to the old process, the automation may technically run while overall throughput and reliability disappoint. The project delivered machinery; the organisation did not yet complete the operating-model transition.
Related article: Projects Deliver Change; Portfolios Decide Which Change Deserves Capacity
Signals to Monitor
Watch for project teams providing extended informal support because operations cannot function independently; users maintaining parallel spreadsheets or old procedures; benefit measures deteriorating after the initial launch period; repeated exceptions being approved to preserve legacy behaviour; training completion being used as a proxy for competence; operational leaders referring to the change as “the project's system” rather than their own; and unresolved issues moving into business-as-usual without named owners.
A further signal is repeated transformation fatigue. It may indicate not that people oppose change, but that the organisation starts new changes faster than it stabilises previous ones.
Questions for the Leadership Team
- Who owns the operating outcome after the project team leaves?
- What must people be able to do—not merely know—before transition is complete?
- Which incentives or legacy processes could pull behaviour back to the old state?
- What operational capacity will be temporarily lost while people learn the new way of working?
- How will we know whether a short-term win is becoming a durable capability?
- Are we closing the project because the organisation is ready, or because the project schedule says it should end?
Sources and Notes
This article develops an original ERANORTH synthesis from supplied study notes on organisational change, resource allocation, stakeholder transition and Kotter's eight-stage change model. The notes cite John P. Kotter (1996) and Appelbaum, Habashy, Malo and Shafiq (2012), “Back to the future: revisiting Kotter's 1996 change model,” Journal of Management Development, 31(8), 764–782.
Closing Perspective
Transformation is complete only when the new capability no longer depends on transformation machinery to survive. The leadership task is not simply to deliver change, but to make the permanent organisation capable of owning it.