>the fact is they can incredibly helpful and save you a boat load of time and effort trying to understand the product in many cases.
I take having to explain what our product does to users as a failure on our part. We have the same mentality when we have to personally explain what code does to our colleagues. We take the necessary measures of using better abstractions, writing documentation and Wikis, simplifying code, and making efforts so that "failure demand" does not arise.
In terms of product, it's either our documentation sucks, or a problem of "affordances and signifiers", or a problem of targeting the "wrong" users.
I take having to explain what our product does to users as a failure on our part. We have the same mentality when we have to personally explain what code does to our colleagues. We take the necessary measures of using better abstractions, writing documentation and Wikis, simplifying code, and making efforts so that "failure demand" does not arise.
In terms of product, it's either our documentation sucks, or a problem of "affordances and signifiers", or a problem of targeting the "wrong" users.
See also: https://vanguard-method.net/failure-demand/