A transformation is not complete when the new system exists; it is complete when the organisation consistently behaves in ways that make the new system valuable.
Transformation governance is usually strong where work can be counted. Executives can see whether a platform has been configured, whether a process has been documented, whether a facility has been commissioned or whether a new structure has been announced.
The harder question is whether the organisation now operates differently.
That distinction matters because many strategic benefits depend on behaviour. A new planning system creates little value if managers continue making decisions outside it. A new operating model is cosmetic if decision rights remain unchanged in practice. A centralised procurement process does not improve leverage if business units keep bypassing it. A new safety process does not improve control if supervisors reward output at the expense of compliance.
Transformation therefore creates two systems at once: a formal system of processes, technology and structures, and a behavioural system of choices, incentives, habits and leadership signals.
The second is often less visible and more decisive.
The Strategic Context
Accenture's journey-management material treats transformation as more than systems implementation and communications. Its roadmap approach includes the identification of behaviours required from management and the wider organisation. It describes leaders aligning around measurable outcomes and taking explicit responsibility for what success means.
The 2018 UK Government project-delivery standard reaches the same issue through its change-management provisions. It states that programs and projects should define a future state, assess the current state of target groups, prepare and support organisations and individuals to change their approach and behaviours, assess readiness and monitor whether new practices revert after implementation.
These sources differ in context, but they point to the same governance issue: implementation is not equivalent to institutionalisation.
The executive team must govern the distance between the formal future state and the lived operating reality.
What Leaders Commonly Misread
The first mistake is to treat behaviour as a communications problem.
People do need to understand why a transformation is happening, but understanding is not the same as changing. If a new process conflicts with performance incentives, existing authority, workload, customer demands or local measures, communication alone will not resolve the system.
The second mistake is to assign behavioural change entirely to a change-management team.
Change specialists can design interventions, assess readiness and support adoption. They cannot substitute for line leadership. Employees learn what the transformation really means by observing which decisions executives make, which trade-offs managers accept and what is rewarded when the new model conflicts with the old one.
The third mistake is to measure participation instead of adoption.
Training completion, communication reach and attendance can be useful leading indicators. They do not prove that the organisation is operating differently. The stronger measures are behavioural and operational: whether decisions are made through the new governance path, whether processes are followed without workarounds, whether expected data is used, whether new roles exercise their intended authority and whether old practices are disappearing.
The fourth mistake is to assume that behaviour stabilises after go-live.
GovS 002 explicitly warns against reversion. This is strategically important. When implementation support withdraws, pressure rises and leaders turn their attention elsewhere, the organisation can drift back toward familiar practices.
Reframing the Issue
Leadership behaviour is part of the transformation architecture.
That means it should be defined with the same seriousness as technology requirements, process design and organisational structures.
A useful distinction is between declared design and operating truth.
Declared design says that portfolio decisions will be prioritised against strategy. Operating truth is revealed when a politically sponsored project competes for scarce capacity.
Declared design says that product teams have decision authority. Operating truth is revealed when a senior functional leader overrides them.
Declared design says that data will be a common enterprise asset. Operating truth is revealed when functions keep private spreadsheets because the official source is inconvenient.
Transformation governance should therefore ask not only whether people have adopted the new process, but whether leadership choices reinforce or contradict the future state.
Behaviour Must Be Specific Enough to Govern
Generic behavioural aspirations are difficult to use.
"Collaborate more."
"Be accountable."
"Think strategically."
"Embrace change."
These statements sound positive but do not tell people what different action is required.
Accenture's practitioner material describes defining specific behaviours and asking leaders to reflect on where they sit against those expectations. The deeper principle is to make the behavioural requirement observable.
If a transformation seeks integrated planning, a leadership behaviour might be: do not commit local resources to major initiatives before cross-functional capacity is reviewed.
If the objective is faster decision-making, a behavioural requirement might be: decisions inside agreed tolerances remain with the accountable team rather than escalating for unnecessary approval.
If the objective is a common operating model, a behavioural requirement might be: local deviations require an explicit business rationale rather than becoming the default response to inconvenience.
The behaviour becomes governable because leaders can see whether it is occurring.
Accountability Must Connect to Outcomes
One of the strongest ideas in the Accenture source is leadership alignment around a shared definition of success. Metrics and accountability create what the paper calls a collective sense of responsibility.
The executive value is not the phrase itself. It is the prevention of retrospective ambiguity.
Transformations often fail into a fog of different interpretations:
- technology says the system was delivered;
- operations says it was not practical;
- finance says savings were expected elsewhere;
- business units say they were never accountable for adoption;
- the program says benefits were transferred to the business;
- leadership says the outcome was not what it intended.
Clear outcome accountability reduces this escape route.
A transformation should define who owns the future-state outcome, not merely who owns each delivery workstream. That owner needs authority to resolve cross-functional barriers and enough visibility to know whether operational behaviour is moving toward the intended state.
Related article: Benefits Are Realised in Operations, Not in the Program Office
Decision Framework
Leaders can test behavioural governance through five layers.
| Layer | Governance test |
|---|---|
| Outcome | What business result must become consistently true? |
| Behaviour | What will leaders and employees do differently to create that result? |
| System | Which process, incentive, authority or tool must support the behaviour? |
| Evidence | What observable measure will show the behaviour is occurring? |
| Reinforcement | What will happen when old behaviour reappears under pressure? |
This prevents the common error of trying to change behaviour without changing the environment that produces it.
For example, if leaders want project teams to surface risk earlier but penalise teams whose dashboards turn amber, the behavioural message and management system conflict. If leaders want cross-functional optimisation but bonuses remain entirely local, collaboration depends on goodwill rather than design.
Behavioural governance therefore reaches into incentives, decision rights, performance measures and the routines of management itself.
From Strategy to Execution
Immediate action should begin with the few behaviours that are essential to the transformation's economics or operating logic.
Do not create a long cultural wish list. Identify the behaviours without which the future state cannot work.
For each one, ask:
- Which leaders must model it first?
- What existing incentive or process pushes people in the opposite direction?
- What decision would prove leadership is serious?
- How will adoption be observed in real work?
- What reversion signal should trigger intervention?
In the medium term, connect transformation governance to operational measures. If the new operating model requires faster cross-functional decisions, measure decision latency and escalation patterns. If a new system is intended to become the source of truth, track the persistence of parallel tools and manual reconciliations. If new roles are expected to own benefits, test whether they control the operational levers required to create them.
The governance forum should distinguish implementation complete from behaviour embedded.
Longer term, transfer ownership from the transformation structure into business management. A behaviour that survives only while the program team is present is not yet organisational capability.
Related article: Build Capability Before Strategy Depends on It
Signals to Monitor
Behavioural adoption may be weaker than reported when:
- training completion is high but workarounds remain common;
- managers continue seeking approvals above their formal authority;
- local spreadsheets or shadow processes remain necessary for daily work;
- performance measures reward the old operating model;
- executive exceptions repeatedly undermine the new governance design;
- new roles exist on organisation charts but lack practical authority;
- business units describe the transformation as something the program is doing to them;
- benefits depend on heroic individuals rather than repeatable management routines;
- old processes return after implementation support reduces.
These signals do not mean the transformation must stop. They mean the management system has not yet stabilised around the desired behaviour.
Questions for the Leadership Team
- Which three behaviours are indispensable to the future-state operating model?
- What do leaders currently do that contradicts those behaviours?
- Which incentives, measures or approval structures still reward the old model?
- How will we distinguish communication reach from genuine adoption?
- Who owns the outcome after the transformation team withdraws?
- What evidence would show that the organisation is reverting?
- What difficult executive decision would demonstrate that the new behaviour is real?
Closing Perspective
Transformation does not become durable when people have heard the message. It becomes durable when the management system makes the new behaviour normal.
Technology, processes and organisation charts establish possibilities. Leadership choices determine which possibilities become operating reality.
For executives, the implication is demanding but practical: govern behaviour as part of the transformation design. Define it, make it observable, align the surrounding system and keep measuring after implementation. Otherwise the organisation may complete the change program while quietly preserving the conditions that made change necessary in the first place.
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.