Keep Delivery Moving When a Steering Committee Disagrees

Steering disagreement slows delivery when leaders argue for a preferred solution before agreeing on the choice before them. A delivery director brings order without choosing for client leaders. Name the decision, state each view fairly, show available evidence, and explain the delivery effect of waiting. Those moves give a committee a route from disagreement toward an owned choice.

Before a meeting, find the decision hidden inside broad statements. “We need more assurance” might mean a request to delay a release. “The team is moving too slowly” might mean a request for more people, a scope change, or a later date. Ask each leader which action they want approved. Reduce those requests into one neutral question. “Should the East release proceed on 14 October, move after the service window, or pause for forecast review?” gives everyone one subject.

Write options in plain language. Each option needs a delivery effect, conditions, and a decision owner. Proceeding might preserve a planned service window yet need a checked cost forecast. Moving a release might protect a spending limit yet alter training arrangements. Pausing might create review time yet leave staff using an older process. You are not predicting results. You are showing what work changes after a choice and which facts need checking first.

Separate facts, interpretations, preferences, and unknowns before people arrive. A fact has a source, date, and owner. “The supplier invoice lists 42 September hours” becomes a fact after finance checks the source. “The program exceeds budget” is an interpretation until people agree on cost treatment and forecast assumptions. “Release after peak season” is a preference. “Whether staffing covers weekend support” stays unknown until an operational owner checks the roster. This separation stops a preference borrowing authority from a number.

Meet leaders individually when tension has appeared. Do not arrange a private result. Use short discussions to hear concerns, identify evidence, and reduce surprises. Ask finance which forecast element needs review. Ask operations which service period needs protection and why. Ask a sponsor what decision rights sit with the committee. Tell every person you will present their point accurately, including uncertainty. People usually address the real choice more readily after feeling heard.

Prepare a short pre read. Put the decision question first. Follow with one page per option, source evidence, facts still under review, and a decision date. State the delivery consequence when no decision arrives by a named date. Configuration work might stop to avoid spending outside agreed scope. A planned training session might lose its reservation. Such detail is not pressure. Leaders need a clear view of the operational cost of waiting.

Set meeting roles early. The sponsor owns the committee choice. A finance lead explains financial records and assumptions. An operations lead explains service effects. The delivery director keeps time, restates the question, and records actions. A project manager supplies plan detail when asked. Clear roles matter during disagreement. Without them, people speak past one another or expect a delivery director to settle a decision outside their authority.

Open the meeting by describing a finished result. A decision is one valid result. A defined evidence request with a named owner and return time is another. Open discussion with neither result leaves delivery stalled. Ask members to challenge evidence or an option, rather than assign motives to another leader. When someone says, “Finance always blocks progress,” return to a record. Ask which forecast assumption needs review before finance supports an option.

Consider this fictional steering situation. Finance chief Elena wants to delay a regional release planned for 14 October. An updated forecast from program analyst Leo raises a concern about work outside approved scope. Operations leader David wants the release to stay on schedule because a service calendar reserves staff for training from 7 through 11 October. Delivery director Brooke speaks with both leaders before the committee session.

Brooke writes a neutral question. “Should the regional release proceed on 14 October, move to 4 November, or pause until forecast review ends?” She asks Leo to list assumptions beside every cost figure. She asks operations planner Maren for available training dates after 14 October and their service effects. Brooke also asks Elena whether her committee holds authority for a scope adjustment. Elena says the committee chooses a date, yet an executive group must approve a scope adjustment.

The fictional pre read arrives on Monday 6 October. One page says a 14 October release needs agreement on outstanding vendor hours. Another says 4 November avoids the October service period yet needs a new training reservation. A third says a pause stops configuration work after 9 October until scope approval arrives. The pack names Leo and Maren as evidence owners. Each page separates figures from assumptions. Brooke asks members for factual corrections before noon Tuesday so meeting time stays focused on the choice.

During the session, Elena says, “We need to delay the release.” David replies, “A delay will disrupt the service calendar.” Brooke says, “Our question covers 14 October, 4 November, or a pause. Finance needs review of vendor hours and internal estimates. Operations needs a workable training date. Do Leo’s and Maren’s records answer those concerns, or is a specific point still open?” This wording stops discussion from becoming a contest between positions.

Elena says two vendor entries lack descriptions. Brooke records the issue precisely and asks Leo whether descriptions will arrive by Wednesday morning. Leo agrees. David says 4 November works only if operations confirms two trainers by Friday. Brooke asks Maren to secure confirmation. The group does not claim agreement exists. Elena sets a decision session for Thursday at 3 pm, after both checks return. Brooke records which option each check affects.

David then says finance raised the concern too late. Elena says operations did not provide estimates early enough. Brooke does not turn the session into an argument about history. She says, “Both concerns point to missing inputs before a release decision. Leo will return vendor descriptions, and Maren will confirm trainers. After Thursday, we will decide how estimate owners send updates before future steering sessions.” The committee accepts a follow up item for its next agenda.

Keep a short action log during conflict. Record the issue, owner, evidence requested, return time, decision session, and delivery status. Avoid a vague note such as team to align. Send notes soon after the meeting and ask owners to correct factual errors. When evidence returns, prepare one updated decision page. Mark what changed, who checked each point, and which options remain practical. If evidence does not arrive on time, report absence plainly. The sponsor then chooses whether to extend review, decide from present records, or pause work.

For practice, set up a fictional release choice. Give one leader a cost concern and another leader a service concern. Write a neutral question with genuine options. List one fact, interpretation, preference, and unknown for each view. Chair a ten minute roleplay. When blame enters discussion, return everyone to a record and owner. Finish by placing Thursday’s fictional decision session on the calendar, then send Leo a request for vendor descriptions by Wednesday at 10 am.