Guidelines fo Mek Decision Last

We don learn dis lessons for our work wey fit be guidelines and assessment to achieve sustainable decisions:

Use lean/minimalistic approach for di initial decision documentation.
Prioritize and capture all di important decisions wey relevant well to document and to understand di target architecture.
Detail di particularly important decisions with full-blown templates only after di initial work don finish (dat na, wen di decision makers dey content with di architectural decisions wey dem make and dem sure say dem no go need to revise dis decisions soon).
Use di lean/minimalistic versions from step 1 as short version of documented decisions with di right granularity level to give overview of di detailed decisions, and also for trivial or obvious decisions.
Wherever e possible, use architectural knowledge wey dey already, either from guidance models or from other sources. Review and extend such knowledge and fit am to di context of di specific decision.
Make sure say traceability links dey established between decisions and both requirements and architectural designs/code.
Provide automated consistency checking to make sure say di traceability links dey in sync after change. Limit di number of dependencies between decisions and other software artifacts.
Apply di guidelines for di justifications consistently and forcefully—na dem be di most important part of di decision documentation because dem dey give di rationale.