4 ms·
Storing knowledge is a bit tricky. For a starter you have to consider the types of knowledge. Most commonly you talk about tacit[0] and explicit[1] knowledge.
by pathy 13y ago
Storing knowledge is a bit tricky. For a starter you have to consider the types of knowledge. Most commonly you talk about tacit[0] and explicit[1] knowledge.
Tacit knowledge is hard to communicate by writing or even verbally. Rather it is mostly transferred via learning by doing. In a software scenario tacit knowledge would probably be the code base. The style, naming conventions and what not of the code is likely to be relatively unique and it is hard to communicate via a document, rather the employees has to get a feel for the code, use and modify it. It takes time and you probably should have some kind of coaching set up for new employees coming in, especially if your company is specialized or uses something unusual.
You should also keep in mind that certain employees may possess unique knowledge and considering the relatively high employee turnover you should make sure that your processes don't fall apart if an employee leaves the company. Don't let people have their own pet projects that no one else knows anything about, especially if those projects are mission critical.
Explicit knowledge is easier to document and you can use stuff like Wikis or Confluence. Explicit knowledge is basically everything you can easily communicate via documents or verbally. So guidelines, processes and such.
If you got proprietary information or personal information of EU citizens you may want to consider a locally hosted solution, especially if you are located outside USA (avoid Google etc). I've used Wikis in the past but also had solutions like word documents with processes.
It does depend on your needs, simple word documents with processes may be enough. I know huge companies like Shell has had moderate success with a wiki solution[2]. I should have slides from a knowledge manager Shell presentation somewhere, will have a look around.
[0]: https://en.wikipedia.org/wiki/Tacit_knowledge https://en.wikipedia.org/wiki/Tacit_knowledge
[1]: https://en.wikipedia.org/wiki/Explicit_knowledge https://en.wikipedia.org/wiki/Explicit_knowledge
[2]: http://www.ikmagazine.com/xq/asp/txtSearch.Intranet/exactphrase.1/sid.0/articleid.0A6EF1DD-1D6A-4CD0-94EA-DC872A5A708E/qx/display.htm http://www.ikmagazine.com/xq/asp/txtSearch.Intranet/exactphr... (Old but may be relevant).
- mkuhn 13y agoThanks for this. I am definitely looking at how to store explicit knowledge. Tacit knowledge in my mind is a lot about your organizations culture and that needs to be lived. Luckily being based in Switzerland hosted solutions are not a problem but that is a different story altogether anyways.