by Organisers @virtualddd | Oct 13, 2025
Recognise that not all team members want to be involved in every architectural decision, and this is acceptable. Forcing participation can be counterproductive; their silence may indicate a lower psychological safety or a preference to focus elsewhere. The goal is to...
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 | Jul 22, 2024
Short description Align boundaries with the parts of the domain where there are different domain experts (not different people but different domain skills/knowledge). Context We should align boundaries in sociotechnical systems with our business processes to minimise...
