filmov
tv
Documentation is a Waste of Time.
Показать описание
Documentation is a waste of time.
Because documentation gets outdated as soon as you document. But even your website gets outdated – as soon as you create it.
It doesn’t mean that you should not have a website.
It’s just that you need to have the right framework, to keep the knowledge management system centralized. That can be updated conveniently.
Here is the best documentation framework I have seen:
- Buy an internal system that allows content authoring easily, just like your website.
- Create a framework on the basic guardrails like the page navigation etc. - If people can’t find the information they need, they would rather not document it. Who likes to donate when there is no reward in return? The reward could be personal satisfaction, but there has to be something.
- Have a couple of moderators who are willing to invest some time in making sure the guidelines are followed
- Have an internal communication channel like Slack and post any suggestions publicly so everyone knows what to keep in mind when updating the documentation.
- Have a reward system for people to always document.
- Document everything, internal policies and procedures, processes, how-tos, support tickets, and dictionaries. Anything and everything that a new hire would need.
If you maintain your documentation just the way Wikipedia is maintained, it will become the ultimate source of collaboration for the entire team.
But if you really want to master the art of documentation and maintaining a knowledge management system inside the org, you need to lead and be the role model for the team.
What has been your experience in championing a KMS and true knowledge management repository inside your organization?
Your take? Comment below!
—-----------------------------------------------------
💠Ring the 🔔 for notifications!
#ERP #data #ERPConsultant
Because documentation gets outdated as soon as you document. But even your website gets outdated – as soon as you create it.
It doesn’t mean that you should not have a website.
It’s just that you need to have the right framework, to keep the knowledge management system centralized. That can be updated conveniently.
Here is the best documentation framework I have seen:
- Buy an internal system that allows content authoring easily, just like your website.
- Create a framework on the basic guardrails like the page navigation etc. - If people can’t find the information they need, they would rather not document it. Who likes to donate when there is no reward in return? The reward could be personal satisfaction, but there has to be something.
- Have a couple of moderators who are willing to invest some time in making sure the guidelines are followed
- Have an internal communication channel like Slack and post any suggestions publicly so everyone knows what to keep in mind when updating the documentation.
- Have a reward system for people to always document.
- Document everything, internal policies and procedures, processes, how-tos, support tickets, and dictionaries. Anything and everything that a new hire would need.
If you maintain your documentation just the way Wikipedia is maintained, it will become the ultimate source of collaboration for the entire team.
But if you really want to master the art of documentation and maintaining a knowledge management system inside the org, you need to lead and be the role model for the team.
What has been your experience in championing a KMS and true knowledge management repository inside your organization?
Your take? Comment below!
—-----------------------------------------------------
💠Ring the 🔔 for notifications!
#ERP #data #ERPConsultant