To a degree, the same happens with a design doc - you may start it with a peer, or have manager oversee it, or pull someone from a team, from which you rely on

To a degree, the same happens with a design doc - you may start it with a peer, or have manager oversee it, or pull someone from a team, from which you rely on specific technology to gain more confidence for you, and whoever later reads the design doc that all important bits are covered... For example decision to use system A (from your point of view) may be good idea, but owners of system A may no longer support it, or may have in plans to deprecate it soon, but haven't announced it yet, so adding key personnel there would help for sure. I'm trying this new model at my new workplace, but I'm already seeing pain doing this with Outlook (the desktop version), the Mobile version is much better in this respect, though the comment system need some features, that I got used to (assigning action-items). The other approach would be google for business, but I'm not a decision maker here. (Or some other cool product - EtherPad?)