A project can deliver exactly what was approved and still fail to change the organisation in the way the business case assumed.
Projects are often created because an organisation wants a different future state: a new system, process, facility, product, operating model or capability.
That makes project managers participants in change. But it does not mean the project output itself is the change.
A new system can be installed without being adopted. A new production process can be commissioned while old behaviours continue. A restructuring can be announced without decision rights changing in practice. The physical or technical deliverable is therefore only one component of transformation.
The Strategic Context
The supplied material presents project managers as change agents and includes familiar change concepts such as Lewin and Kotter. It also emphasises stakeholder communication, resistance and the need to involve affected people.
The deeper strategic issue is ownership. Projects are temporary, while organisational behaviour is ongoing. If benefits depend on new behaviours after the project team disbands, someone outside the project must own that transition.
Programs are often the better level for this integration because they can coordinate multiple projects, operating changes and benefits over time.
What Leaders Commonly Misread
The first mistake is treating change management as communication. Communication matters, but information alone does not alter incentives, roles, skills, systems or habits.
The second is assuming resistance is irrational. People may oppose change because they understand operational consequences that designers have missed. Resistance can be evidence.
The third is declaring success at handover. Handover proves that an output exists. It does not prove that the organisation is using it effectively or that benefits have materialised.
Reframing the Issue
Separate four layers of transformation:
- output: what the project delivers;
- adoption: whether people use it;
- capability: whether the organisation can operate it reliably;
- benefit: whether the intended business outcome occurs.
Project governance often becomes weak because these layers are collapsed into one milestone.
Change Has an Operating-Model Dimension
A new technology can change who has information, who makes decisions, what skills are valuable and which processes become unnecessary.
That means transformation leaders should ask operating-model questions early. Which roles change? Which decisions move? What work disappears? What new capability becomes critical? What measures should change?
Without this analysis, organisations automate existing assumptions rather than redesigning the system.
Resistance Is a Diagnostic Tool
The supplied personal reflections recognise that change can create both positive and negative consequences for people.
Leaders should therefore distinguish between resistance caused by uncertainty, loss, poor communication, capability gaps and legitimate design concerns.
The response differs. More communication will not solve a badly designed process. Training will not resolve a loss of decision authority. Executive sponsorship will not make an unusable system useful.
Benefits Need Owners Beyond the Project
A project manager can coordinate benefit-related work but should not be expected to own an operating result indefinitely after closure.
Benefits should have named business owners with measures, baselines and review points. These owners must remain accountable after the temporary delivery structure dissolves.
This is where project, program and operational governance must connect.
A program perspective is useful because it keeps related work, organisational transition and benefits connected after individual projects complete. The business should not have to reconstruct ownership at every handover.
Change Capacity Is Also a Portfolio Constraint
Organisations can approve more change than their people can absorb.
A portfolio may contain several individually rational initiatives that all require the same managers, subject-matter experts or frontline teams to adopt new processes at the same time. The result is not simply resource contention. It is change saturation.
This should be governed explicitly. Leaders need to understand which groups are affected by which initiatives, when behavioural change is expected and whether the combined burden is feasible.
A transformation portfolio should therefore sequence adoption as carefully as it sequences technical delivery.
Transition States Matter
Large changes rarely move directly from an old operating model to a stable new one. There are intermediate states in which systems coexist, responsibilities overlap and performance can temporarily decline.
These transition states deserve deliberate design. Who owns decisions while two processes operate? Which measure takes precedence? What temporary controls are required? What triggers the next stage?
Ignoring the transition state creates a gap between project plan and operating reality. Strong program leadership makes that gap visible and governable.
Decision Framework
For each intended change, test six conditions.
| Condition | Question |
|---|---|
| Outcome | What business result should change? |
| Behaviour | What must people do differently? |
| Capability | What skills, process or technology must exist? |
| Incentive | What encourages or discourages the new behaviour? |
| Ownership | Who owns adoption and benefits after delivery? |
| Evidence | How will we know the change is working? |
If these questions cannot be answered, the initiative may have an output plan without a transformation plan.
A further test is reversibility. If the transition is difficult to reverse, leaders need stronger evidence before committing the organisation. If the change is reversible, staged experiments can reduce uncertainty before full deployment.
From Strategy to Execution
Immediate action: revisit major projects and identify where benefits depend on behaviour outside project control. Assign explicit business owners and clarify what evidence they will use to judge adoption.
Medium-term capability building: integrate change analysis into business cases, design operating-model impacts early and create transition measures that extend beyond implementation dates. Give operational leaders a meaningful role before final design decisions are locked in.
Long-term strategic positioning: manage transformation as a portfolio of capability changes rather than a collection of technical projects. Stop initiatives whose outputs no longer justify the organisational disruption they require. Build institutional capability for adoption, benefit ownership and post-project review.
Related article: Temporary Teams Should Leave Permanent Capability
Related article: The Hidden Cost of the Iron Triangle
Signals to Monitor
Watch for projects reporting green while users avoid the new process, benefits being measured only during implementation, operational leaders joining too late, training occurring immediately before go-live without practice, old systems remaining because confidence in the new environment is low, and teams equating communication activity with adoption.
Another warning sign is a benefits register owned by the project office rather than by the part of the business expected to realise the benefit. That may preserve documentation while weakening accountability.
Positive signals include business-owned measures, early involvement of affected functions, explicit transition states, feedback changing the design and benefit reviews continuing after project closure.
Questions for the Leadership Team
- Which current projects are delivering outputs rather than outcomes?
- Who owns each material benefit after the project team leaves?
- What behaviours must change for our major transformations to succeed?
- Which resistance is telling us something important about the design?
- What old process, measure or incentive must stop for the new model to work?
- Are we willing to change or stop a project if adoption evidence remains weak?
- What transition decision today will be hardest to reverse later?
Closing Perspective
Projects are powerful vehicles for change because they concentrate resources and attention around a defined outcome. But temporary delivery structures cannot substitute for permanent organisational ownership.
The mature leadership question is not, "Did we deliver the project?" It is, "Did the organisation become more capable, did behaviour change and did the intended benefit occur?"
Change is not the thing delivered at the end. It is the new way the organisation is able to operate afterwards.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.