After showing four or five slides or speaking for about ten minutes, stop and explicitly ask for doubts and concerns. Frame it as "if you didn't have to be polite, what would you say?" or "what seems totally useless from your current point of view?" This creates recurring permission to speak up rather than expecting people to interrupt you when something isn't working.
Example
An integration architect ran a three-day workshop to design architecture for a new CRM system. The process seemed to go well—people participated, agreed on principles, even physically placed themselves on the "yes, I support this" end of a line. Four weeks later, none of the action items were done. As one manager pointed out, everyone agreed but nobody was excited. The workshop had become success theater because there were no structured moments to surface genuine concerns.
Context
This becomes critical when you're in an authority position as an architect or when introducing new methodologies people might find intimidating. Your expertise can actually prevent people from speaking up. The pattern works because it normalizes dissent as part of the process rather than as disruption. If people are scrolling on their phones or disengaging, that's information you need. Small groups of three people feel safer for initial sharing before bringing concerns to the full room.
When This Might Not Apply
- During high-energy creative phases like initial sticky note generation—frequent pauses kill momentum.
- With highly experienced, self-managing teams who already surface issues organically.
Variations
- For technical workshops, ask "What assumptions here break in production?"
- For remote sessions, use timed polls or reactions before verbal sharing.
