4 ms·
Solution: Hire a librarian. I'm not kidding in any way. They are massively underemployed and are very good at exactly this task. Back at PBwiki we hired a libra
by iandanforth 9y ago
Solution: Hire a librarian. I'm not kidding in any way. They are massively underemployed and are very good at exactly this task. Back at PBwiki we hired a librarian who not only organized all the things but ended up running and building our support organization.
Do not tell them what tool to use, let them own your knowledge base and make their requests for information understood to be P1 priority.
- maxxxxx 9y agoI'll second that. In one company I worked at we had a tech writer we could throw stuff at and she did the work of structuring and editing. This worked great.
- Viliam1234 9y agoI am afraid that the idea of hiring an expert for a specialized task goes against the trend of "full-stack developers". Imagine explaining why it is not necessary for the project to have a database expert, a back-end expert, or a web expert... but you definitely need a wiki-pages-organizing expert.
- clintonb 9y agoThe librarian is not for a single project, but the entire company. The librarian's job is to make sure that as much information as possible is stored in a manner that is searchable and accessible to all employees who need the information when they need it with minimal effort.
- stephenr 9y agoPerhaps that's a cue that "full stack developer" is just a cute buzzword for "jack of all trades, master of none".
- tarr11 9y agoThis is a brilliant idea. I really never thought of actually having a person responsible for internal corporate knowledge, but it makes a lot of sense!