
For most regulated companies, documentation is a burden rather than an improvement.
Quality documentation is something that a lot of companies, who deal with regulated industry, struggle with. We get it, you want to get the certification. Fast. Low cost. Therefore, you want to make sure that everything is documented and auditable. So, you throw together a bunch of documents that are barely readable and call it good.
The problem with this approach is that if your auditors come back with any questions or concerns, they will be able to easily find holes in your documentation because it was not created well. This is not only a waste of time, but it can also be costly for your business. The good news is that you can still get the certification you want and need without having to spend a lot of time or money on documentation. The worst part is that a wrong approach can lead to the need to create even more documentation after every audit, as a lack of definition and systematic approach does not provide any traceable reasons not to do so.
Instead of going deeper and deeper and letting the costs in the company become unbearable, I recommend implementing the following 5 measures immediately:
- Stop doing the same things over and over again! Regularly check the usefulness of your documentation. Stop doing things just because they have always been done that way, and start doing things that will take you forward.
- Stop believing that documentation is the answer to all your problems. Instead of dying in beauty and perfection, work out which content and format of documentation helps you to meet your needs.
- Stop with prose texts! Start writing documentation that is easy to understand, to the point and clearly conveys what needs to be done.
- Prevent documenting content multiple times with all your might. Evidence in IT systems that are regulatory-relevant must be stable and secure anyway, so additional documentation does not make sense. On the contrary, it is an additional source of errors.
- Never isolate the creation of documentation in quality management from research and development, because they “don’t have time” to write it! Never! Make sure those who write the documentation, need it and must master it content-wise.
The Bauhaus principle applies here: Form follows function.
People dislike writing documentation and often put it off, despite knowing that a well-written manual will save them time later. Instead of treating this topic stepmotherly and trying to somehow get away with a quick and dirty solution, I recommend understanding documentation as part of corporate communication. It links people and processes at the points where collaboration and IT systems reach their limits. Good design of documentation processes is at least as important as digital processes and teamwork.
