Essay: Why Simple Changes Become Programmes

The forum finished its meeting. The change did not. The company had made coordination easier to buy than authority was to move.

Marianne's decision made more sense once Felix understood that slide 37 had asked several sponsors to surrender unspecified rights. A new forum preserved their budgets, reporting lines and professional territories. Moving authority would give one owner the ordinary decision and remove another's expected say at once; the benefit would arrive gradually through later changes.

Sometimes caution is rational because the boundary is unclear, reversal is costly or the last reorganisation damaged trust. A change trace and co-change map can test that. Here the team had sold more capacity to exchange information while leaving its cause in place.

Roles form around the joins. Programme managers reconstruct a whole from partial plans, architects negotiate among systems whose owners cannot change together, and consultants give the combined account consistent fonts. Their competence makes the fragmented system survivable. Budget, status, safety from blame and further work supply enough incentive without a private agreement.

The company can still complete every performance review. On a successful programme, several leaders can describe their contribution. On a failed one, each can identify a dependency outside their control. Both accounts may be accurate. Neither, on its own, tells the company whom to promote, whom to replace or whose judgement made the difference.

A person who commits to a change and states what would count as failure gives the company something that can prove them wrong. A person whose contribution is described after the result has more room. If advancement rewards the safer account, the next allocation of authority favours people practised at producing one. The damage reaches beyond this year's delivery: the company becomes less able to recognise and retain the people who could improve it.

Fragmented authority generates alignment work, which helps the design survive.

A six-step loop begins with authority and state divided by function. A complete outcome crosses several owners, ordinary change requires alignment, coordination becomes leadership and institutional value, moving rights creates concentrated losses, and the approvable answer adds coordination, making the original design survivable. Faster local production sends more work into the same boundary. A dashed escape moves ordinary rights, state and capability around a complete process.

Employment is immediate and personal. A completed improvement benefits customers and shareholders whose complete outcome no participant owns. Delay disperses across calls, incidents, rework and missed opportunities, while repair begins with a visible argument about somebody's current authority. People can work punishing hours inside a system that still cannot complete an ordinary change.

The five-key door

Imagine an office door fitted with five locks. Facilities holds one key, Security another, Finance a third, the floor manager a fourth and the landlord the fifth. Every holder is diligent. Four usually arrive on time. The room still opens only when all five are present.

Five locks make sense on a vault if each protects a different interest. On the door to an ordinary meeting room they create a daily ceremony whose failure belongs to nobody. Management can add a key coordinator, publish attendance statistics and ask late holders for improvement plans. The door remains a five-key door.

The mileage change worked that way. Underwriting answered the eligibility question in two days. Data confirmed the field in three. Architecture reviewed the route within its service level. Operations changed the adviser procedure.

Release found a slot the following week. No holder behaved unreasonably, but the work moved serially because a clarification from one changed the paper sent to the next. A returned question missed the release slot and added another week. The elapsed delay was a property of the door, not the punctuality of one keyholder.

The design question asks which locks protect independent interests and which exist because the room was divided among five departments. Genuine protections remain as explicit constraints. The other keys move with the ordinary right to use the room.

Almost every local account can still close: the consultant delivers, the executive governs, the function meets its target and the programme reports progress. Customers and shareholders need those successes to join.

Some seams are real. Alignment remains necessary during incidents and through changeovers because independent institutions must sometimes consent and conflicting interests must be settled politically. The anti-pattern begins when a standing coalition is needed to make one ordinary outcome decidable.

The insurer paid by placing meetings at the joins and translations in the systems. With repeated negotiation, the meeting becomes the API. The word

delivered then covered approval, build, deployment and use. Temporary committees survived because nobody owned their retirement.

The test is small. Choose thirty consecutive ordinary changes to one customer outcome. Record every required holder and every wait. Ask which holders changed the decision or protected a distinct institutional interest. If the same work repeatedly crosses the same ordinary approvals, the company is buying alignment from a boundary it has declined to design.

Move nothing on familiarity alone. A flat relationship between holders and delay weakens the diagnosis. A right that protects a separate interest may deserve to stay. The five-key door is useful only when the company is willing to ask which keys belong to the vault and which were fitted to an ordinary room.