Steering Committee Meetings That Never Decide
A cross-functional steering committee is six weeks behind on a customer-portal replacement. Victor, the executive sponsor, is results-first, opens with 'What is the bottom line?' and has twice ended meetings at 30 minutes. Lin, the finance lead, brings a 12-page risk memo and asks for line-by-line assumptions. Sofia, the operations manager, listens, takes notes, rarely speaks, then sends carefully worded objections after decisions are 'final.' Dev, the marketing lead, opens with stories and has twice taken the group into a 20-minute discussion of a competitor's campaign. Meetings run 90 minutes, end without decisions, and the last three action items were re-litigated. The project manager sends a 40-slide pre-read that no one reads. You are brought in to fix the governance rhythm.
1. How would you redesign the 60-minute decision meeting to work with these behavioral preferences without stereotyping anyone? Include agenda, pre-work, and facilitation moves.
Read the worked answer
I would treat DISC as a set of hypotheses about preferred pace, detail, and processing style, not as labels to announce. The redesign should make the meeting safe for each preference while forcing a decision.
Pre-work: replace the 40-slide deck with a one-page decision memo: the decision requested, a recommendation, three options with cost, risk, and schedule impact, and a short appendix of assumptions. Send it 48 hours ahead. Ask Lin for written questions by a deadline and answer them in the appendix. Ask Sofia for a pre-meeting conversation or written concerns. Give Dev a three-minute customer-story slot at the start.
Agenda: 0-5 minutes, frame the decision and the decision rule; 5-15, data and assumptions, with Lin's questions handled first; 15-30, options and trade-offs; 30-45, decision; 45-55, commitments, owners, and dates; 55-60, recap and parking lot. Use a visible parking lot for tangents and a decision log projected on screen. Lead with the bottom line for Victor, then give him a choice between options rather than an open discussion. Timebox each segment. Use silent writing before discussion so Sofia's views are captured before the fastest speakers dominate.
Facilitation moves: round-robin, 'what would make this hard to support?', and an explicit 'disagree and commit' check. Never say 'Victor is a high D' in the room; describe the behavior and the process adjustment instead.
2. Sofia's after-the-fact objections are blocking commitments. What is your diagnosis and what would you do before, during, and after the next meeting?
Read the worked answer
My working diagnosis is that Sofia may need more processing time and may avoid open conflict, so she signals disagreement late rather than in the room. That is a behavior pattern, not a personality verdict, and it may also reflect a legitimate concern that operations risk is being ignored. The worst response is to label her passive-aggressive in public or to ignore the objections because they arrive late.
Before the next meeting, I would speak with her one-to-one at least 48 hours ahead, send the decision memo, and ask: 'What concerns would you need addressed to support this decision?' I would ask for written conditions and make clear that late objections will be treated as input, but not as a veto after the decision. During the meeting, I would invite her first in the options round, use silent writing before discussion, and run a structured 'concerns and conditions' round. I would separate the decision from implementation details so she can support the former while flagging the latter.
After the meeting, I would record the decision, rationale, dissent, and her stated conditions in the decision log. I would assign her a check-back point so her concerns have a route. If she continues to block commitments, I would address role clarity and accountability directly, not through the group. I would also test whether operations has a real risk that the committee has been dismissing.