Ideas, beliefs, and values create cognitive patterns—when we think of something, our minds go in particular familiar directions. Teams moving from CRUD monoliths to microservices will architect microservices to be tightly coupled because their thinking remains tightly coupled. Your role is to listen energetically for places where the conversation will go down the same path and end up in the same place, even though it seems like new thinking. Then introduce a different question or perspective at those moments.
Example
When facilitating teams through architecture changes, you need some sense of what direction might work differently while remaining genuinely open to discovering you're wrong. You're flying with the flock of birds, grounded enough in the space to facilitate effectively. If you try to marshal or control the direction, it won't work. If you turn off your brain and just flow with it, you're not adding useful tension where it might help. Sometimes facilitation means helping people articulate what's happening—that's valuable. More often, you're facilitating toward an insight nobody has had yet, looking for opportunities to open a window differently.
Context
This requires thinking about what change you're actually trying to enable. If you have no idea where a different direction might lead, you cannot do this kind of facilitation. At the same time, if you're just bringing people to your predetermined idea, you might as well tell them directly and be intellectually honest about it. The expertise being developed here is recognizing cognitive and energetic patterns—where will this thinking lead, where might a different question help, when should you add tension and when should you simply let the group articulate their own understanding.
When This Might Not Apply
– When you lack any hypothesis about alternative directions—facilitation becomes aimless articulation without tension. – Teams rigidly committed to predetermined solutions—your nudges get dismissed as bias rather than helpful interruption.
Variations
– For technical workshops, interrupt during EventStorming when CRUD patterns reemerge in event modeling. – For remote sessions, use timed breakout rooms to force pattern breaks through diverse grouping.
Related Concepts
– Rebecca Wirfs-Brock, *Design Heuristics* – Cognitive pattern recognition aligns with responsibility-driven design critique sessions.
