While a technical approach to knowledge management sometimes could benefit from a “big bang”, this usually produces just a technological implementation.
But who will maintain the processed knowledge stored inside the knowledge management system? Certainly not the knowledge producers, as it will be completely different from the source.
Each document has (or should have) a destination public, i.e. an intended audience.
If you cannot define the audience, chances are that your document will not achieve the intended results.
But do you really need to write the same item time and again? The risk is that your knowledge producers will spend seven hours reporting in slightly different formats what they spent one hour doing.
While knowledge production obviously should stay with those who own the knowledge and are able to make it evolve, knowledge retention and communication might involve a differentiation of roles based on your own specific organizational culture and structure.
As an example, consider the differentiation between “knowledge producers” and “knowledge consumers”: what the former produce might require somebody belonging to the organization from the latter and able to “convey the message”.
This is probably already part of your practices, as e.g. you would not expect to communicate with the CEO as if (s)he were a production engineer: but data management tools often took over common sense- also if there is an alternative, i.e. to use both tools and common sense.