-
1/ I recall a team session that we were defining that the product was: - *Easy* to use - *Simple* Those qualities look like vanity qualities. Instead define: - Conversion rate in this flow of N% - Support color-blind Then the user helps you validate the qualitiesPermalink On twitter.com
Mood +14 🙂
-
2/ Saying "our product needs to be easy to use" is abstract to me and opinion based. Instead, debate which user flows are business critical and how you can measure that you're succeeding at them. As well some accessibility qualities.Permalink On twitter.com
-
3/ I see this kind of situation when Designers are unable to influence the Team to invest more in the look and feel. When we start listening "we need to ship fast, let's take some short cuts", it's quite possible that those tradeoffs affect the UI/UX effort.On twitter.com
-
4/ If the organization has different incentive systems per role and how they measure performance, these conversations are accentuated. We aren't aligned. So, when hearing "our product needs to be easy to use" explore the reason behind it.Permalink On twitter.com
-
5/ The first response might be "it's an organization goal". The inner reason could be "my performance is measured by how the application looks" Understand the root people incentives and motivations behind the "easy"! They will drive way more interesting conversations 😊Permalink On twitter.com