Write the decision record before memory edits it
Capture an async decision with context, options, rationale, consequences, and review trigger.
lost rationale Support needs to explain a refund delay. The team remembers the decision but not the constraints or rejected options. Without rationale, old decisions look careless even when they were sensible. ADR pattern Context -> Options -> Decision -> Consequences A decision record stores why a call was reasonable at the time. That protects future work from memory drift. Reflex Post the final answer only. Future readers can understand and adapt the call. Document the tradeoff, not just the answer. 01 Context 02 Options 03 Trigger Capture context why now
Sign up free — one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in