Installing a new technology can be a project success and an enterprise failure if the surrounding system continues to reward the old way of working.
Transformation programs often begin with a visible object: a platform, facility, process, structure or policy. That object is easier to budget, schedule and govern than the behavioural and organisational changes required around it. As a result, leaders can convince themselves that implementation is progressing because the technical deliverable is on time while the operating model remains largely unchanged.
The supplied change-leadership material offers a simple but powerful distinction: organisational change can affect structure, technology and people. Treating those categories independently creates risk because they interact. A technology can redistribute decision authority. A structural change can alter information flows. A new process can make existing skills obsolete. A changed incentive can overwhelm the behaviour a training program was intended to create.
The Strategic Context
Projects create outputs. Transformations must create new organisational performance. That difference changes how success should be governed.
A system implementation may be complete when software is deployed and users have access. A transformation is not complete until the organisation can reliably produce the intended outcome through the new way of working. That may require changes to roles, measures, incentives, workflows, capability, management routines and customer interactions.
Lewin's change model is presented in the source material through unfreezing, changing and refreezing, alongside force-field thinking about driving and restraining forces. Kotter's sequence emphasises urgency, a guiding coalition, vision, communication, empowered action, short-term wins, sustained effort and making change stick. These models differ in form but share a systems insight: change is not simply the introduction of a new state; it is the alteration of forces that keep the old state in place.
What Leaders Commonly Misread
The first misreading is resistance as a communication defect. People may resist because they do not understand the change, but they may also understand it perfectly and see rational personal or operational disadvantages. Their workload may increase. Their status may fall. Their competence may become less valuable. They may have evidence that the proposed design will not work in practice.
The second misreading is believing training equals adoption. Training can provide capability. It cannot by itself correct a performance metric that rewards the old behaviour, a manager who continues to demand the old process, or a workflow that makes the new method slower.
The third is assuming leadership alignment at launch will persist. Transformations compete with operational pressure. When deadlines tighten, people often revert to familiar practices unless governance actively protects the transition.
The fourth is treating "go-live" as the end of change. It is often the point at which organisational consequences become most visible.
Reframing the Issue
Transformation should be understood as a controlled redesign of an operating system.
That system includes formal structure, technology, people capability, culture, incentives, information, decision rights and external dependencies. Changing one element can produce second-order effects elsewhere.
Consider a hypothetical manufacturing business introducing automated scheduling. The software may optimise production sequencing, but supervisors may continue changing priorities informally to satisfy urgent requests. Sales may still promise delivery dates without reference to capacity. Performance metrics may reward local utilisation rather than total flow. The technology is operational, yet the decision system around it has not changed.
A healthcare example might involve a new digital workflow intended to improve patient handovers. If staffing models, clinical accountability and escalation practices remain unchanged, the organisation may digitise existing coordination problems rather than solve them.
The executive responsibility is therefore to govern the interactions between technical and organisational design.
Strategic Analysis: Driving Forces Are Not Enough
Leaders are often good at adding force: executive sponsorship, communications, deadlines, training, incentives and project resources. Less attention is given to removing restraining forces.
Restraining forces may include obsolete policies, duplicated systems, conflicting measures, fears about competence or job security, legacy contracts, overloaded managers, weak data, or a history of previous failed changes. Adding more pressure without removing constraints can create compliance while reducing trust.
This suggests a more disciplined change question: What is making the current behaviour rational?
If people keep using a spreadsheet after an enterprise platform is introduced, the response should not begin with blame. Leaders should investigate whether the spreadsheet is faster, contains information the system lacks, protects users from a broken workflow, or supports a local need ignored by the design. The old behaviour is evidence about the system.
Decision Framework
For each transformation, test five layers.
Strategic outcome: What measurable enterprise or mission result should improve?
Technical change: What process, technology, asset or structure is being introduced?
Behavioural change: What must people start, stop or do differently for the outcome to occur?
System conditions: Which incentives, roles, policies, skills, information flows and management routines must support the new behaviour?
Reinforcement: What will prevent regression when operational pressure rises?
A transformation is not fully designed until all five layers are credible.
From Strategy to Execution
Immediate action: map the current and future operating system around each major transformation. Identify specific restraining forces rather than describing stakeholders as generally resistant.
Medium-term capability: shift governance from milestone-only reporting toward adoption and benefit evidence. Track whether new behaviours are actually occurring, whether old processes have been retired and whether operational performance is stabilising in the new state.
Long-term strategic positioning: build change capability into line management. Permanent leaders should own the future operating model rather than receiving it passively from a temporary project team. Project completion should include transfer of capability, measures and accountability to the organisation that will live with the change.
Related article: Authority Can Produce Compliance. Leadership Must Create Commitment.
Related article: High-Performing Teams Are Designed Before They Are Led
Signals to Monitor
Watch for parallel use of old and new systems, benefits that remain "forecast" long after go-live, repeated requests for refresher training without behavioural improvement, workarounds, unretired legacy processes, declining trust in program messages, and local managers quietly reversing changes under performance pressure.
Positive signals include faster decisions in the new model, measurable decline in legacy work, stronger ownership by operational leaders, increasing competence, fewer exceptions and benefits that appear in business performance rather than only project reports.
Questions for the Leadership Team
- Which parts of this transformation are genuinely changing structure, technology and people together?
- What current behaviour are we trying to stop, and what makes that behaviour rational today?
- Which restraining forces have we removed rather than merely countered with more pressure?
- Who owns the benefits after the project team leaves?
- What will happen during the first major operational crisis after implementation: will the organisation maintain the new model or revert?
- Which legacy system, process or measure must be retired for the change to become real?
Closing Perspective
Transformation does not occur because a new solution exists. It occurs when the surrounding system makes the new way of working understandable, possible and sustainable. Leaders who govern only the technical implementation may deliver the project they approved while missing the organisational future they intended to create.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.