The first thing I wanted to get right wasn't the interface. It was understanding the problem I was trying to solve.
DAY 1: THE DISCOVER PHASE — UNDERSTANDING BEFORE DESIGNING
Video Link - https://vimeo.com/1242583687
Before I could start thinking about colours, layouts, buttons, or navigation, I needed to understand the people who would eventually use this Bus App.
I didn't want to build another transportation app simply because I could. I wanted to understand the existing experience, identify gaps, and find opportunities to make things better.
So, I started with four key activities:
1. Competitive Analysis
I explored existing solutions in the transportation space to understand what was already out there, what they did well, and where there were opportunities for improvement.
2. User Survey
I wanted to hear directly from potential users. What are their experiences with bus transportation? What challenges do they encounter? What would make the experience better?
3. User Interviews
Surveys provided useful insights, but I also wanted to hear people's stories in their own words. The interviews helped me explore their experiences and understand the problems beyond surface-level responses.
4. User Personas
With the insights gathered, I began developing user personas to give the research a human face and help me understand who I was designing for.
Why did I spend time on all these?
Because it's easy to assume you know what users need. But assumptions can easily lead you to build the wrong solution.
I wanted my design decisions to be informed by actual user needs, not just personal preferences.
And that was how the journey began.
Next up: The Define Phase. How do you turn all these discoveries into a clear product direction?
We're just getting started! 🚀
#ProductDesign #UXResearch #BuildInPublic
View passport