4 ms·
One trick I've used successfully, at least at the team evel, is to maintain a "doc of docs". This is a document which exists to link to other documents. I use
by simonw 9y ago
One trick I've used successfully, at least at the team evel, is to maintain a "doc of docs".
This is a document which exists to link to other documents. I use a shared Google Doc for it (which is almost equivalent to a wiki).
Since it's a document (and not a folder or a spreadsheet) each linked document can be combined with some explanatory context - is the document current? What does it cover? etc.
I also like splitting my doc-of-docs into different headings, for example:
Current
Outdated
Related projects from other teams
The key benefit of the doc-of-docs approach is that the answer to EVERY question about "where can I find documentation for X" is "Look in the doc-of-docs". And the follow-up answer if they don't find it there is "Go and find that document, then add it to the doc-of-docs".