This is one way that you can design your software - follow existing conventions so that people's existing knowledge is useful for understanding your software.
The alternative can be summarized as "not doing that" and personally I don't see that solving any problems. It just means people have to learn it from scratch instead. And it's not like anyone actually reads manuals and such.
Nintendo, for example, regularly hires game designers with no game design experience.
Famously, there was a shoe designer who was hired on the BOTW team. The fresh perspective keeps Nintendo games from falling into idiosyncrasies, which is part of the reason children and adults can just walk up and play most Nintendo games and have immediate without needing prior gaming experience.
I think it’s valuable to have non technical designers and QAs for that reason.
Sure the fresh perspective fades after a while, but it’s still valuable AND gives us in tech a reason to hire those not in tech.
