The Why — Every Project Is a Change Project
Every project, by definition, delivers something new. A new frigate combat system. A new ERP rollout across a manufacturing plant. A new safety procedure on a mine site. The technical deliverable is only half the equation — the other half is the organisational and human transition required to absorb that deliverable into "business as usual."
A Project Manager who can build a Gantt chart but cannot lead change will deliver an output the organisation refuses to use. Schedule and cost variance are visible; adoption variance is the silent killer of project value.
In major defence and heavy engineering environments — where transitions involve unionised workforces, export-controlled processes, and decades-old operating cultures — change leadership is not a "soft skill." It is the discipline that protects the benefits case.
The What — Defining Organisational Change
Drawing on the supplied research, we can anchor a working definition:
Organisational change is any alteration in people, structure, or technology within an organisation. It is ever-present, cannot be eliminated, and must therefore be actively managed rather than avoided.
The Three Categories of Change
| Category | Scope | Project Examples (Heavy Engineering / Defence) |
|---|---|---|
| Structure | Work specialisation, departmentalisation, chain of command, span of control, centralisation, formalisation, job redesign | Standing up a new IPT (Integrated Project Team); merging maintenance and engineering functions under a single Asset Manager |
| Technology | Work processes, methods, equipment | Replacing a CMMS; introducing additive manufacturing on a sustainment line; CAD/PLM migration |
| People | Attitudes, expectations, perceptions, behaviours | Safety culture reset after an incident; embedding Agile ceremonies in a Waterfall-trained engineering bureau |
Most real projects touch all three categories simultaneously — which is precisely why change is hard.
The How — Two Models Every PM Must Carry
1. The three-phase change model Three-Phase Model
The three-phase change model proposes that durable change moves through three sequential states:
The three-phase change model explains that the transition itself is achieved through two complementary actions:
- Increase driving forces — incentives, sponsorship, executive air-cover, position power.
- Reduce restraining forces — fear of job loss, skill gaps, sunk-cost attachment, political opposition.
Force Field Analysis
The Force Field tool gives the PM a literal balance sheet of the change. Each force is rated (commonly +1 to +4 / −1 to −4), and the net score indicates whether the system will move, stall, or regress.
| Driving Forces (+) | Strength | Restraining Forces (−) | Strength |
|---|---|---|---|
| Executive sponsor mandate | +4 | Tradesperson fear of de-skilling | −3 |
| Cost savings business case | +3 | Legacy IT integration risk | −3 |
| Safety regulator pressure | +4 | Middle-management political loss | −2 |
| Total Driving | +11 | Total Restraining | −8 |
Net = +3 → Change is feasible but fragile. The PM's job is to widen that gap before go-live, ideally by reducing restrainers rather than just shouting louder with drivers.
2. Engineering manager eight-step change sequence Eight Steps
Where three-phase change model gives us the physics of change, eight-step change sequence gives us the playbook. His eight steps remain the most widely taught sequence in PM and MBA programmes.
| Step | Project Manager's Action | Defence / Heavy Engineering Example |
|---|---|---|
| 1. Increase Urgency | Quantify the cost of the status quo | "If we don't migrate the CMMS by EOFY, sustainment KPIs breach the applicable contract framework contract." |
| 2. Build the Guiding Team | Form a cross-functional sponsor coalition | Project Sponsor + Engineering Manager + Union Delegate + acquisition authority Liaison |
| 3. Get the Vision Right | One-page vision, testable in 30 seconds | "Zero unplanned downtime by Q4 through predictive maintenance." |
| 4. Communicate for Buy-in | Repeat 7× through 7 channels | Toolbox talks, intranet, town halls, posters in the workshop |
| 5. Empower Action | Remove blockers, delegate authority | Issue temporary procedure waivers; fund overtime for training |
| 6. Create Short-term Wins | Engineer visible early successes | First production cell migrated within 60 days, celebrated publicly |
| 7. Don't Let Up | Resist premature "mission accomplished" | Maintain the steering committee through the warranty period |
| 8. Make Change Stick | Hard-wire into HR, KPIs, induction | Update position descriptions, onboarding decks, and audit checklists |
The Human Curve — What People Actually Feel
Models are tidy. Humans are not. Drawing on change-response curve grief cycle (adapted for organisational change), people typically traverse four emotional zones:
A parallel curve — sometimes called the Change Curve or positive change arc — tracks mood over time:
- Uninformed Optimism (the honeymoon: "this'll be easy")
- Informed Pessimism (the trough: "this is harder than we thought")
- Informed Optimism (the climb: "we can actually do this")
- Completion (embedded confidence)
The PM's most dangerous moment is Informed Pessimism — the valley where good projects are quietly killed by attrition, executive impatience, and budget reviews. Plan for the trough before you enter it.
The Pitfalls — Where Project Managers Lose Change Battles
- Treating change as a comms problem. Sending an email is not change leadership. Behaviour shifts require coaching, KPI alignment, and structural reinforcement.
- Skipping the Unfreeze. Jumping straight to "the new system goes live Monday" guarantees resistance. People must first be dissatisfied with the old way.
- Declaring victory too early. eight-step change sequence Step 7 exists because executives love to redeploy sponsorship the moment short-term wins land. The change then quietly thaws.
- Ignoring the middle layer. Frontline workers and senior executives are usually surveyed; middle managers, who actually own the restraining forces, are often the silent killers.
- No Refreeze mechanism. If HR position descriptions, audit checklists, induction decks, and reward systems are not updated, the organisation reverts within 12 months.
- Confusing compliance with commitment. People may do the new process while waiting for it to fail. Watch for malicious compliance.
Knowledge Check
- A defence sustainment project is migrating 400 technicians from paper-based work orders to a tablet-based CMMS. Using three-phase change model, name one specific action you would take in each of Unfreeze, Change, and Refreeze.
- Your Force Field Analysis returns Driving = +9, Restraining = −9. What does three-phase change model theory suggest you do first — and why is that counter-intuitive to most executives?
- Map the change-response curve emotional stages to eight-step change sequence eight steps. Where is the highest risk of project failure, and which eight-step change sequence step is the antidote?
Key Takeaways
- Every project is a change project — technical delivery without adoption is wasted spend.
- Change touches three categories: structure, technology, and people — most real projects touch all three.
- three-phase change model gives you the physics: Unfreeze → Change → Refreeze, powered by driving and restraining forces.
- eight-step change sequence gives you the playbook: eight sequential steps from urgency to embedment.
- change-response curve reminds you that humans grieve the old way before they adopt the new — plan for the Valley of Despair.
- The PM's greatest leverage is usually in reducing restraining forces, not amplifying drivers.
- Refreeze is non-negotiable — without HR, KPI, and audit reinforcement, organisations revert.
"There is nothing wrong with change, if it's in the right direction." — a historic national leader
Integrated Insights from the Supplied Source Set
The archive contains several overlapping treatments of this subject. The following sections retain the most distinct practical material while avoiding a second article that teaches the same core topic.
What's the Difference? Functional vs Project Management
Integrated source perspective — Source 63: This section preserves distinct material from an overlapping source treatment.
Both are legitimate management disciplines, but they answer different questions.
| Dimension | Functional Management | Project Management |
|---|---|---|
| Purpose | Run ongoing business operations | Deliver a unique outcome to a defined specification |
| Duration | Indefinite | Temporary — has a defined start and end |
| Scope | Routine, repeatable work | Novel, one-off or significantly different work |
| Authority | Direct line authority, usually permanent | Temporary, often matrix, frequently shared |
| Team | Stable, long-tenure staff | Assembled, borrowed, and released |
| Success metric | Efficiency, throughput, service level | On time, on budget, fit for purpose |
| Relationship to change | Preserves stability | Creates change |
A new project leader, especially one promoted from a functional role, must consciously unlearn some instincts. The reflex to "optimise the steady state" has no traction when the steady state is the very thing being replaced.
Applying the Guidance as a Controlled Practice
Use this subject as a decision aid, not as a label applied after the event. Start by defining the delivery problem, the people affected, the authority available and the consequences of a poor decision. Record assumptions before selecting an intervention. That simple discipline makes later review possible and prevents a preferred leadership style from being treated as the answer to every situation.
Six-Step Application Cycle
- Define the trigger. State the decision, behaviour, team condition or delivery risk that requires attention. Separate observation from interpretation.
- Map the context. Identify the project phase, task uncertainty, dependencies, stakeholder interests, time pressure, team capability and formal authority.
- Choose a proportionate response. Select the smallest intervention capable of improving the condition. Explain why it fits the evidence and what alternatives were rejected.
- Agree ownership and boundaries. Make decision rights, escalation points, review dates and non-negotiable safety or ethical limits visible to the people involved.
- Act and observe. Monitor both delivery indicators and human signals such as challenge, information sharing, participation, trust and follow-through.
- Review and adapt. Compare the result with the original intent. Retain, adjust or stop the intervention, and capture the learning for the next phase.
Evidence and Verification
| Required record | Purpose | Verification question |
|---|---|---|
| Change impact statement | Makes the selected approach and its basis visible. | Can an independent reviewer understand why this response was chosen? |
| Force-field analysis | Translates intent into owned actions, interfaces or boundaries. | Does every critical action have an owner, timing and escalation path? |
| Adoption and reinforcement plan | Preserves evidence of follow-through and learning. | Does the record show what changed, what did not and what happens next? |
Evidence should be proportionate to the project's risk and governance needs. A short decision note may be sufficient for a routine team adjustment; a high-consequence change may require sponsor approval, formal consultation, controlled records and a scheduled assurance review. Documentation must support judgement rather than replace it.
Review Questions
- What observable condition are we trying to change, and how will we know if it improves?
- Whose perspective is missing from the diagnosis or decision?
- Are authority, accountability and capability aligned, or are we asking someone to own an outcome they cannot control?
- Could the intervention suppress challenge, conceal risk or create dependency on one individual?
- What evidence will trigger escalation, adaptation or closure?
Practice boundary: Frameworks in this article organise thinking; they do not guarantee performance. Project context, contractual obligations, safety duties, workplace requirements and approved governance remain controlling.