When we experience something broken in digital products, we often call it poor design. Or at best, the customers may say that the information is incomplete, or is not clear. They do not question the engineering.
Even when the customers are from a technology background and if they are using a product with poor user experience, they rarely call it as a badly written code.
Is it really bad design? If the customers cannot fill an online form because it is not designed well, or if they cannot use it confidently because of some usability issues, isn’t it an engineering failure as well?
Or, is it because the code is badly written? If the code is badly written and the users are struggling to use the product, isn’t it automatically a UX failure?
Where do we separate UX and engineering?
Product sense (my related post on LinkedIn, opens in a new tab) or our product judgment is not about design, interactions, code, DevOps, product marketing, content design, or research—product sense is collective. If you divide a mission into multiple missions, it is likely to become and behave as a continent and continents rarely have a single mission.
PS: To say that content design leadership or product content strategy could have saved them here is a bit of overstatement.
