Many companies store huge amounts of documents, but every team does it in its own way. One template can quickly result in thousands of variations. If robust documentation principles are not used from the very beginning (checklists / reduction in free text, visual indications, etc), it will be a nightmare to make sense of that data afterwards. Also, there is no value in generating large amounts of text data unless you can easily scan it and retrieve the information of interest

What I wrote wasn't simply a poorly specified product requirement document ;) Instead it was a general idea.

Better and more granular documentation in a form that can be interpreted by humans and also machine readable would be a desirable outcome for any system. Especially true for systems in which the builders and operators are being replaced or EOLed

Better?