Notes · Why should a problem be picked?

Impact analysis for an identified UX problem

Background

In June 2024, our team was invited to work onsite for three weeks, providing an opportunity to meet in person. I took this chance to connect with our data team to understand how they use data to identify and pitch problems.

Getting started

While designing 0-1 products at smallcase Gateway, I realized that there are still a lot of things we can do to improve user experience but limited engineering bandwidth hence understanding evaluating what problem should be picked became crucial?

Data became the key to answering these questions. This led me to explore how I could identify and prioritize UX problems using data.

Steps:

  1. Identify Issues:

I listed all known problems in our products.

  1. Prioritize based on impact:

I ranked these problems by considering:

  • What’s the revenue impact?

  • How many users are affected, and does this issue appear in the happy flows?

  • Is the problem occurring at the top or bottom of the funnel?

  • Is this issue a major blocker, or can high-intent users still proceed?

  1. Feedback from product folks

Once I did my research & curated all the points I had. I took everything to discussed with the PMs & Product analyst to ensure to i am going the right direction

Feedback 💡

Understand how you can do revenue forecasting by comparing different flows to have a basic benchmark in place.

Final outcome

I mapped the loan application journey and identified key drop-off points to estimate how many users could complete the flow with the proposed enhancements.

While I can’t share exact figures, these changes were designed to remove blockers, increase user completions, and positively impact monthly revenue.

As a result, we projected 'X' additional users per month would complete the loan flow, with a median loan amount of 'Y' per user

©2024 Vaibhav – The story continues