Heuristics

Prioritise Documenting Impact Over Process Consistency

Authors: Peter Hunter, Elena Stojmilova, Kenny Schwegler, Andrea Magnorsky

Submitter: Peter Hunter

How should you handle varying levels of adoption for decision recording across teams?

Instead of enforcing strict consistency in how often teams write decision records, focus on the outcome. The critical measure is whether impactful decisions are documented before they cause unforeseen problems. Allow teams to find their own rhythm as long as this core principle is met.

Example

Rather than forcing all teams to write ADRs with the same frequency, the goal was to ensure no undocumented decisions caused problems later. This allowed each team to find their own balance.

 

Tags

Follow us

Read our latest news from Virtual DDD on any of these social networks!

Recent heuristics

Discussed content

Sorry, no results found!

Whoops... we couldn't find what you're looking for