Teamwork advice fo ADR

If you dey think to use decision records with your team, then na dis advice we don learn from to work with plenty teams.

You get opportunity to lead your teammates, by to talk together about di "why", instead of to force di "what". For example, decision records na way for teams to think smarter and communicate better; decision records no valuable if na just after-the-fact forced paperwork requirement.

Some teams like di name "decisions" well pass di abbreviation "ADRs". Wen some teams use di directory name "decisions", e be like say light bulb turn on, and di team start put more information inside di directory, like vendor decisions, planning decisions, scheduling decisions, etc. All dis kinds of information fit use di same template. We hypothesize say people dey learn faster with words ("decisions") pass abbreviations ("ADRs"), and people dey more motivated to write work-in-progress docs wen dem remove di word "record", and also some developers and some managers no like di word "architecture".

For theory, immutability na ideal. For practice, mutability don work better for our teams. We dey insert di new info inside di ADR wey dey already, with date stamp, and note say di info come after di decision. Dis kind approach dey lead to "living document" wey all of us fit update. Typical updates na wen we get information thanks to new teammates, or new offerings, or real-world results of how we dey use things, or after-the-fact third-party changes like vendor capabilities, pricing plans, license agreements, etc.