Table of Contents
- The Great Design Process Shift: 2015 vs 2025
- Why Your "Messy" Process Might Be Your Greatest Advantage
- The Essential Elements of an Effective Design Process
- 1. User-Centric Decision Making
- 2. Problem Collection (The Right Way)
- 3. Research That Actually Matters
- 4. Wild Ideation Sessions
- 5. Rapid Prototyping
- 6. Launch Strategy (The Quick Version)
- 7. Real User Testing
- 8. Constant Iteration
- Common Traps To Avoid In Your Process
- 1. The Perfectionism Trap
- 2. The Documentation Obsession
- 3. The Tool Fixation
- 4. The Feedback Fortress
- 5. The Trend Trap
- Real Talk: When to Break "The Rules"
- 🔻 When you're working with tight deadlines
- 🔻 When you're in a startup environment
- 🔻 When you're creating something entirely new
- 🔻 When the traditional approach isn't yielding results
- The Bottom Line: Your Process > Perfect Process
- Taking Action: Your Next Steps
- Conclusion
- TL;DR
Do not index
Do not index
Read time: under 11 minutes
The Great Design Process Shift: 2015 vs 2025
Remember 2015?
That was the year everyone lost their minds over having the "perfect" design process. Every other article was preaching about how messy your process was and how you needed to fix it RIGHT NOW.
It's 2025, and we're calling BS on that perfectionism trap.
Why Your "Messy" Process Might Be Your Greatest Advantage
What design influencers won’t tell you: There is no such thing as a perfect design process. I'll say it louder for the people in the back:
THERE. IS. NO. PERFECT. DESIGN. PROCESS.
Why? Because:
- Every team has its own quirks
- Every project is uniquely weird
- Every context brings its own chaos
And you know what? That's perfectly fine.
Never run out of inspiration again
The world’s largest UX/UI library.
1,150 apps, 405,800 screens, and 81,700 flows.
Forget Dribbble, Behance, or Twitter.
🔥 Get inspired with Mobbin.com
The Essential Elements of an Effective Design Process
Let's break down what actually matters in your design process. No fluff, no unnecessary complications—just the meat and potatoes of good design work.
1. User-Centric Decision Making
Look, if you're designing without considering actual users, you might as well be designing a fancy paperweight.
User-centric design is like cooking for guests instead of just yourself – sure, you might love putting pineapple on pizza, but your users might think you're a monster.
So just stop designing for stakeholder egos. Start designing for real humans. Here's how:
- Talk to actual users (shocking, I know)
- Watch how they interact with similar products
- Document their pain points, not just their feature requests
Example:
Remember when Snapchat rolled out their infamous 2018 redesign?
They ignored user research and ended up with a $1.3 billion loss in market value. Even Kylie Jenner tweeted, "sooo does anyone else not open Snapchat anymore?"
Ouch 🤕
2. Problem Collection (The Right Way)
Problems are like Pokemon – you gotta catch 'em all. But unlike Pokemon, you don't need to catch them all at once.
The best designers are like detectives with ADD—always collecting clues while working on the case.
The secret sauce isn't starting with a perfect strategy; it's about being a problem magnet. Here's my approach:
- Gather problems at the beginning
- Keep collecting them as you go
- Don't wait for all problems to surface before starting
Real-world example:
Take Airbnb's evolution. They didn't solve all hosting problems at once.
They started with "people need affordable travel options" and later discovered "hosts need protection from property damage".
Each problem led to new features and policies.
3. Research That Actually Matters
.png)
Research without action is just expensive procrastination.
You need just enough research to move forward confidently, not enough to write a dissertation about button colors. So focus on:
- Finding actionable insights
- Understanding user behavior patterns
- Gathering enough data to move forward (not all the data in the universe)
Example:
When Spotify developed their Discover Weekly feature, they didn't do endless research about music discovery.
Simple, effective, done.
4. Wild Ideation Sessions
Creativity is like a friend who only shows up to parties after midnight. You can't force it, but you can create the right conditions.
Wild ideation is your design party, and you need to invite every crazy idea, even the ones wearing questionable outfits. It’s where the magic happens, so remember:
- No idea is too wild
- Quantity over quality in early stages
- Break conventional thinking patterns
Example:
Nintendo's Wii came from a wild ideation session where someone basically asked, "What if we make people look ridiculous while playing video games?"
Everyone probably laughed, but it sold 101.63 million units.
The lesson? Embrace the ridiculous.
5. Rapid Prototyping
.png)
Your perfect Figma file won't answer the question "Will this actually work?"
Prototypes are like dating—you need to meet a few duds before finding 'the one'. And just like dating, don't spend too much time trying to make each one perfect.
So stop polishing that Figma file and start building something real:
- Create quick, dirty prototypes
- Test core functionality
- Don't worry about pixel perfection
Example:
The first prototype of Twitter (X now) was called "Twttr" and didn't even have vowels in its name.
It was ugly, basic, and perfect for testing the core concept.
They didn't worry about the perfect shade of blue—they worried about whether people would actually want to share 140-character thoughts.
6. Launch Strategy (The Quick Version)
Launch dates are like gym memberships—everyone has one, but most people never use them.
A launch strategy isn't about having the perfect plan; it's about having the guts to put your work out there before you think it's ready.
The best products are the ones that actually see the light of day. Here's how to get there:
- Set a realistic launch date
- Identify MVP features
- Stick to your deadline
Example:
They basically said, "Hey, this isn't perfect, but it works better than Hotmail, so... want to try it?"
And guess what? People loved it because it solved their problems, even with the 'beta' label.
7. Real User Testing
.png)
Your mom, your best friend, and your cat are not your target users (unless you're designing a cat food app, then maybe the cat stays).
Real user testing is like stand-up comedy—you don't know if your jokes work until you try them on a real audience. You need:
- Actual target users
- Real-world scenarios
- Unfiltered feedback
Example:
Remember when Microsoft Bob tried to make computers "friendly" without proper user testing? It failed so spectacularly that it's now a case study in what not to do.
Even Clippy, its spiritual successor, became more annoying than helpful because they didn't test with real users who were trying to get actual work done.
*Fun fact, there’s a research book called The Mom Test.
8. Constant Iteration
.png)
First versions are like first pancakes—they're never the best ones.
Iteration isn't about admitting failure; it's about admitting that you're not psychic and can't predict exactly what users want. Here’s how you do it right:
- Monitor user behavior
- Collect feedback actively
- Make quick improvements
Example:
Instagram started as Burbn, a check-in app with photo features.
Through iteration and user feedback, they realized people only cared about the photo sharing. They cut everything else, and well... you know the rest of the billion-dollar story.
Common Traps To Avoid In Your Process
Let's talk about the common pitfalls that keep designers in analysis paralysis:
1. The Perfectionism Trap
Stop trying to create the perfect strategy before you start. It's like trying to plan every conversation you'll have for the next year—impossible and unnecessary.
Root cause: You're treating every design decision like it's going to be carved in stone and displayed in the Museum of Modern Art. News flash: it's going to be updated in three months anyway.
How to overcome it:
- Use the "good enough for now" rule.
- Set hard deadlines for each design phase.
- Create a "perfectionism budget"—choose what actually needs to be perfect.
- Remember that Facebook's first design looked like a college project (because it was).
2. The Documentation Obsession
Yes, documentation is important. No, you don't need to document every single thought that crosses your mind during the design process.
Root cause: You think if you document everything perfectly, nothing can go wrong. Spoiler alert: things will still go wrong, but now you'll have more documents to update.
How to overcome it:
- Document only what brings value to the team.
- Ask yourself: "Will anyone actually read this?".
- Create living documents that are easy to update.
- Use screenshots and quick videos instead of writing novels.
3. The Tool Fixation
Figma vs Adobe XD vs Sketch – who cares? Pick one and get to work. Your tools don't define your success.
Root cause: You believe that if you just find the perfect tool, all your design problems will magically disappear. It's like thinking a new pan will make you a better cook.
How to overcome it:
- Pick one main tool and stick with it for at least 3 months.
- Spend more time thinking about users than toolbar options.
- Focus on mastering the basics before exploring advanced features.
- Remember that Dieter Rams designed with paper and pencil.
4. The Feedback Fortress
Stop trying to please everyone before shipping anything. Your design isn't a UN resolution—it doesn't need unanimous approval.
Root cause: Fear of criticism has you building an impenetrable wall of stakeholder approvals before showing anything to real users.
How to overcome it:
- Start with rough sketches shared early.
- Create a "feedback funnel"—users first, stakeholders second.
- Remember: Feedback is like vegetables—sometimes it tastes bad but it's good for you.
5. The Trend Trap
Chasing every design trend is like following every TikTok dance – exhausting and ultimately pointless. Focus on what works for your users instead.
Root cause: You're so busy chasing the latest design trends that you forget about solving actual problems.
How to overcome it:
- Ask yourself: "Does this trendy glassmorphism actually help users?".
- Test new trends with real users before implementing.
- Remember: MySpace was once trendy too. Think about that.
Real Talk: When to Break "The Rules"
Here's when you should throw the traditional design process out the window:
🔻 When you're working with tight deadlines
Why: Because perfect is the enemy of launched, and launched is the enemy of unemployment.
Instead, focus on:
- Quick wins that can be implemented fast.
- Core user flows that directly impact business goals.
- Documentation that actually helps development (not your design ego).
🔻 When you're in a startup environment
Why: Startups need speed and flexibility more than they need perfect process documentation.
Instead, focus on:
- Rapid prototyping and testing.
- Features that drive user acquisition.
- Solutions that scale with limited resources.
- Quick iterations based on real user feedback.
🔻 When you're creating something entirely new
Why: Innovation doesn't come from following the same old playbook.
Instead, focus on:
- Learning from failures fast.
- Quick experiments to validate assumptions.
- User problems rather than existing solutions.
- Building a process that fits your unique challenge.
🔻 When the traditional approach isn't yielding results
Why: If you keep doing what you've always done, you'll keep getting what you've always got.
Instead, focus on:
- Experimenting with different methodologies.
- Finding what works for your specific context.
- Identifying what's actually blocking progress.
- Measuring impact rather than process adherence.
The Bottom Line: Your Process > Perfect Process
Remember these key points:
- Most of us aren't designing life-support systems.
- Perfect is the enemy of done.
- Users care about solutions, not your process.
- The best process is the one that ships.
Taking Action: Your Next Steps
- Review your current process.
- Identify where you're getting stuck.
- Cut out unnecessary steps.
- Start shipping faster.
- Iterate based on real feedback.
The real question isn't whether your process is perfect—it's whether it's getting results. If you're shipping products that users love, you're doing it right, messy process and all.
Conclusion
Stop obsessing over the perfect process and start obsessing over getting real products into real users' hands. Your "messy" process might just be the perfect approach for your specific situation.
Remember: The best design process is the one that works for you and your team. Everything else is just noise.
TL;DR
- Your "messy" design process might actually be perfect for your needs.
- Focus on these essentials: users, problems, research, ideation, prototypes, launching, testing, and iteration.
- Stop obsessing over perfection and start shipping.
- Break the "rules" when they don't serve your project.
- The best design process is the one that gets results, not the one that looks good on paper.
Thank you Mobbin for sponsoring. Try it today and sign up for free
Whenever you're ready, there are 4 ways I can help you:
1. Junior Designer Bundle: Transition into UX and craft an unforgettable portfolio & get hired.
2. Senior Designer Bundle: Become a design leader with systems to build healthier, happier teams.
3. UX Portfolio Critique: In less than 48 hours, get your 30-minute personalised video of brutally honest feedback.
4. Job Sprint Course: Stand out in an unpredictable job market by building a memorable personal brand and a killer job search strategy.
