When Explaining More Isn't the Answer

We often assume that when people resist a new architectural direction, the answer is to explain better — clearer diagrams, more detailed documents, another walkthrough of the rationale. Diana Montalion spent twenty years perfecting this instinct. Then she realized she was Sisyphus: pushing the same rock up the same hills, and getting flattened every time it rolled back down.

The shift came at Kripalu, a retreat center where Diana had gone to rest from the exhaustion of constant explanation. The environment was overwhelmingly female — the opposite of the tech spaces where she'd spent her career, often as the only woman in the room. Learning happened there through movement and experience, not endless discussion. When her phone pinged with a question from the DDD Europe organizer — "You said this could be a workshop. What would you do?" — the answer suddenly felt obvious: design an experience, not an explanation.

What followed was a workshop that used the iceberg model to help participants understand how systems generate outcomes — using, as their subject, the fact that 91.88% of software developers are male. Nobody debated gender politics. Instead, working in groups, they modelled how a system produces that result, then designed a different system. Diana has run it four or five times now and learns something new every time. Back in her current role, she's applying the same logic to architectural change: rather than explaining until people understand, she tries things with them — and finds that people who were deeply resistant often pick up the ball and run with it once they've had the experience.

This conversation explores what it actually takes to move from explanation to experience — including how to work inside genuine uncertainty, how to interrupt cognitive patterns without steering people to your predetermined answer, and why facilitative leadership is, in Diana's words, genuinely harder than just telling people what to do.

Key Discussion Points

1. [00:01] The Sisyphus Pattern: Diana names her core habit — when facing resistance, explain more — and the exhaustion that finally forced her to question it
2. [03:00] The Kripalu Moment: A retreat centre, a predominantly female room, and a way of learning through experience rather than discussion that stops Diana cold
3. [04:00] The DDD Europe Workshop: How a well-timed ping from the conference organiser became the prompt to design an iceberg model workshop unlike anything she'd done before
4. [06:00] Modelling the Patriarchy: How asking teams to model a system that produces 91.88% male developers — not to debate gender, but to practise systems thinking — unlocks participation in a way no lecture ever could
5. [08:00] Architectural Miracles: In her current role, Diana catches herself falling back into "explain more" — and experiments with just trying things instead, with surprising results
6. [12:00] There Is Only Uncertainty: Diana's perspective on complexity, consent, and why promising important insight rather than solved problems is the honest deliverable
7. [22:00] Flying with the Flock: The delicate balance between listening, facilitating, and nudging — knowing when to interrupt a cognitive pattern without simply steering people to your own answer
8. [28:00] A Science and an Art: How facilitation is both deep listening and an energetic interruption of pattern — and why the hardest part is the work itself, once the friction is gone

Guest: Diana Montalion Hosts: Andrea Magnorsky, Kenny Schwegler

Part of the Stories on Facilitating Software Architecture and Design series from Virtual DDD.