Wouldn’t it be interesting if Leadership Decision Records (LDRs) were a thing?

(The equivalent of ADRs for software architecture)

#Leadership #SoftwareArchitecture

@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?

Good question @noctovis !
The templates I use all have "context" as one of the headings. The rest of the template is as follows:

```
# {0000}. {TITLE}
Date: {yyyy-mm-dd}
## Status
{Accepted|Proposed} by {author}
{Superceded by 0000}

## Context
{Given external factor A and B, a choice was made between options 1 or 2}

## Decision
{Option X was selected because REASON}

## Consequences
{Because X was selected project Z can now proceed. Project Y cannot.}
```
/ @giorgiosironi @nick_tune