All insights

Program leadership

Governance should help delivery, not slow it down.

Omer Khan · 2 min read

Updated · Practical guidance with illustrative examples

A practical way to make steering committees more useful: start with the decisions that delivery needs.

How do you make program governance useful?

Start with the decisions required to protect delivery and benefits. Give each decision a recommendation, accountable owner and deadline. Use reporting to explain the evidence and trade-offs, then follow through on the actions agreed.

A steering committee can have a complete reporting pack and still leave a program without direction. The quality of governance is better judged by the decisions it enables than by the volume of information it receives.

Begin with the decision

Before preparing an update, ask what the committee needs to decide. A funding choice, unresolved dependency or change in scope deserves a clear recommendation. Routine progress can be summarised separately.

Make the trade-off visible

Present the available options, their consequences and your recommendation. Explain the effect on delivery, cost, risk and intended benefits. A request to approve additional funding becomes more useful when the committee can see what happens if it declines.

Give each decision an owner

Record who will act, by when and what evidence will confirm completion. Revisit outstanding actions at the next meeting. An agreement without ownership can disappear between reporting cycles.

Keep the reporting proportionate

A small initiative and a complex portfolio need different reporting depth. Use enough information to expose material issues without burying them. When a metric changes, explain its significance and the action required.

Try this at your next meeting

Identify the three decisions that matter most before building the slide pack. Put them near the beginning. Give each a recommendation, owner and required date. After the meeting, assess whether the program is better able to move forward.

Illustrative example: a shared testing bottleneck

Suppose two technology projects need the same test facility. Both report progress against their own plans, but neither can secure the required slot. The committee needs a sequencing decision: which release protects the most important outcome, what delay is acceptable and who will negotiate capacity? A useful update presents those choices rather than two separate green status indicators.

A practical decision brief

Use five fields: decision required, options, recommendation, consequence of delay and accountable owner. Add the evidence needed to assess the choice. This is a suggested working format, rather than a prescribed PMI template.

Further reading and scope

PMI's governance practice guide describes governance across portfolios, programs and projects. The decision brief and example here are practical editorial guidance, not a quotation from that guide or a reported client result.

References