I've run hundreds of workshops and alignment sessions with enterprise teams. The problem I see most often isn't that people disagree. It's that they think they agree — and then find out three sprints later that they were talking about different things the whole time.
The meeting that should have been a workshop
A product team has a kickoff. Everyone nods along to the slides. The PM walks away thinking they're aligned. Engineering starts building. A few weeks in, someone says, "Wait — that's not what I thought we agreed to."
This isn't a communication problem. It's a conversation design problem. The meeting wasn't set up to surface the differences in how people understood the work.
What good facilitation actually does
It's not about sticky notes and dot voting, though those can help. It's about setting up the conversation so that:
- Assumptions come out early, before anyone writes code
- The loudest person doesn't automatically win — quieter voices get room
- Decisions are said out loud, not just implied by silence
- Everyone leaves with the same understanding, not just the same slides
Why I think about it like design
I approach facilitation the same way I approach product design:
- Who are the users? — Stakeholders, each with their own mental model
- What outcome do we need? — Real alignment, actual decisions, a prioritized list
- What are the constraints? — Time, politics, whether people are remote, who has decision authority
- How do we know it worked? — Can each person explain what was decided and why?
The workshop is the product. The people in the room are the users.
When you probably need a facilitator
Not every meeting needs one. But you likely do when:
- The stakes are high and people want different things
- You've tried to align before and it didn't stick
- The team crosses disciplines and people are talking past each other
- The decision will be expensive to undo
A two-day facilitated workshop almost always costs less than building the wrong thing for a quarter.
The best teams I've worked with treat facilitation like infrastructure, not overhead. They put effort into the quality of their conversations the same way they put effort into their code — because a bad conversation creates its own kind of debt, and it compounds just as fast.