Anything that is related to "why" related to _changes in_ architecture and domain usually goes in for me. e.g.
- Why did we end up not using FIFO queues here?
- Why did we decide to disable users who did x?
- Why did we create a new module rather than updating the existing one?
I say "changes in" because we'd often write an architecture document at the start of a project. That document has the initial assumptions and reasonings. A decision record documents inevitable changes to the plan as we find out more about the problem space.
I also find having a person directly responsible updating the record is the best, if the project doesn't involve too many people.
- Why did we end up not using FIFO queues here?
- Why did we decide to disable users who did x?
- Why did we create a new module rather than updating the existing one?
I say "changes in" because we'd often write an architecture document at the start of a project. That document has the initial assumptions and reasonings. A decision record documents inevitable changes to the plan as we find out more about the problem space.
I also find having a person directly responsible updating the record is the best, if the project doesn't involve too many people.