Why User Research Beats Pretty Mockups
It's tempting to jump straight into Figma and start crafting beautiful screens. But the prettiest mockup in the world won't save a product that solves the wrong problem. In my ~2 years as a UI/UX designer, the biggest wins came from research — not pixels.
Start with people, not screens
Before opening any design tool, I talk to users (or proxies) and review the data we already have. A short interview or a quick survey often reveals that the real pain point is different from what stakeholders assumed.
In one project, the team assumed users wanted a feature-rich dashboard. After 5 user interviews, we discovered they actually needed a simple mobile-first checklist. The research saved months of development on the wrong product.
Research doesn't have to be expensive or time-consuming. Even 30 minutes of user observation can surface insights that would otherwise take weeks of A/B testing to discover.
Lightweight research that fits any timeline
- User interviews — 3–5 conversations surface 80% of the insights
- Usability testing — watch real users attempt real tasks
- Analytics review — where do users drop off today?
- Competitive teardown — learn from what already exists
For tight deadlines, focus on the quickest wins:
- Guerrilla testing: Grab 5 people at a coffee shop, give them a task, watch them struggle for 10 minutes. You'll learn more than from hours of internal debate.
- Crazy 8s: Sketch 8 ideas in 8 minutes. It's fast, it's messy, and it gets ideas out of your head before you commit to pixels.
- Analytics audit: Check your existing data. Where's the drop-off? What's the most-used feature? Let data guide your priorities.
Turning research into design
Once I understand the user, I move to wireframes and user flows, then interactive prototypes in Figma. Research becomes the north star that keeps the design honest — and makes handoff to the frontend team smoother, because every decision is backed by a reason.
Document your findings. Create a simple research summary that includes:
- Key user quotes that stuck with you
- Pain points ranked by frequency
- Success criteria for the design
- Assumptions that still need validation
This document becomes your design brief. When stakeholders question a decision, you can point to the research. When developers ask why a feature exists, you have the answer. Research isn't just about discovery — it's about alignment.
Research in a backend context
As a backend developer, I apply the same mindset to API design. Before writing code, I ask: Who will consume this API? What are their use cases? What errors will they encounter? Research isn't limited to UI — it's about understanding your users, whether they're clicking buttons or making HTTP requests.
Pretty is easy. Useful is hard. Do the research, and you get both.
— Fegi Sucepto Priawan · UI/UX Designer & Backend Developer