When two senior leaders in a cross-functional planning session arrive at genuinely conflicting positions and both are right, the consulting team’s facilitation work begins in earnest. The VP of Sales wants to sequence a commercial model rollout by territory because her field teams can only absorb one major change per quarter; the VP of Marketing wants to sequence by channel because the digital engagement architecture requires the foundational CRM integration everywhere before the second channel can function. Both positions are defensible, rooted in real constraints, and both cannot be fully satisfied at the same time.
Compromise Inherits Constraints Without Advantages
The instinct is to find middle ground: split the difference, propose a hybrid. This instinct is wrong in most cases because the hybrid frequently inherits the constraints of both options without the advantages of either. A hybrid that sequences by territory for early waves and switches to channel for later waves sounds reasonable until the team works through the implications and discovers it violates both leaders’ core constraints in different phases of the plan. The consulting team’s job is to make the tradeoff explicit through exercise design, something a brokered compromise would obscure.
Structured Tradeoffs Let the Room See What It’s Actually Deciding
The first move is to name what each option gains and loses, structured on the wall so the room can see it.
- Sequencing by territory: the field sales teams absorb changes in a controlled cadence and training can be concentrated with hands-on support from regional directors. The cost is that the foundational CRM integration doesn’t deploy broadly until late in the rollout, delaying the most complex digital engagement work.
- Sequencing by channel: the digital engagement architecture gets built in the right order with incremental testing, and the marketing team avoids supporting partial channel deployments. The cost is that every territory absorbs both changes in a compressed window, and training has to be redesigned for a sequence that doesn’t align with how the field teams are organized.
Writing this on the wall validates both leaders by showing their positions are rooted in real constraints and makes visible the thing the room actually needs to decide: which set of costs is the organization more willing to absorb?
Naming the Decision Reframes Disagreement as Structure
The consulting team names the decision explicitly: “This is a sequencing decision that prioritizes either field team absorption capacity or digital engagement architecture integrity. Both are legitimate priorities. The question is which one takes precedence for this program, and that’s a decision for someone with authority over both functions.” Naming the decision this way reframes the disagreement. The two leaders are each advocating for the constraint that matters most from their function’s perspective; the conflict is structural rather than personal. The program has two legitimate constraints that cannot both be fully satisfied, and someone needs to decide which one to optimize for.
Routing Authority Preserves Trust for the Rest of the Engagement
The next move is to identify who has the authority to make this decision. If the decision-maker is in the room, the consulting team turns to them and asks for a direction. If the decision-maker isn’t in the room, we document the tradeoff precisely: the two options with what each gains and loses, and the specific decision needed. A well-documented escalation takes ten minutes to resolve in a leadership meeting; a vaguely documented one (e.g., “the team disagrees on sequencing and needs guidance”) restarts the same debate.
Our value in this moment is preserving the relationship between the two leaders while surfacing the structural tradeoff. Creating conditions where disagreement is productive rather than threatening is what makes the rest of the engagement work. When the consulting team names the tradeoff and validates both positions before sending the decision to the person who can make it, both leaders feel their constraint was taken seriously and the process was fair.
This matters for the rest of the engagement. Architecture and roadmap sessions produce dozens of decisions, and the leaders in the room need to trust that the process will handle disagreements with integrity. If the first real conflict produces a clear tradeoff and a clean decision, the next conflict will be brought to the table; if it produces a forced compromise, the next conflict will be avoided rather than surfaced. The same principle applies when the quiet room and the dominant voice are both present: the exercise design determines whose input shapes the outcome.
