I looked through about 8 of these templates before feeling the need to stop. While the content is mostly solid, the design and layout make them hard to use in practice.<p>I really appreciate the effort behind this, but they could benefit from a design pass to make them more usable and visually coherent.
Nit:<p>- Decision doc: It'll be great to have a "Stakeholders" section listing each stake holders' name , and they can add their concerns in that section to start discussion.<p>- Investigation doc: There should be a "things we tried so far" section listing the actions took to validate each hypothesis, and the outcome of those actions, in timeline order.<p>- 1:1 meeting note: there's a built-in building block support in Google Docs: <a href="https://youtu.be/S1ef5vvMT2k" rel="nofollow">https://youtu.be/S1ef5vvMT2k</a>
If only people would document... When I was a SW Eng Mgr, I had to stop approving commits/deploys because engs would not do something as simple as javadoc.<p>Once people started missing deliverables and having their comp and ratings impacted, documentation shot to 100%.