As a UX designer, I always heard that research is the cornerstone of great design. And while I still strongly believe that understanding user needs is important, there’s a fine line between research that informs good design and research that slows everything down.
In a lot of cases, the better approach isn’t months of interviews, surveys, and analysis, it’s spotting a real problem, building a Minimum Viable Product (MVP) fast, and refining it based on actual user feedback.
This isn't about skipping research altogether, it's about finding the right balance between learning and doing.
The Case for Rapid MVPs
Traditional UX processes love a good research phase. Dig deep, uncover insights, analyse behaviors, and then, usually after weeks, start building.
Sounds smart, right? Except in fast-moving markets, that long research phase can lead to:
❌ Missed opportunities (while we’re analysing, someone else is launching)
❌ Overcomplicated solutions (because we try to address every possible need)
❌ Delayed progress (perfect wireframes mean nothing if the product never ships)
Instead, by focusing on a clear problem and quickly building an MVP, teams can:
1. Test assumptions quickly
A functional product in the wild will always give you better data than a carefully crafted survey. At the end of the day, who is more likely to be honest: someone paid to give an interview or a user who genuinely engages with the product? Launching an MVP lets teams validate ideas in real-world conditions, ensuring the solution actually resonates with users.
2. Iterate efficiently
Instead of trying to design the "perfect" solution upfront, an MVP lets you launch something good, get feedback, and make it great, all while staying ahead of competitors.
Real-World Success Stories: The Power of Shipping Fast
Tony Dinh: Shipping first, refining later
Tony Dinh, an indie hacker, is proof that rapid MVPs work. He’s built multiple successful products, including Black Magic, DevUtils, and Xnapper that now generate $15K–$20K in monthly revenue.
His method?
✅ Solve a real problem (usually one he has himself)
✅ Build and launch a functional product fast
✅ Collect user feedback and improve based on real needs
No overthinking. No endless planning. Just build, launch, refine, repeat.
If Tony had waited for extensive research before launching, his products might still be stuck in a backlog. Instead, he’s iterating live, learning from actual users, and growing his projects in real time.
Balancing Perfection and Progress
Striving for perfection is great until it becomes a blocker. In dynamic markets, speed and adaptability often matter more than pixel-perfect designs.
What UX Designers can learn from this approach:
1. Reduce time-to-market
Speed matters. The faster a product is in users’ hands, the quicker it can be refined based on real behavior (not just theoretical personas).
2. Allocate resources wisely
A polished, research-heavy product that never launches is useless. Focusing on core features first ensures time and money are spent on what actually matters.
3. Foster a culture of innovation
Encouraging rapid experimentation leads to faster learning, better ideas, and a more forward-thinking team. (And fewer meetings about whether the button should be blue or green.)
Final Thoughts: Progress > Perfection
In UX, progress beats perfection every time. While informed design decisions are crucial, they don’t always require months of exhaustive research.
By identifying real user problems, quickly developing MVPs, and iterating based on feedback, designers can:
🚀 Deliver impactful solutions faster
💡 Learn from actual user behavior (not just predictions)
🎯 Continuously refine and improve in a real-world context
So before diving into a months-long research phase, ask yourself: Do we need more data, or do we just need to start building?
Comments