A governance forum creates value only when it improves the quality, clarity or pace of a decision.
When a transformation encounters control problems, the instinctive response is often to add governance. A new committee is established. Reporting becomes more frequent. Attendance lists grow. Templates become more detailed.
The result can be more oversight without more control.
Governance is not the number of forums around a programme. It is the system through which authority is allocated, evidence is brought to decision-makers, conflicts are resolved and accountability is maintained. Meetings are one mechanism within that system. They are not the system itself.
For Boards, CEOs and transformation sponsors, this distinction matters because poor governance consumes scarce leadership attention while allowing important decisions to remain unresolved.
Start with the decisions, not the committees
The most reliable way to design governance is to identify the decisions required to deliver the transformation. These will vary by mandate, but they commonly include decisions about scope, priorities, service or operating-model design, standards, investment, resources, benefits, risk acceptance and intervention in underperformance.
Each decision should be defined with sufficient precision to allocate it. “Strategic decisions” is too broad. “Approve a material change to the target operating model” or “release funding for the next mobilisation stage” is specific enough to assign authority and evidence.
Only after the decisions are clear should forums be designed. This reverses a common pattern in which existing committees are retained and transformation decisions are distributed among them, regardless of fit.
Place authority at the right level
Decision rights determine both pace and control. If authority sits too high, senior forums become congested and operational decisions wait for attention. If it sits too low, teams may make choices with enterprise consequences they are not positioned to assess.
A practical allocation test considers four factors:
- Materiality: the scale and reversibility of the consequence
- Interdependence: the number and significance of parties affected
- Expertise: where the relevant knowledge sits
- Accountability: who will carry the outcome after the decision
The right level is not always the most senior one. It is the lowest level that has the authority, perspective and accountability required to make the choice safely.
Delegation should be explicit. A forum should know which decisions it owns, which it recommends and which it must escalate. Without this distinction, discussion can be mistaken for approval.
Define the evidence required
Decision quality depends on the evidence brought into the room. Yet executive packs often mix status updates, analysis and recommendations without making the decision request clear.
A disciplined decision paper should answer a small set of questions:
- What decision is required, by whom and by when?
- What problem or opportunity makes the decision necessary?
- Which viable options have been considered?
- What are the implications and trade-offs of each option?
- What is recommended, and why?
- Which risks, dependencies and implementation requirements follow?
The level of analysis should be proportionate to the decision. Not every choice requires a large pack. A concise, well-framed paper is often more valuable than extensive material that transfers the work of synthesis to the executive audience.
Make accountability visible after the decision
Governance frequently concentrates on reaching a decision and gives less attention to what happens next. Decisions are recorded, but actions are fragmented, assumptions are forgotten and the connection to outcomes weakens.
Every material decision should result in an explicit record of ownership, expected outcome, implementation dependencies and review point. This is more than an action log. It preserves the logic of the decision and creates a basis for assurance.
When circumstances change, leaders can then distinguish between a failure to implement the decision and a legitimate need to revisit its assumptions. Without that record, decisions are reopened through organisational memory and stakeholder influence rather than evidence.
Design escalation as a normal control
In complex transformation, issues will cross boundaries and exceed delegated authority. Escalation is therefore not evidence that governance has failed. It is a planned mechanism for resolving what cannot be resolved at the delivery level.
The design should define escalation triggers such as impact on critical outcomes, decision delay beyond an agreed threshold, unresolved cross-entity dependency, material deviation from the approved model or risk outside tolerance.
It should also define the route and response time. An escalation that enters a senior forum’s ordinary calendar may arrive too late to protect delivery. Some decisions require an exception process between meetings.
Healthy governance makes escalation safe and useful. Teams should not be rewarded for presenting an artificially stable picture or penalised for exposing a problem early.
Separate oversight from delivery
Boards and executive committees need assurance, but they should not become operational programme teams. The distinction lies in the questions they ask.
Delivery forums ask: What action is required, who will complete it and by when?
Executive governance asks: Is the transformation still aligned with strategic intent? Are material risks understood and owned? Are critical decisions being made at pace? Is the operating model viable? Are benefits still credible? Does management need intervention or support?
Board oversight asks: Is the transformation within mandate and risk appetite? Does the executive team have control? Are the assumptions supporting expected outcomes still valid? Is the information presented sufficient for assurance?
When these layers are blurred, senior leaders become drawn into task management while strategic risks receive insufficient attention.
Measure the performance of governance
Governance itself should be tested. Attendance and meeting frequency say little about whether the system works.
More useful indicators include decision cycle time, proportion of decisions made at the intended level, frequency with which decisions are reopened, age of material escalations, implementation of agreed decisions and concentration of unresolved dependencies.
Qualitative evidence matters as well. Do papers frame genuine options? Are dissenting views surfaced? Can accountable executives obtain timely resolution? Does reporting change the conversation or merely document it?
These questions reveal whether governance is enabling delivery or becoming another layer through which information must pass.
A five-part governance design
An effective governance system can be described through five connected components:
- Decisions: a clear inventory of the choices that matter to delivery
- Rights: explicit authority to decide, recommend, advise and execute
- Evidence: proportionate information and a clear recommendation
- Cadence: timing determined by decision need, not calendar habit
- Accountability: ownership and follow-through visible after approval
The system should remain as simple as the mandate allows. Complexity may be unavoidable in the stakeholder environment. It should not be recreated unnecessarily in the governance design.
The aim is disciplined flow: evidence reaches the right authority, a decision is made in time and responsibility moves into implementation without ambiguity.
Executive questions
- Which important transformation decision is currently circulating through discussion without a clear owner?
- Where is senior leadership attention being used for status review rather than decision or assurance?
- Which escalation would arrive too late if it waited for the next scheduled forum?
JP Associates helps leaders review governance, clarify decision rights and establish an executive cadence focused on delivery rather than reporting volume.