Wouldn’t it be interesting if Leadership Decision Records (LDRs) were a thing?
(The equivalent of ADRs for software architecture)
@nick_tune or just use the term "decision records" - it's what I've been doing for a while. https://jon.sprig.gs/blog/post/2339
@JonTheNiceGuy @nick_tune my team uses Miro boards and "post its as decision" instead of textual records due to the reduced friction and the capability to visually organize decisions into application layers, or different viewpoints such as testing or observability. Less space to write in, but finding and moving content more quickly?
@giorgiosironi @JonTheNiceGuy @nick_tune How do you then keep track of the context that led to that decision? Context, alternatives, etc? Are those recorded on surrounding post its?
@noctovis @JonTheNiceGuy @nick_tune we have tended not to record the "why" as much as the "what". Sometimes there is a link to an example from the code, which provides context along with the position in the map e.g. what architectural layer we are in.
Our motivation was speeding up repeatable decision-making while we build new features, more than architecture auditing or evolution: that might be why. Assuming if we change decisions later on the context has changed enough that it needs to be evaluated again.
