You're spot-on about the poor quality of many technical manuals. My career was in aerospace software. Many years ago I wrote a system to search vendor records to find out who might supply particular items. This was in the days of those pokey, old, IBM 360s and dozens of reels of mag tape. My manager insisted on describing the system to the customer (NASA) as a "real-time" system, under protest from me, and forced the technical writers to put that in the documentation. The problem was that "real time" was an average of 6 hours of dedicated 360 time...... 😱
It happens all the time. The designers write a design spec, the software types come up with all the functions and maybe a few more on the side, but do them differently than the tech writers envision them. Then out come the products and unmatched or incomplete user manuals. And that doesn't even account for the translation from Hindi or Mandarin Chinese on many products.
Heath Kit (RIP) used to solve the problem by going out into the supermarkes of Grand Rapids and asking about 15 people, primarily housewives in those days, to come put a kit together. They would lay out the proper tools for them, give them the parts and the technical manual, and ask them to put the kit together. The instructions to the folks were "If you have any questions, ask us." Any problems popped up before the product got into the hands of the consumer. Too much to ask these days I suppose, and a certain knowledge of what the product actually does is needed, not just a set of rules about what gets soldered, where.