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
Before committing to a major architectural change, explicitly map it against the concrete frustrations that make the team's job difficult. A proposed solution might use modern technology but still leave developers dealing with the same unpleasant work. If the new...
by Organisers @virtualddd | Mar 1, 2026
When someone pushes hard for a specific technical solution, they're usually operating from an underlying value or concern that they haven't made explicit. Before evaluating technical options, dig into what's driving the strong preference. Is it fear of...
