Governance Lessons From Organisational Change Programs

Transformation programs are usually governed through plans, milestones, budgets and risk reports. These controls are necessary, but they tend to focus attention on the delivery of the program. Boards also need to understand what the program is doing to the institution while delivery is under way.

Change alters more than a process or technology. Responsibilities move, familiar routines disappear and people must interpret new expectations while continuing to operate the existing organisation. During that period, formal structures and practical behaviour can separate. Staff create workarounds, decisions take unfamiliar routes and accountabilities that looked clear in the design become uncertain in use.

A dashboard may show that training has been completed and a system has gone live. Neither measure establishes that people are able or willing to use the new arrangements as intended. Implementation records whether an intervention occurred. Adoption concerns whether behaviour changed. Renewal asks whether the institution can sustain and improve the change after the formal program ends. Treating these as the same outcome gives a board an incomplete view.

The pressure of delivery can deepen the problem. Once time and reputation have been committed, unfavourable information becomes harder to surface. Teams may describe a workaround as temporary because acknowledging its significance would challenge the plan. Leaders may interpret resistance as a communication issue when it reflects a genuine design flaw or an unresolved conflict between operational demands and the proposed change.

This is not an argument for boards to supervise project detail. It is an argument for governing the conditions on which transformation depends. The board should know who can make difficult trade-offs, how consequences for customers and staff are being identified, and whether assurance reaches beyond the program's own reporting line. It should also understand which existing pressures may defeat the intended behaviour once intensive implementation support is withdrawn.

Different questions are useful at different stages. Before implementation, the board can test whether the institution is ready, whether accountabilities are credible and whether the change competes with other demands. During implementation, it can look for emerging behaviour, uneven adoption and assumptions that no longer match experience. After the formal program, it can ask what capability remains, what has reverted and which benefits have become part of normal operations.

The quality of information matters throughout. Reports should distinguish activity from effect and explain exceptions rather than absorb them into an overall status. Evidence from operational teams, customers and affected stakeholders can test the account provided by the program. Where measures remain uncertain, that uncertainty should be visible rather than converted prematurely into a confident rating.

Organisational change is often described as a temporary journey from a current state to a future state. In practice, the institution continues to make decisions, respond to pressure and form new habits throughout the transition. Governance must remain connected to that lived organisation, not only to the architecture of the program.

A transformation can meet its delivery milestones and still leave the institution less capable, more dependent or less trusted. Conversely, a program that adjusts its plan in response to evidence may produce a stronger result. The board's responsibility is to see the difference and ensure that completion is not mistaken for renewal.