The stakeholder who kills the strategy.

You know this person. They attended every session. They did the sticky-note exercises. They said "this is great" at least twice. And then, at the final readout, the one with their boss in the room, they leaned back and said the sentence: "I just worry this doesn't reflect where the business is going."

Meeting over. Not officially (it ran another forty minutes), but the strategy died right there, and everybody felt it happen.

The tempting read is betrayal, and I want to talk you out of it, because I've watched this movie from the facilitator's chair for a decade and the villain framing gets the mechanics wrong. Getting the mechanics wrong means it happens to you again.

Silence was never agreement

Here's what actually happened: the workshop asked for consensus in a setting where dissent was expensive. Speaking up in a room of colleagues, against momentum, against a cheerful facilitator with a marker, that costs something. So the objection waited. It waited for the setting where raising it was cheap and not raising it was expensive: in front of their boss, attached to a business concern, at the moment of commitment. The readout wasn't where the disagreement started. It was where it finally became affordable to say.

Once you see it that way, the fix stops being "manage the difficult person" and becomes "reprice the dissent." Make disagreement cheap early and expensive late, instead of the reverse.

Make them argue in week two

Practically, that means the strategy process needs a fight built into its front half, on purpose. Not a survey. Surveys collect polite fictions. A real session where the positioning territories are pinned up as rivals and every stakeholder is required to attack one. I mean required: "Before we leave, everyone names the strongest argument against the direction they like most." You're not harvesting opinions. You're making dissent a completed assignment instead of a pending threat.

The one-on-one pre-wire matters even more, and it's where I've learned to spend my hours. The quiet stakeholder will tell you things alone that no workshop will ever extract, usually the real thing, which is rarely strategic and almost always structural. Their team gets smaller under this direction. Their pet project loses its rationale. They fought for a version of this two years ago and got burned. None of that will ever be said at a whiteboard, and all of it votes at the readout.

Give the objection a job

When you find that concern, don't neutralize it. Hire it. The stakeholder who worries the strategy abandons the core customer becomes the named owner of the transition plan for the core customer. Their worry appears in the deck, attributed, with a mitigation they approved. This isn't a trick. It's the honest version of alignment: the strategy is stronger because the objection is inside it, and the objector can't torpedo a ship they helped design. People defend what they argued about. That's the whole mechanism.

If it still happens

Sometimes it happens anyway: the sentence, the boss, the deflating room. Don't debate the vague version; vagueness is the weapon. Ask for the specific: "Which part conflicts with where the business is going?" Half the time there's no answer behind the sentence, and the room watches it dissolve. The other half, there's a real answer, in which case you just learned the thing the entire process failed to surface, and the strategy genuinely needs it.

Either way, take the note for next time: nobody kills a strategy at the readout. They kill it in the weeks before, in every session where staying quiet was the cheaper move. Price the room so the truth comes out early, and the readout goes back to being what it should be: a formality.