Recognise that your perspective is different from your users’ experiences and needs. Software is built for them and not for the developers, designers, product owner or service delivery team.
Your assumptions are your windows on the world. Scrub them off every once in a while, or the light won’t come in.
- Alan Alda
Why is it important to recognise user needs?
- Prevent bias and assumptions: Developers and product owners etc will often have a deeper understanding of the product than the average user.
- Increases usability and accessibility: By designing inclusively you increase access and adoption.
- Improves effectiveness, efficiency and reduces friction: If the product aligns with user expectations they can carry out tasks faster and with greater satisfaction. Abandonment is reduced.
How to Understand User Needs?
- User research: This can happen at any point during the product lifecycle from concept to end of life. It can include, but isn’t limited to interviews, surveys, and usability testing. We can assist you in finding student users through our partnership with the Bodleian student panel.
- Analytics & behavioural tracking: Using tools such as google analytics and Microsoft Clarity you can get a clear understanding of where people are staying and when they are drop off or out.
- Feedback loops: Review customer support tickets, reviews, comments on social media. All with give first hand accounts of where users have experienced issues.
