Indeed it is -- it's perhaps the central way developers offend their customers, let alone misunderstand them.

One problem is it is met from the other side by customers who think they understand software but don't actually have the training to visualise the consequences of design choices in real life.

Good software does require cross-domain knowledge that goes beyond "what existing apps in the market do".

I have in the last few years implemented a bit of software where a requirement had been set by a previous failed contractor and I had to say, look, I appreciate this requirement is written down and signed off, but my mother worked in your field for decades, I know what kind of workload she had, what made it exhausting, and I absolutely know that she would have been so freaking furious at the busywork this implementation will create: it should never have got this far.

So I had to step outside the specification, write the better functionality to prove my point, and I don't think realistically I was ever compensated for it, except metaphysically: fewer people out there are viscerally imagining inflicting harm on me as a psychological release.