Governance Should Be Designed Around Decisions, Not Meetings

Transformation governance often starts with a calendar.

A steering committee is created.

A monthly meeting is scheduled.

A dashboard is prepared.

Status reports are circulated.

Issues are reviewed.

Actions are recorded.

Then everyone leaves with another meeting on the calendar.

The transformation has governance.

But does governance have a purpose?

A governance forum should exist because a particular set of decisions needs authority, evidence and accountability.

Governance should be designed around decisions, not meetings.

A meeting is not governance

A meeting creates a forum.

Governance creates a decision system.

The distinction matters.

A steering committee might receive extensive reporting without making a single meaningful decision.

A programme might remain red for months while the same issue appears in successive status reports.

A major dependency might sit between business and technology because neither side has clear authority.

A decision might move from one committee to another because nobody knows who owns the final call.

The organisation is meeting.

The transformation is still waiting.

Governance exists to prevent this.

Start with the decisions

Before creating a governance forum, identify the decisions requiring authority.

For a transformation, those decisions might include:

Priorities

Which initiatives receive scarce capacity?

Investment

Where should funding increase, decrease or stop?

Scope

Which outcomes and capabilities belong inside the transformation?

Trade-offs

Which competing priorities take precedence?

Dependencies

Which decisions require coordination across programmes or business units?

Risk

Which risks require executive intervention?

Value

Are expected benefits still credible?

Direction

Should the transformation continue with the current approach?

The governance structure should follow the decision set.

Not the other way around.

Every decision needs an owner

A decision without an owner becomes a discussion.

A decision with multiple owners becomes a negotiation.

A decision with unclear authority becomes an escalation.

Effective governance makes decision rights explicit.

For every significant transformation decision, leadership should know:

Who decides?

Who provides input?

Who needs to be informed?

What evidence is required?

What threshold triggers escalation?

Who owns the consequence?

The objective is not to create another responsibility matrix.

The objective is to remove ambiguity.

When authority is clear, decisions move closer to the point where the relevant information exists.

When authority is unclear, decisions move upwards.

The executive team becomes the escalation point for problems that should have been resolved elsewhere.

Not every decision belongs with executives

Executive governance does not mean executives decide everything.

Some decisions belong with the transformation leadership team.

Some belong with programme leaders.

Some belong with business owners.

Some belong with delivery teams.

The executive role is to own decisions where enterprise-level trade-offs, investment, risk or strategic direction are involved.

A useful principle is:

Push decisions down until the risk, value or consequence requires a higher authority.

This creates speed without removing control.

The executive forum should therefore focus on decisions where enterprise accountability matters.

Routine delivery decisions should not consume executive attention.

Information is not a decision

Governance meetings often spend too much time receiving information.

A programme presents progress.

Another presents risks.

Another presents financials.

Another presents dependencies.

The meeting ends.

The information was useful.

The governance was weak.

Information becomes valuable when someone knows what decision the information is intended to support.

Every material item entering an executive governance forum should therefore answer:

What decision is required?

Why is the decision required now?

What evidence supports the decision?

What options exist?

What happens if we do nothing?

Who owns the decision?

If no decision is required, the item might belong in a dashboard rather than a governance meeting.

Escalation should be designed, not improvised

Escalation often becomes a sign of failure.

A delivery team encounters a problem.

The issue moves upwards.

Another meeting is scheduled.

More people become involved.

The original decision remains unresolved.

A better governance system defines escalation before problems occur.

For example:

Delivery team

Resolves issues within agreed authority.

Programme leadership

Resolves cross-workstream dependencies and material delivery trade-offs.

Transformation leadership

Resolves portfolio-level conflicts, capacity constraints and significant value or risk issues.

Executive leadership

Resolves decisions involving strategic direction, major investment, enterprise risk or competing business priorities.

The exact thresholds will vary.

The principle should not.

Escalation should move a decision to the right authority, not simply move a problem to a more senior meeting.

Governance needs evidence

A governance forum should not operate on presentation quality.

A programme marked green does not prove healthy transformation.

A completed milestone does not prove business progress.

A budget variance does not explain value.

A benefits forecast does not establish validated value.

Governance needs a common evidence base.

For each major decision, leadership should have access to the information required to understand:

Current position

What is happening?

Expected position

What should be happening?

Variance

Where is reality different?

Cause

Why has the difference occurred?

Impact

What does the difference mean for outcomes, value, risk or capacity?

Decision

What action is required?

This turns reporting into decision support.

Governance should respond to evidence

Transformation conditions change.

A dependency appears.

A benefit weakens.

A technology assumption fails.

A capability takes longer to establish.

A new business priority emerges.

A delivery team identifies a better approach.

Governance should respond.

A fixed governance structure often treats change as an exception.

A useful governance system treats adaptation as part of its purpose.

The forum should therefore have explicit triggers for intervention.

For example:

Value falls below an agreed threshold.

A critical dependency threatens an outcome.

A decision exceeds delegated authority.

A major assumption changes.

Capacity becomes insufficient.

Risk moves beyond agreed tolerance.

The trigger should lead to a decision.

Not another status update.

Governance should evolve

Transformation governance should not remain identical from beginning to end.

Early transformation often requires tighter executive involvement.

As capabilities mature, more decisions should move into the operating organisation.

As delivery expands, governance might need broader representation.

As the transformation stabilises, some forums should disappear.

The governance structure therefore needs periodic review.

Ask:

Which decisions still require this forum?

Which decisions should move closer to delivery?

Which decisions have become routine?

Which new decisions have emerged?

Where are decisions still taking too long?

A governance forum should have to earn its place.

The executive test

Take your next transformation governance meeting.

Look at the agenda.

For every item, ask:

What decision is required?

Then ask:

Who owns the decision?

Then:

What evidence supports the decision?

Then:

What happens if we do not decide?

If most items do not lead to a decision, the meeting is probably functioning as a reporting forum.

If decisions repeatedly leave the meeting unresolved, decision rights are probably unclear.

If the same issue appears month after month, the governance mechanism is probably not working.

If executives spend most of the meeting receiving information, the governance design needs attention.

From meetings to control

Effective transformation governance creates four conditions:

Clear decisions

Everyone knows what requires a decision.

Clear authority

Everyone knows who decides.

Relevant evidence

Decision makers receive information linked to the decision.

Clear intervention

The organisation knows what happens when evidence moves beyond agreed thresholds.

This is governance as a control mechanism.

Not governance as meeting administration.

The distinction becomes especially important as transformation portfolios grow.

More initiatives create more dependencies.

More dependencies create more trade-offs.

More trade-offs create more decisions.

The answer is not more meetings.

The answer is better decision architecture.

The EOS™ Control Loop starts with:

LEAD → DIRECT → GOVERN → EXECUTE → ENABLE → MEASURE → EVOLVE

Governance sits inside the loop.

Leadership establishes direction.

Governance converts direction into controlled decisions.

Execution produces evidence.

Measurement exposes what changed.

Evolution feeds new decisions back into the system.

The objective is not to govern more.

The objective is to make the decisions required to keep transformation aligned, moving and accountable.

And once governance is designed around decisions, another question becomes unavoidable:

Who is responsible for keeping those decisions connected across the transformation?