by Organisers @virtualddd | Jan 27, 2026
Before running a collaborative session, explicitly challenge the stated purpose with participants. Ask who agrees and who doesn't agree with why they're there. When someone asks you to run a workshop because "the team really needs this," treat that...
by Organisers @virtualddd | Jan 20, 2026
Decisions are made based on the context at a specific point in time, such as team size or available technology. Documenting this original context allows you to determine if it has changed enough to justify revisiting the decision. This prevents historical choices from...
by Organisers @virtualddd | Jan 20, 2026
After a decision is made, allow dissenting members to express their concerns freely without becoming defensive. Then, shift the conversation by asking, “What do you need to go along with this decision?” This validates their perspective while focusing on a constructive...
by Organisers @virtualddd | Jan 20, 2026
Treat testability, observability, and recoverability as first-class design concerns, not afterthoughts. A system that cannot be easily tested, understood in production, or quickly restored is inherently low-quality. Build in the necessary instrumentation, APIs, and...
by Organisers @virtualddd | Jan 20, 2026
Reverse-engineer Architecture Decision Records (ADRs) for foundational decisions that were never formally documented. This makes implicit constraints explicit, clarifies historical context, and allows the team to re-evaluate them. It provides a clear baseline for new...
