architectural-proposals

Document architectural decisions by creating a structured proposal that captures the problem statement, proposed architecture, and trade-offs. This approach aligns stakeholders before code is written, ensuring evidence-based prioritization and reducing rework.

Structure an architecture proposal with required sections: Problem Statement, Proposed Architecture, What Changes, What Stays the Same, Key Decisions Needed, Risks and Mitigations, and Scope, plus a structured implementation plan to capture full context.

Write an architecture proposal when architecture shifts invalidate existing assumptions, product direction changes require a new foundation, multiple waves will be affected, or external dependencies change, making a document cheaper to modify than refactoring code.

Manage risk mitigation by documenting risks and mitigations within the proposal, mapping clear wave and milestone impacts with decision ownership and traceability to reduce regression risk before implementation starts.

Documentation-driven design works for cross-wave architecture impacts by enforcing structured sections that capture problem statements, proposed architectures, changes, and risk decisions to align multiple milestones before implementation.