When a steering committee stops steering

Look at the last few steering committee minutes. If they contain many updates and few decisions, the meeting may be providing visibility without providing direction.

Visibility can be useful. It does not necessarily require a committee with senior people in the room. The cost becomes harder to justify when the project still waits for decisions after everyone has attended.

I would review what the committee is authorised to decide, how quickly it does so and what would happen if the meeting stopped. Those questions are more revealing than whether the agenda follows a recognised format.

Give the committee a bounded job

A committee should exist to make a defined class of decisions. That might include material scope changes, allocation between competing business priorities or recommendations above its financial delegation.

Write the remit in language participants can apply. "Provide strategic oversight" does not tell a project manager whether the committee can approve a changed release scope. State the limits and name the route for matters outside them.

Check the authority of the people attending. A representative who can only relay a question to someone else may contribute useful knowledge but cannot substitute for the decision owner. If attendance regularly excludes the people who can decide, change the membership or the decision route.

Keep engineering judgement in the appropriate place. A steering committee can decide whether a business outcome justifies investment or a revised deadline. It should not vote a technical constraint out of existence.

Bring choices before the meeting

A decision paper should explain the problem, credible options, recommendation and consequence of waiting. Circulate it early enough for participants to ask for missing information before the scheduled discussion.

In a fictional project, user testing identifies a workflow that cannot be completed reliably in the planned first release. The project team can narrow the release, move the date or add a temporary supported process. The committee needs the implications of those options, not a lengthy account of every test defect.

Ask for a specific resolution. If the required evidence is incomplete, identify the smaller decision that can be made now, such as funding an assessment or agreeing an interim scope boundary.

Routine status belongs in the pre-read unless something has changed enough to need discussion. Spending the meeting reading the report aloud leaves the hardest item to the final minutes, when participants are already thinking about their next appointment.

Measure how long decisions wait

Track the date a decision was needed, the date sufficient information was available and the date it was made. This helps distinguish a slow committee from an incomplete proposal.

Review decisions carried between meetings. Ask what is preventing closure and who can remove that obstacle. "Further discussion required" should not survive repeatedly without a named question and owner.

Set a route for decisions that cannot wait for the next scheduled meeting. An authorised chair may convene a short session or use a documented written process, subject to the organisation's rules. Urgency should change the route, not silently remove the authority requirement.

If a delay affects delivery, update the plan and tell the sponsor. Do not continue reporting the original date as achievable while the prerequisite decision remains open. This is one reason a roadmap needs decision points, not just project bars.

Record conditions as carefully as approvals

A resolution should state what was approved, who is responsible and any conditions. "Committee endorsed the approach" can conceal disagreement about scope, cost or timing.

For the fictional release decision, record which workflow is excluded, what temporary process is approved and who will verify that process before launch. If a committee accepts an exposure within its authority, document the duration and review conditions.

Keep a decision log distinct from the action list. An action to obtain a quote is not an approval to buy. An agreement to investigate a release delay is not approval of a new date. The distinction prevents tentative discussion from becoming an assumed commitment.

Bring back previous decisions when their conditions no longer hold. That is a legitimate reason to revisit a resolution. A sponsor simply preferring a different option after the meeting is a different matter and should be treated transparently.

Retire meetings that no longer have a purpose

A committee may be useful during a difficult investment or delivery period and unnecessary once the service has a stable owner. Give the committee an explicit review point rather than assuming it exists indefinitely.

Before closing it, identify where any remaining decisions, risks and actions will go. A service owner, existing management forum or temporary working group may be better placed to handle them. Tell participants which old escalation route is ending.

Do not preserve a redundant committee merely because people appreciate the update. Replace that function with an appropriate report. Equally, do not abolish the meeting if it is the only place unresolved business priorities can be settled; fix its authority and agenda first.

Business ownership should not depend on a recurring invitation. The owner should remain accountable between meetings and after the committee closes.

For the next session, put the most consequential decision first and reserve time to resolve it. If there is no decision, no material challenge and no required oversight discussion, consider whether a written update would do the job better that month.