I wear a Tilley Airflo pretty much any time I am outside.
I need a wide broom to protect my eyes from the sun (early cataracts). I need a hat that is useful for outdoor fun but also looks good around town. I do not want to worry about rain or have a lot of upkeep.
I wash my Tilley in the machine. I get compliments everywhere I go. It works great on the trail, and looks great paired with a sport coat for a country-boy-on-the-town sort of look. I can’t recommend that hat enough.
Good documentation should, in part, tell people where to click. I have designed software documentation for high performing individuals at leading global companies, and I have designed software and hardware documentation for minimum wage fast food workers with limited English proficiency. In both extremes, I showed them exactly where to click on the screen at each step.
You might not need that level of help, but many people do. Others do not strictly need it, but they prefer the simple instruction set. “Click here then here,” instructions ease the transition into a new system one needs to learn, or it removes the need entirely to learn a system one uses infrequently.
The problem is that making good documentation is difficult and time consuming. It relies on a fundamentally different skill set than coding or even UI design.
I agree that the ideal is for software to not need any documentation. In my experience, I have yet to see software that rises to that task and is used across a variety of experience levels and societal cross sections.