by Organisers @virtualddd | Jul 21, 2026
Most decisions in software teams don't fail because people disagreed. They fail because people thought they agreed, but they didn't — and nobody found out until much later. You walk out of a meeting feeling good about where things landed, and three weeks...
by Organisers @virtualddd | May 12, 2026
We've all been in that meeting. Someone proposes a solution, someone else proposes a different one, and within minutes the room has split into camps. People stop listening and start waiting for their turn to argue. The discussion goes in circles, nobody feels...
by Organisers @virtualddd | Apr 28, 2026
We often assume that architects working on the same system share the same understanding of its structure. They're looking at the same code, working with the same components, attending the same meetings. But that assumption rarely holds up when you actually test...
by Organisers @virtualddd | Mar 31, 2026
We often assume that resolving a major outage requires centralized command and control—getting the right experts in a room and coordinating their efforts until the problem is solved. But sometimes the best thing incident commanders can do is create space for the right...
by Organisers @virtualddd | Mar 17, 2026
We hit resistance in our architecture work, and what do we do? We explain more. We create another diagram, write another document, schedule another meeting to walk through the rationale. After twenty years of this pattern, Diana Montalion realized she was pushing the...