On the other hand, you can always tell software that was written (and/or bought) by someone who knew they'd never have to use it themselves. It's why most corporate software is so bad: it's written by someone who really couldn't care less about General Ledgers, and it's bought by the CFO who has staff to actually operate it.
I always get a bit irritated when people make the "people first" argument. It's not that I disagree with putting people first. It's just that "putting people first" always seems to mean "being a good cog in the machine".
There's more to putting people first than writing documentation and explaining your code to other people. Those are important, but they mean putting the task first, not the people. To put people first, you have to do things like: listen to others, empathize with them, use tact, compromise, and occasionally do something impractical for no other reason than to help work suck a bit less.