When people resist change or seem confused, the instinct is to explain more—create more models, use more words, provide more documentation. This rarely works. Instead of adding more explanation, design an experience where people can discover the insight themselves. Facilitation creates more lasting impact than explanation because people internalize what they discover through their own thinking.
Example
Moving from a CRUD monolith to microservices requires fundamentally different thinking patterns. Rather than explaining event-driven architecture repeatedly, create workshops where teams model systems themselves—first modeling how current patterns generate current outcomes, then redesigning for different outcomes. When developers experience the difference between tightly coupled and loosely coupled thinking by working through it themselves, they pick up the pattern and run with it. Even when the experience leads to "this won't work and here's why," that's valuable—better to discover problems early through experience than after significant investment.
Context
This approach requires consent—you cannot force experiential learning on unwilling participants. Look for areas where the organization already acknowledges complexity and wants to move forward but lacks certainty about the path. Focus on situations where people recognize they need valuable knowledge rather than promising to solve a complete problem. The hard part shifts from convincing people to try something different to designing experiences that will actually generate useful insights. You're taking a risk alongside participants, which makes facilitative leadership harder than simply telling people what to do.
When This Might Not Apply
– When participants withhold consent and demand command-and-control certainty—experiential learning fails without willingness to risk uncertainty. – In environments requiring immediate, measurable deliverables where organizations refuse any ambiguity in outcomes.
Variations
– For remote sessions, use digital collaborative tools like Miro for iceberg modeling to simulate hands-on system redesign. – For technical workshops, pair with EventStorming to let teams experience domain events driving architectural shifts. – When working with executives, frame short storytelling experiences around high-level outcomes rather than deep modeling.
Related Concepts
– Eric Evans, *Domain-Driven Design* – Experiential modeling aligns with Distilling the Ubiquitous Language through shared discovery. – Corporate Tribe, *The Corporate Tribe* – Shaman role creates ritual experiences to shift organizational mental models.
