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

When a transformation starts to wobble, most organisations add governance. More meetings, more detailed reports and another escalation route.

It feels like control. Often it just means the same problem gets discussed in more rooms.

Most stalled programmes have already spotted the problem. What they're missing is someone making the decision to fix it.

What we'll cover

• How governance turns into a reflex

• Why slow decisions are a hidden delivery risk

• Why too many voices slow things down

• How to write papers that get decisions made

• How to design governance around decisions

• Signs your governance is slowing delivery

The governance reflex

Governance matters. Big investments need oversight and risks need managing. The trouble starts when governance becomes the answer to every problem:

• A milestone slips, so weekly reporting starts

• A dependency causes delay, so a working group is set up

• Leaders lose confidence, so another layer of assurance is added

Each step makes sense on its own. Together they mean an issue can move through working groups, programme boards and executive committees without anyone resolving it. Every meeting reviews it and asks for more analysis. Meanwhile the delivery team works around it.

Slow decisions are a hidden delivery risk

A decision delayed by six weeks rarely affects just one thing. It can:

• stop work further down the line

• leave teams planning around guesses

• use up contingency

• create uncertainty in other programmes

When the decision finally lands, work may need redoing and the options may have narrowed.

Most dashboards track milestones, spend, risks and RAG status. Few show how long decisions have been open or what they're holding up. Leaders see the slippage without seeing the cause.

Treat big decisions like milestones. Give each one an owner, a deadline and a clear statement of what happens if it slips. Postponing is a decision too.

Too many contributors, no clear decision-maker

Transformation crosses functions. A change to a commercial process might involve Sales, Finance, Technology, Legal and Operations. Everyone has a valid view, so organisations assume everyone has to agree.

That's how committees end up unable to finish a discussion. A good decision process separates three roles:

• the people who give input

• the people whose agreement is genuinely required

• the one person who decides

Making those roles explicit forces an answer to a question organisations often avoid: who can end this discussion?

The escalation trap

Escalation is right for decisions with big financial, strategic or regulatory consequences. It becomes a problem when routine choices keep travelling up the hierarchy because nobody lower down has the authority to make them.

Meeting cycles make it worse. An issue raised just after a monthly steering committee can wait weeks, then get referred on to the next forum.

Set clear thresholds based on value, risk, customer impact and knock-on effects. Then decide things at the lowest sensible level and save executive time for the calls only executives can make.

Write papers that ask for a decision

Many governance papers bury the decision under pages of background and status. Executives spend the meeting working out what they're being asked.

A good decision paper:

• states the decision needed up front

• explains why it's needed now

• sets out the realistic options and what each one means

• gives a recommendation

• shows the cost of waiting

Match the depth of analysis to the stakes. A big, irreversible choice deserves detail. A decision you can adjust later doesn't. More analysis can become a respectable way to avoid making the call.

Not every decision needs a meeting

If the accountable executive has the information and the authority, they can decide outside the meeting cycle and record it at the next one.

Formal forums should focus on what needs collective discussion: competing priorities, big changes to investment, cross-functional conflicts and major risks.

It also helps the relationship between programmes and leadership. Delivery teams don't have to wait for a meeting to ask for a decision, and executives know when their input is genuinely needed.

A decision only counts once delivery changes

Some programmes lose time even after a decision has been made. Common reasons:

• the decision was recorded too vaguely

• different functions interpret it differently

• the plan, budget or design isn't updated to reflect it

• someone who missed the meeting reopens it next time

Translate every material decision into delivery consequences straight away. The people responsible for acting on it need to understand both the decision and the reasoning behind it. A decision log on its own isn't enough. Someone needs to check the decision actually removed the blocker.

Design governance around decisions

Most governance models start with a hierarchy of meetings. Start with the decisions delivery needs instead:

• Which choices come up again and again?

• Where should authority sit?

• How fast does each type of decision need to happen?

• What evidence is needed, and from whom?

Then design forums around those needs. If a meeting can't say what decision it exists to make, question whether it should exist.

The best measure of governance is whether decisions keep pace with delivery. For more on spotting problems early, read The Most Dangerous Transformation Status Is Green.

Signs your governance is slowing delivery

Most organisations can spot these within a few weeks of looking:

• the same issue appears on the agenda of several forums

• papers come back for more analysis more than once

• decisions wait for the next scheduled meeting

• executives spend most of their meetings receiving updates

• delivery teams plan around assumptions while they wait

Each one is a sign that governance is reviewing problems without resolving them.

Frequently asked questions

What is decision latency?

Decision latency is the time between a decision becoming necessary and it being made. In transformation programmes it's one of the most common causes of delay, and one of the least measured.

How do you speed up decision-making in a transformation programme?

Make it clear who decides, set thresholds for what needs escalating, write papers that lead with the decision and track open decisions like milestones, with an owner, a deadline and a cost of delay.

How many governance forums does a transformation need?

As few as possible. Each forum should have a clear purpose and the authority to act. If a meeting can't explain what decision it exists to make, it probably shouldn't exist.

What role does a TMO play in decision-making?

A Transformation Management Office (TMO) tracks material decisions, challenges those that stay open too long and checks that agreed decisions actually change what happens in delivery.

How Condor helps

We design and run transformation governance that helps delivery move. That means clear decision rights, visible costs of delay and decisions that turn straight into action. Past work includes £18m of in-year EBITDA impact for a UK telecoms client.

If your programme has more meetings than decisions, give us a call. Get in touch

When Execution Matters, We Deliver.