Most knowledge projects stall for the same three reasons. Here is how to avoid them.
Many organisations invest in a knowledge system and watch it go quiet within a year. In our experience the causes are rarely technical.
The system is nobody's job
Assign an owner and give them time to do it.
It sits outside daily work
If people have to leave their usual tools to use it, they will not. Build knowledge capture into the workflow they already follow.
Success is measured by volume
Counting uploads rewards clutter. Measure whether people find what they need.
Start small, pick one team and one real problem, and grow from there.