Let me explain.
In many corporations, documentation is seen as a secondary resource. In other words, documentation is something you do AFTER a system has been created or AFTER a product has been created. This is like putting the horse after the cart. In actuality, documentation can be used as your literal road map to success because all details of a product or system are revealed in the documentation. So, in many ways, documentation should AT LEAST be a parallel endeavor alongside engineering and programming efforts as products and systems are created, tested, and deployed. Documentation loses its impact if it is done afterwards. Sure, you can consult with format product documentation after a project is done and before creating a second version. That is fine. But, better still is when you can use documentation DURING the product or system development process to fine tune details and the actual path of creation. Documentation REVEALS what is going well and what is not going well. Documentation is a true reality check. Documentation expedites your project time-wise and money-wise. Documentation is your wildcard ready to be played.
Cheers, Happy Friday.