by Organisers @virtualddd | Mar 13, 2026
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...
by Organisers @virtualddd | Mar 13, 2026
Avoid philosophical debates about uncertainty and experimental approaches. Instead, identify what the organization clearly wants to achieve—outcomes that keep coming up in product strategy, vision discussions, and understanding users. There's always inherent...
by Organisers @virtualddd | Mar 13, 2026
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....
by Organisers @virtualddd | Mar 1, 2026
When choosing an architectural approach, explicitly think through what it means for the teams that deploy, test, and support your software—not just what it means for developers. Introducing patterns like message queues or event sourcing changes how QA needs to test...
by Organisers @virtualddd | Feb 13, 2026
When you find yourself working much harder than usual to keep a session moving, to get people to add stickies, or to generate conversation, that effort is a signal that something beneath the surface is blocking progress. The facilitator shouldn't have to push...
