I’d rather they finish development of the actual product and get it to my door, than delay it by pulling resources to write instruction manuals for something that’s actively changing in development.
Writing manuals becomes an “If You Give a Mouse a Cookie” type of situation. Any attempt to handle one thing sparks a list of unforeseen questions that drags the process down.
Manuals that try to “keep things simple” and ignore complexity, are only good for people that tend to figure out things on their own and dont need the manual in the first place. People that need a manual to get them going will also need a manual that handholds them.
Just my perspective from product development in a small company where I designed everything that went out the door, and not only wrote the manufacturing procedures, also wrote the training material for our own technicians and the instructions for customers.
If you’re going to put the info out there, you either feel like a fraud because you know it’s too simple to really be useful, or you put exhaustive effort into something comprehensive, delay, delay, drive yourself nuts, put in 24 hour days because you still have to keep other work going. Then get reprimanded for producing a detailed 300 page manual for a million dollar portable structure, that’s actually useful to the customer. Oh and still get a ton of questions on things you never ever thought imaginable
It’s a No-Win either way.