4 ms·
A trick I've used effectively is to have a "doc of docs" - a document that tells you where all the other documents for a project or team live. You can do this
by simonw 7y ago
A trick I've used effectively is to have a "doc of docs" - a document that tells you where all the other documents for a project or team live.
You can do this as a wiki page or a Google Doc. The important thing is that the answer to the question "where's the documentation for X" should ALWAYS be "it's in the doc-of-docs".
Then you can take it a step further: you can say "it's in the doc-of-docs... and if it isn't, when you find it, add it to the doc-of-docs!"
It's a universal truth that documentation for projects and teams ends up scattered in many different places. A doc-of-docs is a lightweight technique that can really help here.
- chasedehan 7y agoNotion is wonderful for this. It’s like a wiki with the ease of use of google docs. My company has basically everything on Notion and any time someone asks a question more than once, it gets added
- prepend 7y agoI like this “master read me” approach and try to also reference the lord of the rings poem to both try to make documenting fun and to explain the intent. Three Docs for the Product-kings under the sky, Seven for the Dev-lords in their halls of stone, Nine for Mortal Men doomed to die, One for the Dark Lord on his dark throne In the Land of Mordor where the Shadows lie. One Doc to link them all, One Doc to find them, One Doc to bring them all, and in the darkness bind them, In the Land of Mordor where the Shadows lie.