by Organisers @virtualddd | Oct 13, 2025
A facilitator can offer to formally make the decision and take on the accountability, after asking for the team’s consent. This unblocks the process while protecting the psychological safety of team members who do not feel ready for that level of responsibility. It is...
by Organisers @virtualddd | Oct 13, 2025
Teams are more likely to internalize and value architectural principles after they have personally experienced the pain caused by their absence. Without this context, principles can seem like abstract, unnecessary overhead. An architect’s role is to share their own...
by Organisers @virtualddd | Oct 13, 2025
When a team’s decision optimises for their immediate convenience at the cost of system-wide integrity, the architectural perspective must prevail. The architect’s role is to advocate for the long-term health of the system, even if it means more work for a team in the...
by Organisers @virtualddd | Oct 13, 2025
Instead of relying on theoretical pros and cons, assign a task to build a small, real feature using each competing technology. This provides concrete, context-specific data and direct experience for the team to base their decision on. It moves the discussion from...
by Organisers @virtualddd | Sep 29, 2025
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...
