by Organisers @virtualddd | Nov 21, 2025
When applying DDD to a legacy system, accept that the initial boundaries will be imperfect and 'not pretty.' The goal is to create a starting point for team autonomy, even if it requires pragmatic compromises on architectural purity. These boundaries can be...
by Organisers @virtualddd | Oct 23, 2025
Augment formal decision records, like ADRs, with qualitative data about the human element. Include fields for the team's sentiment, confidence level, or readiness to commit to the decision. This provides crucial context for future reviews and helps gauge the true...
by Organisers @virtualddd | Oct 23, 2025
Apply flow metrics to the decision-making process itself to identify systemic issues like paralysis or weaponisation. Track metrics such as: Decision Frequency: How many decisions are we making per month? Decision Lead Time: How long does it take from identifying a...
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 | Sep 16, 2025
Context Rather than writing a decision record after a decision has already been made, which can feel bureaucratic and less useful, teams should start the document early in the decision-making process. This makes the process more useful and collaborative. The ADR...
