risk-assessment

A risk assessment before software design uses a structured self-questioning framework to validate premises, run root-cause analysis, check solution depth, identify risks, and evaluate design judgments before action.

Documenting architecture decisions during planning is best handled by recording evaluated risks and design judgments in a lightweight ADR format, capturing decisions in the present tense for traceability.

Root-cause analysis mitigates implementation risks by enforcing depth checks through repeated self-questioning, preventing shallow solutions and ensuring the fundamental problem is identified before action.

Risk response strategies like avoidance, mitigation, transfer, and acceptance are needed in software planning after risks are identified through structured self-questioning during the design phase.

Yes, you can apply ADR documentation to early architecture decisions by using a lightweight ADR-like format that records design judgments and identified risks without adding heavy overhead.

Shallow problem analysis leads to design risks because it skips premise validation and root-cause analysis, allowing superficial solutions to proceed without identifying fundamental implementation risks beforehand.