How to run a steering committee that makes decisions

Steering committees have earned their bad reputation. In most organisations, they are monthly meetings where project managers present status slides, executives nod politely, and everyone leaves without making a single decision.

The meeting takes an hour. The preparation takes a day. The outcome is a set of minutes that nobody reads and a vague sense that "we should keep an eye on" the projects that are struggling.

That is not governance. That is theatre.

A steering committee that works is a decision-making forum. It exists to make calls that individual project managers cannot make alone: resource allocation, priority changes, risk escalation, and scope decisions that affect the portfolio.

Why steering committees become status meetings

The drift from governance to status happens for predictable reasons:

No clear decision agenda. If the meeting does not have specific decisions to make, it defaults to status updates because that is the easiest thing to present.

Too many projects, not enough time. When the committee tries to review every project in the portfolio, there is no time left for discussion or decisions. The meeting becomes a parade of RAG statuses.

Preparation substitutes for governance. The PMO spends days preparing a beautiful deck. The committee spends the meeting admiring the deck. Nobody asks "what do we need to decide?"

No accountability for previous decisions. If the committee makes decisions but nobody tracks whether they were implemented, the decisions are meaningless. The same issues resurface every month.

How to restructure a steering committee

1. Define the committee's purpose

A steering committee exists to make decisions that require senior authority. Specifically:

• Approve or defer new projects
• Reallocate resources across the portfolio
• Escalate or de-escalate risks
• Approve scope changes that affect timelines or budgets
• Remove blockers that project managers cannot resolve alone

If a topic does not require a decision from this group, it does not belong on the agenda.

2. Replace status slides with an exception report

Do not present every project. Present only the projects that need attention: those that have changed status, those that need a decision, and those that are blocked.

The committee should be able to see the full portfolio health on a dashboard before the meeting. The meeting itself focuses on the exceptions — the things that need human judgment.

3. Structure the agenda around decisions

Every agenda item should be framed as a decision: "Should we approve the additional resource for Project X?" "Should we defer Project Y to Q3?" "Should we accept the risk on Project Z or invest in mitigation?"

If an agenda item does not have a decision attached, it is informational and should be communicated asynchronously rather than consuming meeting time.

4. Limit the meeting to 45 minutes

A steering committee that runs longer than 45 minutes is trying to do too much. If the portfolio is large, increase the frequency (fortnightly instead of monthly) rather than the duration.

Short meetings force focus. Long meetings enable drift.

5. Track decisions and actions

Every decision from the steering committee should be recorded with context: what was decided, why, and who is responsible for implementation. Every action should have an owner and a due date.

The next meeting starts by reviewing whether previous decisions were implemented and previous actions were completed.

The decision-ready format

For each item that needs a steering committee decision, present it in a standard format:

Context: What is the situation? (Two to three sentences maximum) Options: What are the choices? (Two to three options with trade-offs) Recommendation: What does the project team recommend? Decision needed: What specifically does the committee need to decide?

This format respects the committee's time by doing the analysis in advance and presenting clear options rather than open-ended problems.

Real-world example

A professional services firm had a monthly steering committee that ran for two hours. Each of the twelve engagement leads presented a five-minute status update. The partners asked a few questions. Decisions were rare because the meeting ran out of time before reaching the items that needed them.

They restructured: the portfolio dashboard was shared 24 hours before the meeting so partners could review status asynchronously. The meeting agenda contained only items that needed decisions — typically three to five per month. Each item was presented in the decision-ready format.

The meeting dropped from two hours to forty minutes. Decision throughput increased from roughly one decision per meeting to four. The engagement leads got their time back because they no longer needed to prepare status presentations.

Common anti-patterns to avoid

The information dump. Presenting every metric and every project update consumes time without creating value. Use a dashboard for information; use the meeting for decisions.

The open-ended discussion. "Let's discuss Project X" is not an agenda item. "Should we add two weeks to Project X's timeline?" is an agenda item. Frame everything as a decision.

The absent decision-maker. If the person who needs to make the decision is not in the room, the item should be deferred. Do not discuss items that cannot be resolved in the meeting.

The recurring item. If the same issue appears on the agenda for three consecutive meetings without resolution, it needs a different approach — either a dedicated working session or an escalation to a higher authority.

Best practices

Send the dashboard before the meeting. Give committee members 24 hours to review the portfolio status. The meeting should not be the first time they see the data.

Limit agenda items to five. If more than five items need decisions, either the committee is meeting too infrequently or items are being brought that could be resolved at a lower level.

Assign a decision owner for each item. Someone should be responsible for presenting the item in decision-ready format and implementing the outcome.

End with a decision summary. The last two minutes of the meeting should recap: what was decided, who owns the follow-through, and what is due by when.

Rotate the chair if needed. If the same person always chairs, the meeting can become their status update. Rotating the chair keeps the focus on governance rather than reporting.

How Praxiox helps

Praxiox supports effective steering committees by providing the portfolio dashboard that committee members review before the meeting, and the meeting record structure that captures decisions and actions during the meeting.

Decisions from steering committees become tracked items linked to the relevant projects. Actions are assigned with owners and due dates. The next meeting automatically surfaces previous decisions and actions for review.

This closes the loop between governance and execution — the steering committee makes decisions, and the system ensures those decisions are followed through.

For teams restructuring their governance cadence, the portfolio governance guide provides the broader framework. The PMO use case shows how steering committees fit into the operational model.

A practical rollout

The easiest way to introduce this kind of workflow is to treat it as a habit change, not a documentation exercise. People adopt what saves them time. They ignore anything that adds ceremony without changing the work itself.

That means the first goal is not full coverage. It is one visible win that shows the new approach is lighter than the old one. If the team can feel the difference in the first cycle, the change has a chance to stick.

1. Identify the step that causes the most chasing, copying, or follow-up.
2. Replace that step with something the team can update in place.
3. Revisit the change after two or three cycles and remove anything nobody is using.

In practice, the first owner should be the person already closest to the work, not someone assigned to police the process. The best change is the one the team can keep alive without making a separate ritual out of it.

The features page shows the operational side of a lighter workflow, and the PMO use case shows how the same habit supports a wider portfolio.

When the first version feels easy, people keep going. When it feels like extra process, the rollout will stall no matter how useful the idea is.

How to tell it is working

The process is working when the team stops asking where the latest version lives. You see fewer reminders, fewer surprise escalations, and fewer meetings spent re-creating the same status.

Watch for three signs:

• people update it without being chased
• meetings get shorter because the status is already visible
• decisions move faster because the facts are current

The real signal is trust. When people stop keeping their own shadow list and start relying on the shared view, the system has begun to work properly.

The features page shows the kind of setup that makes those signals easier to see. The PMO use case shows the same behaviour at portfolio level.

If those signs do not move, the workflow is still too hard to maintain. The fix is usually to simplify the steps people touch every week, not to add another rule.

Practical next step

If How to run a steering committee that makes decisions is supposed to produce decisions, not just discussion, the first move is to make the meeting shorter and sharper. Keep the agenda focused on exceptions, decisions, and follow-through. Anything that can be read from the dashboard should stay out of the live conversation.

A useful governance change does not need a new committee. It needs a cleaner rule for what gets discussed in the room. Put status in the shared system, reserve the meeting for decisions, and make sure every decision produces an owner and a due date.

That usually shortens the meeting immediately, because people stop reading their updates out loud. It also makes the result easier to trust. When the same structure is used week after week, the team knows where decisions live and what gets reviewed next time.

The features page shows how the workflow stays connected to the work. The PMO use case shows how the same structure plays out in a live operating model.

After two cycles, review what people are still doing outside the system. If the answer is “copying status,” “asking for the latest version,” or “keeping a backup spreadsheet,” the process still needs one more simplification pass. If the answer is “nothing,” the change is probably small enough to stick.

Frequently asked questions

How often should a steering committee meet?

Monthly for most portfolios. Fortnightly if the portfolio is large or fast-moving. Weekly is usually too frequent for a senior governance forum — use a portfolio review for weekly operational decisions.

Who should attend a steering committee?

The people with authority to make the decisions on the agenda. Typically: executive sponsors, the PMO lead, and the project managers whose items are being discussed. Avoid inviting people who do not have a role in the decisions.

How do I prevent steering committees from becoming status meetings?

Structure the agenda around decisions, not updates. Share the portfolio dashboard before the meeting so status is consumed asynchronously. Only bring items that require senior authority to resolve.

What decisions should a steering committee make?

Resource allocation across projects, priority changes, scope approvals, risk escalation responses, and project approvals or deferrals. Anything that requires authority beyond the individual project manager.

How do I handle items that need more discussion than the meeting allows?

Schedule a separate working session for complex items. The steering committee should make the decision or delegate it — not become a working group.

What is the ideal length for a steering committee meeting?

Thirty to forty-five minutes. If the meeting consistently runs longer, either the agenda has too many items or items are not being presented in decision-ready format.