3 ms·
Show HN: Decision record – how to improve teamwork decisions by using templates
- jph 7y agoI'm the author and I welcome constructive advice. This repo is a generalization of a sibling repo for architecture decision records.
- xwowsersx 7y agoThis just seems like a whole lot of structure imposed on what are, essentially, "notes". It's not like it makes any special tooling possible either - the section on using DR with tools lists Google Drive and git...I'm not trying to crap on this, but it seems like a lot of time spent on a hollow pursuit.
- jph 7y agoThanks for commenting. Can you help me understand your comment more? When you and your teammates want to make a significant decision (such as what technology to choose), and you want to do evaluations and communications, how do you do it?
- xwowsersx 7y agoWe talk in person or use Slack. We certainly don't impose some conventions on how to have the discussion. This is the kind of thing where even we took the time to use DR, we'd never use it again.
- jph 7y agoPerfect thanks. I'll add a section now that addresses your point.
- yitchelle 7y agoI guess talking in person or over slack would facilitate the need to discuss the pros, cons, impact etc. of the decision. How do you socialise the decision to the rest of the current and future team?
- Noumenon72 7y agoDon't you have trouble remembering why you made certain decisions, or even which way the decision went? I have a terrible problem with not being able to remember other people's logic after about a week or so. Then I deliver things that are more like my own preferences than they should have been.