Research isn't about endless reports - it's about learning what truly matters to the people you're designing for. Insights turn data into direction. They help you see patterns, understand motivations, and design with clarity instead of assumptions.
This article focuses on three fast, practical ways to learn from users and translate that learning into design decisions.
Learn more in one afternoon than a week of guessing.
Action play: Talk to 3-5 users this week. No script, no formal study - just quick, genuine conversations. Literally, pick up the phone and call them.
Ask what they use your product for, what's hardest about it, and what they wish it did better. Take notes fast. Write down exact quotes, not summaries.
Example: For a budgeting app, you might hear: "I just want to see if I can afford this before payday." That one sentence can reshape your entire value proposition.
Share what you learn with your team the same day - one slide, three takeaways.
Why: You don't need a research lab to get real insights. Short, informal talks reveal the truth faster than any assumption. It keeps you close to the people you design for.
Watch real users in their real environment.
Action play: Spend one hour watching a user interact with your product in their natural setting. Let them work the way they normally would - no prompting, no guiding. Take notes on what they do differently than you expected.
Example: You're designing a delivery tracking app and notice that couriers keep screenshots of addresses instead of using the in-app map. That small observation exposes a huge usability gap.
Summarize what surprised you most and share three actionable insights with your team.
Why: What people say and what they do are rarely the same. Observing in context reveals real habits, workarounds, and pain points that interviews can't capture. It's one of the fastest ways to turn design from theory into reality.
Prioritize what hurts most - for users and the business.
Action play: List all the pain points you've found from research, feedback, or testing. Then draw a simple pyramid with three levels:
Sort each issue into the right level.
Example: "Can't complete payment" goes at the top - critical. "Doesn't remember last search" lands in the middle. "Irregular use of colors" sits at the bottom. Once sorted, focus your next design cycle on the top layer only.
Why: Not all pain points are equal. Teams waste effort treating every issue the same. The pyramid gives clarity - fix what hurts most first. It aligns design work with both user impact and business value, turning chaos into focus.
Written by
Björn Rutholm
Founder of PixelPappa
Technical cofounder for hire. Product designer and developer helping teams build digital products that work.
There are hundreds of different ways of performing user testing. In this article I focus on the most fundamental testing methods and do my best to explain how it works and why these are a great place to start.
You don't need months to find out if your idea works. Here's a step-by-step breakdown of the 5-day design sprint, and how it can save you from building the wrong thing.
Fonts are one of the foundations of an accessible reading experience. Here are seven things to look for when choosing a typeface, and a checklist to keep on your desk.
Insights, case studies, and updates from PixelPappa.
