Transformation Doesn't Need More Governance. It Needs Better Decisions.

When transformation delivery becomes uncertain, organisations often respond by increasing governance. More meetings are scheduled, reporting becomes more detailed and additional escalation routes are introduced.

The intention is understandable. Leadership wants greater visibility and confidence that the programme is under control. More governance provides neither.

In many organisations, there is no shortage of forums in which transformation is discussed. The problem is the time taken to reach decisions, the lack of clarity over who is authorised to make them and the failure to translate agreed decisions into action.

A programme can therefore be governed extensively while making very little progress. Few dashboards show the age of open decisions or the work they are holding up, so the cost of waiting stays hidden.

The governance reflex

Governance is an essential part of complex transformation. Significant investment requires oversight, risks need to be managed and executives must understand whether delivery remains aligned with the organisation's priorities. The difficulty begins when governance becomes the standard response to every delivery problem.

A programme misses a milestone, so weekly reporting is introduced. A dependency creates delay, so a cross-functional working group is established. Leadership lacks confidence in the status, so another layer of assurance is added.

Each response appears sensible in isolation. Collectively, they can create an environment in which the same issue moves through working groups, programme boards, portfolio forums and executive committees without being resolved.

Every meeting reviews the issue. Each group asks reasonable questions, requests further analysis or refers the matter elsewhere. Meanwhile, the delivery team continues working around an unresolved decision. The organisation isn't ignoring the problem. It is processing it repeatedly.

This is the difference between governance designed to provide oversight and governance designed to enable execution. The first ensures that issues are visible. The second ensures that somebody decides what to do about them.

Decision latency is an execution risk

Transformation continually generates choices about scope, sequencing, investment, design, people, technology and risk. Some decisions are strategic and irreversible. Others are relatively operational. What they have in common is that delivery depends on them being made at the right time.

A decision delayed by six weeks rarely affects only the matter under discussion. It can stop downstream work, leave teams planning around assumptions, consume contingency and create uncertainty across dependent programmes.

When the decision eventually arrives, work may need to be revised or repeated. Resources may no longer be available, supplier dates may have moved and the original range of options may have narrowed.

The cost of this delay is real, but it is rarely measured. Most transformation dashboards report milestones, expenditure, risks, issues and RAG status. Few show the age of unresolved decisions, the value they are holding up or the consequences of waiting.

Leadership therefore sees the eventual schedule slippage without seeing the accumulated decision latency that caused it.

Organisations serious about execution should manage material decisions with the same discipline applied to milestones and risks. Each should have a clear owner, a deadline and an explicit explanation of what happens if it isn't resolved in time. Postponement is itself a decision, and its consequences are rarely made visible.

Too many contributors, no clear decision-maker

Decision delay is often blamed on insufficient information or limited executive availability. Both can be genuine constraints, but the underlying problem is frequently unclear authority.

Transformation crosses organisational boundaries. A decision about a new commercial process may affect Sales, Finance, Technology, Legal and Operations. Each function has a legitimate interest and relevant expertise. Because several executives need to contribute, organisations often assume that they must all agree.

The resulting committees can be highly collaborative but structurally incapable of ending the discussion. Each participant can identify an additional concern, request further evidence or protect the interests of their own function. Nobody is clearly accountable for weighing those perspectives and making the final choice.

Consultation is necessary. Consensus isn't always possible, and it isn't always desirable.

An effective decision process distinguishes between the people who provide input, those whose formal agreement is genuinely required and the individual authorised to decide. Making those roles explicit forces the organisation to answer a question it often avoids: who has the authority to end this discussion?

Without that clarity, adding more senior stakeholders is unlikely to produce a better decision. It may simply increase the number of people capable of delaying it.

The escalation trap

Many transformation governance models compensate for unclear authority through escalation. When an issue can't be resolved at one level, it moves to the next forum. If that group can't resolve it, the matter progresses again until it reaches somebody senior enough to intervene.

Escalation is necessary for decisions with material financial, strategic or regulatory consequences. It becomes inefficient when routine delivery choices repeatedly travel through the hierarchy because the people closest to the issue haven't been given sufficient authority.

The timing of governance forums compounds the problem. An issue identified shortly after a monthly steering committee may wait several weeks for formal consideration. The committee then requests additional information or refers it to an executive forum taking place later in the month. By the time leadership makes the decision, the programme may have carried the consequences through an entire reporting cycle.

Effective governance should resolve decisions at the lowest appropriate level while providing a rapid route to leadership when the implications genuinely require executive judgement.

That requires clear thresholds. The financial value, strategic importance, customer impact, regulatory exposure and cross-portfolio consequences of a decision can all determine where it belongs. The objective isn't to exclude executives. It is to reserve their attention for the choices that only they can make.

Write papers that ask for a decision

Governance papers can also contribute to delay. Transformation programmes often produce lengthy documents containing detailed background, extensive analysis and several pages of status information. The actual decision may appear near the end or remain implicit. Executives spend the meeting establishing what they are being asked to decide before they can consider the merits of the decision itself.

A useful decision paper should make the required choice clear from the outset. It should explain why the decision is needed now, set out the realistic options, describe the implications of each and state the programme's recommendation.

It should also make the cost of waiting visible. If a delay will affect the critical path, increase expenditure or reduce the available options, that information belongs alongside the recommendation. Leadership should understand not only the risks associated with making the decision but also the risks associated with postponing it.

The depth of evidence should be proportionate to the consequence. A high-value, irreversible choice deserves extensive analysis. An operational decision that can be adjusted later shouldn't be held to the same standard.

Organisations sometimes seek a level of certainty that doesn't exist in transformation. Further analysis may reduce some uncertainty, but it can also become a respectable way of avoiding accountability. The purpose of a decision process isn't to eliminate uncertainty. It is to allow an accountable leader to make an informed choice despite it.

Not every decision needs a meeting

A calendar of monthly governance forums can create the assumption that decisions must wait for the relevant meeting. They shouldn't.

Where the accountable executive has the required information and authority, a decision can often be made outside the formal governance cycle. It can then be recorded and communicated through the next meeting rather than delayed until it.

Formal forums should concentrate on matters that genuinely benefit from collective discussion: competing enterprise priorities, material changes to investment, cross-functional conflicts, significant risk acceptance and challenges to the value case. Routine approvals, factual confirmations and decisions that have already been socialised shouldn't consume the same executive time.

This doesn't weaken governance. It makes the formal governance more valuable because it shifts the emphasis from receiving information to resolving material choices.

It also helps to create a healthier relationship between programmes and leadership. Delivery teams don't need to wait for a meeting to request a decision, while executives have a clearer understanding of when their intervention is genuinely required.

A decision only matters when delivery changes

Some programmes lose time even after a decision has apparently been made. The meeting concludes, minutes are circulated and the decision is entered into a log. Yet delivery teams remain unclear about what changed, which actions follow or whether every stakeholder accepts the outcome.

The decision may have been recorded too vaguely. Functions may interpret it differently, or the implications may not have been incorporated into the programme plan. Occasionally, the issue returns to the next governance meeting because somebody who wasn't present reopens the discussion.

A decision only creates value when it changes what the organisation does.

Material decisions should therefore be translated immediately into delivery consequences. Plans, budgets, designs, ownership and communications may all need to change. The people responsible for those actions need to understand both the decision and the reasoning behind it.

This is an important role for a Transformation Management Office. It should maintain visibility of material decisions, challenge where they remain unresolved and ensure that agreed outcomes are reflected across the portfolio. Simply maintaining a decision log isn't sufficient. The TMO should understand whether the decision removed the delivery constraint it was intended to address.

Governance should be designed around movement

Many governance models begin with a hierarchy of meetings: workstreams report into programme boards, programme boards report into portfolio forums and portfolio forums report into executive committees. A more effective design begins with the decisions and interventions required to maintain delivery.

The organisation should understand which choices occur repeatedly, where authority should sit and how quickly different types of decision need to be made. It should be clear what evidence is required, whose input is necessary and how unresolved matters will move without waiting for the next scheduled meeting.

Forums can then be designed around those requirements. Some will allocate investment across the portfolio. Others will resolve dependencies, challenge delivery confidence or assess whether benefits remain achievable. Each should have a defined purpose and explicit authority to act.

If a meeting can't explain what decision or movement it exists to create, its value should be questioned.

The result may be fewer meetings, but that isn't the primary objective. The objective is to shorten the distance between recognising a problem and taking action.

The real measure of effective governance

Good governance doesn't need to feel heavy. It gives the right people the right evidence at the point when a decision is required. Authority is clear, escalation is proportionate and the consequences move directly into delivery.

Its effectiveness shouldn't be judged by the volume of reporting, the seniority of attendees or the number of forums operating across the transformation. The better measure is whether decisions are being made at the pace required to protect delivery and value.

A programme doesn't benefit from having its problems discussed by increasingly senior committees. It benefits when an accountable leader makes a clear choice, accepts the consequences and enables the organisation to move.

Condor's perspective

At Condor, we design and operate transformation governance as a mechanism for execution rather than an administrative layer around it.

That means clarifying decision rights, exposing the impact of unresolved choices and connecting executive decisions directly to delivery action. Past work includes £18m of in-year EBITDA impact for a UK telecoms client.

Transformation doesn't need more places to discuss why progress has stalled. It needs leaders with the evidence, authority and discipline to decide what happens next.