There are 15 people in the steering committee.
The CIO is there. The CFO is there. The programme director is there. Three vendors are represented. The PMO has prepared 60 slides.
Nobody can approve the scope reduction.
Nobody can release the specialist architect.
Nobody can decide whether the legacy integration stays or goes.
The meeting ends with an action: “Take this offline and come back with options.”
That is not governance.
That is organised delay.
The most important chair in many transformation programmes is physically empty. It belongs to the person with the authority to make the trade-off, accept the risk and move the programme forward.
The programme does not have a meeting problem. It has a decision-rights problem.
A steering committee is not a discussion forum
A steering committee exists to do three things:
- Make decisions.
- Resolve conflicts.
- Remove obstacles.
If it only reviews status reports, records concerns and asks teams to return with more analysis, it is not steering the programme. It is observing it.
The UK Government’s Teal Book guidance on programme governance makes the point clearly: governance should define how a programme is directed, managed and controlled, including who makes decisions, who is consulted and who is informed.
The distinction matters.
Senior people in a room do not automatically create authority. A committee has authority only when its mandate, decision thresholds and escalation rights are explicit.
Otherwise, every difficult issue moves upward.
Then sideways.
Then into another workshop.
The uncomfortable truth: seniority is not the same as authority
Transformation leaders often tell me, “The right executives are already involved.”
That may be true.
It may also be irrelevant.
An executive can be senior and still lack the delegated authority to:
- Reallocate funding between business units.
- Change a contractual commitment.
- Accept a compliance or operational risk.
- Remove a resistant functional owner.
- Approve a material scope change.
- Commit scarce technical resources.
- Decide which benefits will be sacrificed to protect the critical path.
This is how decision paralysis appears in sophisticated organisations.
Everyone has an opinion. Few people have a mandate.
The programme team is then forced to seek informal permission through bilateral conversations, political escalation and carefully worded emails. Decisions are made in corridors, not in governance forums. The official minutes say “further review required”.
The delivery team knows what needs to happen. The organisation has not authorised anyone to make it happen.
Five signs that your steering committee is powerless
1. Every decision returns as an action
A difficult issue is presented.
The committee asks for three options.
The options return two weeks later.
The committee asks for an impact assessment.
The impact assessment returns.
The committee requests stakeholder consultation.
Six weeks later, the original decision is still open.
This is not prudent governance. It is decision avoidance disguised as diligence.
2. The chair can influence but not decide
Some steering committee chairs are selected because they are respected, visible or politically safe.
But they cannot commit the business.
They cannot approve the funding.
They cannot override a functional director.
They cannot instruct a vendor to change course.
The result is a chair in name only. The programme has a meeting leader, not an accountable owner.
3. Vendors are allowed to escalate without consequences
A vendor reports that a dependency is blocking delivery.
The business says the vendor should solve it.
The vendor says the business has not provided the required decision.
The architecture team says the issue belongs to security.
Security says the programme has not provided enough detail.
The issue circulates until the milestone is missed.
A steering committee with real authority would assign ownership, set a deadline and make the trade-off. A powerless committee records the disagreement.
4. Decisions are made outside the governance calendar
If critical decisions can only be made at the monthly steering committee, the programme is already too slow.
If they cannot be made there, the programme is worse off.
Delivery teams then create shadow governance. They use private calls, escalation chains and personal relationships to get work moving. This may keep individual workstreams alive, but it destroys transparency and increases operational risk.
5. Nobody is measured on decision velocity
Most programmes track budget, milestones, risks and benefits.
Few track how long important decisions remain unresolved.
That is a serious omission.
A decision open for 48 hours may be manageable. The same decision open for 48 days is a programme risk, even if the RAG dashboard remains green.
Track:
- Number of open decisions.
- Average age of open decisions.
- Decisions past their required date.
- Percentage of decisions reopened.
- Actions completed by the agreed deadline.
- Escalations caused by missing authority.
What gets measured becomes visible. What remains invisible becomes expensive.
The cost is larger than the delay
A blocked decision rarely affects one task.
It creates a chain reaction.
A scope decision is delayed, so the solution design remains provisional. The design remains provisional, so development cannot start. Development slips, so testing compresses. Testing compresses, so defects are deferred. Defects accumulate, so adoption suffers. Adoption suffers, so the business questions the value of the programme.
The original problem was a decision that nobody made.
The eventual consequence is a transformation that fails to deliver its business outcome.
This is also how budgets expand without a single dramatic mistake. Teams remain staffed while waiting. Vendors raise change requests. Contractors are extended. Dependencies are rescheduled. Temporary workarounds become permanent. The programme pays for uncertainty month after month.
The 7 Vendor Death Spiral often begins this way. More suppliers are added to solve a problem that is fundamentally caused by unclear ownership and weak governance.
More delivery capacity cannot compensate for absent decision authority.
What effective decision rights look like
A functioning transformation governance model separates decisions by level.
Executive steering committee
The steering committee should decide matters involving:
- Strategic scope.
- Major funding changes.
- Cross-functional conflicts.
- Material risk acceptance.
- Business ownership.
- Programme continuation, reset or termination.
Programme leadership
The programme director or transformation office should decide matters involving:
- Integrated planning.
- Sequencing.
- Dependency management.
- Resource allocation within the approved envelope.
- Risk responses below the executive threshold.
- Escalation of decisions that exceed delegated authority.
Design and technical authorities
Architecture, security, data and design forums should own decisions within their professional mandate. They should not become places where business trade-offs are endlessly debated.
Their role is to establish whether a choice is viable, compliant and supportable.
They should not be expected to decide whether the business is willing to pay for it.
Workstream leads
Workstream leaders should have authority over day-to-day delivery decisions. If every small dependency requires programme-board approval, the governance model is too centralised.
The goal is not to put every decision in the executive room.
The goal is to put each decision with the person who has both the insight and the mandate to make it.
The practical fix: create a decision ledger
Do not start with another committee redesign workshop.
Start with the decisions currently blocking delivery.
Create a decision ledger with six fields:
| Field | Question |
|---|---|
| Decision | What exactly must be decided? |
| Owner | Who is accountable for making it? |
| Authority | What mandate allows them to decide? |
| Inputs | What evidence is required? |
| Deadline | By when must the decision be made? |
| Consequence | What happens if it remains open? |
Then apply five rules.
One: name one decision owner.
Not a committee. Not “business and IT”. One person.
Two: define the decision deadline before discussing the options.
A decision without a date is only a discussion topic.
Three: state the consequence of delay.
Make the cost visible in terms of budget, milestones, risk, compliance or benefits.
Four: separate input from approval.
Stakeholders may provide input without having veto power.
Five: escalate automatically when the deadline passes.
Do not wait for the next monthly meeting. Escalation should be a designed mechanism, not a personal act of courage.
The Project Management Institute’s guidance on transformation programme management similarly emphasises senior leadership engagement, data-driven decisions and documented governance.
Documentation is not bureaucracy when it records accountability. It is bureaucracy when it records activity without ownership.
Fix the empty chair before rescuing the plan
When a programme is stalled, organisations often revisit the business case, replace the PMO or ask the vendors for a revised plan.
Sometimes those actions are necessary.
They are not the first question.
The first question is:
Who is authorised to make the decisions this programme now needs?
If the answer is unclear, rewriting the plan will not help. The new plan will enter the same governance system and encounter the same deadlocks.
This is why our delivery diagnostic and programme rescue work starts with execution reality. We examine open decisions, ownership, dependencies, governance behaviour and delivery evidence before recommending another solution.
The objective is not to create more reporting.
It is to restore the organisation’s ability to decide.
The question every CIO should ask
At the next steering committee, do not ask only:
- Are we on budget?
- Are milestones green?
- What are the top risks?
- Is the vendor confident?
Ask this instead:
Which decisions are blocking delivery, who owns them, and what authority do they have to resolve them today?
If the answer is “we need to take that offline”, ask who will decide, by when and under what mandate.
That question will make some people uncomfortable.
Good.
Discomfort is often the first sign that governance theatre is being replaced by delivery accountability.
Conclusion: governance must produce movement
A steering committee is not successful because every seat is occupied.
It is successful when the right decisions are made at the right level, within the required timeframe, by people who are accountable for the consequences.
The empty chair is not a staffing issue.
It is the missing seat of authority.
Fill it with a named executive owner. Define the decision rights. Set deadlines. Escalate automatically. Measure decision velocity. Then hold the programme leadership and vendors accountable for execution.
Strategy sets the direction.
Technology provides the capability.
Governance creates the conditions for execution.
Without decision authority, the execution gap remains open.
If your programme has too many meetings and too few decisions, book a discovery call with Dark Consultancy. We help CIOs and transformation leaders identify the governance failures blocking delivery and create a practical route from diagnosis to execution.
Frequently Asked Questions
What is steering committee governance?
Steering committee governance is the framework used to direct a programme, make strategic decisions, resolve conflicts, oversee risks and hold delivery leaders accountable for outcomes. It should define decision rights, escalation routes and accountability.
Who should have decision authority on a transformation programme?
Decision authority should sit with the person who has the relevant business mandate and sufficient insight to make the decision. Strategic scope, funding, material risk and cross-functional conflicts usually require executive authority. Operational decisions should remain with programme and workstream leaders.
How can decision-making be improved in a stalled programme?
Start by listing every open decision blocking delivery. Assign one accountable owner, define the required authority, set a deadline and document the consequence of delay. Escalate automatically when the deadline is missed.
Should the steering committee make every programme decision?
No. The steering committee should make only decisions that exceed delegated thresholds or involve strategic trade-offs, major funding, material risk or unresolved cross-functional conflict. Over-centralising decisions slows delivery.
What is decision velocity?
Decision velocity measures how quickly an organisation makes and implements important decisions. Useful measures include the number of open decisions, average decision age, overdue decisions and action completion rates.
How does programme rescue address governance failure?
Programme rescue begins by establishing the delivery facts, identifying blocked decisions, clarifying ownership and redesigning the governance path where necessary. A new plan cannot succeed if the organisation still cannot make timely decisions.
About the Author
Kunal Patel : CEO & Founder, Dark Consultancy
Kunal Patel founded Dark Consultancy after two decades leading technology and transformation programmes across the public sector, financial services, defence, and energy industries. He has directly managed programme recovery engagements for government agencies, development finance institutions, and regulated enterprises across the US, Middle East, South Asia, and Southeast Asia : ranging from $5M platform migrations to $200M+ enterprise transformation portfolios. Kunal is a recognised practitioner in delivery governance for regulated environments and holds PMP and PRINCE2 Practitioner certifications. He leads every new client engagement personally and remains accountable throughout the programme lifecycle. Connect with Kunal on LinkedIn
SEO Publishing Assets
- SEO title: Why Steering Committees Fail to Unblock Programmes
- Meta description: Transformation programmes stall when steering committees lack decision rights. Learn how CIOs can fix governance, ownership and delivery speed.
- Suggested URL slug:
empty-chair-steering-committee-decision-rights - Focus keyword: transformation programme governance
- Related keywords: steering committee governance, decision rights, programme rescue, delivery governance, transformation execution
- Image alt text: Enterprise transformation steering committee with one empty chair representing missing decision authority
- Search intent: Informational with commercial investigation
- Recommended internal links: Dark Consultancy services, The Real Cost of False Green, The 7 Vendor Death Spiral, and The $50M Re-Baseline
- Authoritative external sources: PMI: Transformation Program Management, UK Government Teal Book: Governance and Management, and PwC: Programme Governance and Delivery Risk
- Recommended schema: Article, FAQPage and Organization schema