One tiny button move = $300 million revenue gain. How? Amazon actually watched users struggle before optimizing.
Take the case of a company with a surprisingly effective approach to the UX design process. They simply changed a button from “Register” to “Continue” (and made registration optional). That tiny change—just one word—resulted in a staggering $300 million sales increase the following year.
Why such a dramatic result? This company talked to their end users first and discovered people weren’t abandoning carts because the design wasn’t pretty enough—they just hated being forced to create accounts to buy a damn blender.
This isn’t fiction. The “$300 million button” is a famous case study from UX researcher Jared Spool. I’ve witnessed similar scenarios firsthand, watching design teams create solutions based on assumptions rather than user needs.
A thoughtful design process isn’t just extra paperwork. It’s what separates designs that look good in presentations from ones that actually work for real people. Think of it as choosing between a flashy sports car that breaks down constantly or a reliable vehicle that gets you where you need to go every time.
Let’s explore what a genuine user-centered design process looks like without all the jargon and buzzwords. When done right, it’s not a rigid set of rules but a helpful guide that keeps you focused on what truly matters.
Most discussions about the UX design process feel like reading an IKEA manual written by a corporate lawyer. They’re either painfully academic (“leverage user-centric methodological frameworks to ideate iterative solutions”) or suspiciously simplistic (“just design what feels right!”).
No wonder so many designers roll their eyes when “process” comes up. The word itself has been beaten to death in countless Medium articles and agency pitch decks.
Here’s the uncomfortable truth: process matters, but not in the way most people think.
The best design teams don’t worship the process; they respect it. They understand that process exists to prevent obvious mistakes and create space for actual creativity—not to turn designers into robots following flowcharts.
And they recognize the irony that sometimes the most creative solutions come from working within constraints rather than having unlimited freedom. As designer Charles Eames famously said: “Design depends largely on constraints.”
So rather than debating whether the process is good or bad, let’s focus on what moves the needle. What parts of the UX design process consistently lead to better outcomes, and which parts are just ritualistic busy work?
Let’s get into what actually matters.
Let’s get brutally honest about the basics of UX design process. Not every project needs the full five-course meal treatment. Sometimes you need the whole enchilada; other times you just need the salsa.
What’s essential: Understanding what keeps your users up at night. Whether it’s through formal user interviews or guerrilla research in a coffee shop, you need to know what problem you’re solving.
I once watched a team spend six months building an elaborate analytics dashboard that literally nobody used. Why? They skipped research and built something that answered questions nobody was asking. That’s like crafting the world’s most beautiful hammer when your users needed a screwdriver.
What you can skip: The 80-page research report nobody will read. Distill your findings into actionable insights that will inform decisions. Your team needs ammunition for better design, not a doctoral thesis.
What’s essential: Alignment on success metrics. If you can’t articulate how you’ll know if your solution worked, you might as well be designing in a parallel universe. Both user needs and business goals need a clear definition.
What you can skip: Elaborate personas that state the obvious. “Meet Dave, 34, who wants a website that loads quickly and doesn’t crash.” Groundbreaking insight there, team. Focus on unexpected motivations and pain points, not demographic fluff.
What’s essential: Creating clear user flows that map how people will actually accomplish their goals. This is where you translate research into structure.
What you can skip: Pixel-perfect wireframes for every single screen. The fidelity of your deliverables should match the complexity and risk of your project. For a simple landing page? Rough sketches might be enough to communicate the concept.
What’s essential: Creating something testable before you commit resources to build it. This doesn’t always mean fancy interactive prototypes—sometimes paper prototypes work just fine.
What you can skip: Building every feature into your prototype. Focus on the riskiest assumptions—the parts most likely to fail or cause confusion. That’s where valuable learning happens.
What’s essential: Putting your ideas in front of actual end users before you commit. Your brain is not representative of your user base, no matter how empathetic you think you are.
I’ll never forget watching a user trying to complete a “simple” task on an interface we’d designed. After five minutes of frustration, they looked up and asked, “Am I just stupid?” That wasn’t a user failure—that was a design failure we would have missed without testing.
What you can skip: Perfect testing conditions. Don’t wait for the ideal lab setup or the perfect participant recruitment. Imperfect testing beats perfect planning every time.
What’s essential: Building in time to learn and refine based on real usage. Version 1.0 of anything is just your best-educated guess.
What you can skip: Starting from scratch with each iteration. Good iteration is surgical—identify specific problems and fix them, don’t redesign the entire experience because one part isn’t working.
Follow-up research after launch – The most valuable insights often come when people actually use your product, yet this is precisely when most teams have already moved on to the next shiny project. Building in time to learn from what you shipped is perhaps the highest ROI activity in the entire design process.
Remember: the process should be your servant, not your master. The best designers know when to follow the recipe precisely and when to throw out the cookbook based on what their specific project needs.
As my first design mentor used to say: “Know the rules well enough to break them effectively.” That’s the difference between someone who does UX and someone who gets UX.
Here’s the thing about user-centered design: it’s not a phase—it’s a mindset that transforms every stage of your process. It’s the difference between designing a car based on what looks cool in your sketchbook versus designing one based on actual humans with spines, arms, and an inexplicable desire to eat burritos while driving.
When companies fail at user-centricity, it’s rarely because they don’t know they should talk to users. It’s because they:
I once watched a product team spend weeks debating button colors while completely missing that users couldn’t figure out how to start the core workflow. The team was so focused on the paint job, they forgot to check if the steering wheel was attached.
Research: User-centered research means investigating actual problems, not just confirming your assumptions. It means asking “What keeps you up at night?” before asking “Would you use this?”
Analysis: A user-centered analysis cuts through corporate priorities to focus on what matters to humans. It means ruthlessly prioritizing based on user impact, not just technical feasibility or business desire.
Design: User-centered design means creating user flows that reflect how people think and work—not how you wish they would behave. It means designing for the messy reality of human behavior, not some idealized robot user.
Prototyping: User-centered prototyping means creating something people can react to honestly. It means embracing rough edges that encourage genuine feedback, not polished mockups that only invite compliments.
Testing: Truly user-centered testing means observing what people do, not just listening to what they say. It means creating scenarios that reflect real contexts, not sterile lab tasks.
Iteration: User-centered iteration means evolving based on actual usage patterns, not just stakeholder opinions. It means having the courage to recognize when your brilliant idea just isn’t working for real humans.
The companies that nail user-centricity don’t just do occasional usability studies; they build ongoing relationships with their end users. They don’t treat user research as an event—they treat it as oxygen.
Take Intuit’s “Follow Me Home” program, where designers literally visit customers to watch them use the product in their natural environment. Or Slack’s practice of bringing in users weekly to test new features before they ship. These aren’t just nice-to-have practices—they’re competitive advantages.
As Bradee Evans, Principal UX Designer at Adobe, said:
“…the single most impactful and time-saving thing we could do was to stop designing for our users…”
This isn’t just altruism—it’s good business. Companies that incorporate user feedback throughout their process are 38% more likely to report revenue growth and 32% more likely to gain market share over competitors, according to a Forrester study.
Of course, being user-centered doesn’t mean taking every user request at face value (hello, “make the logo bigger” syndrome). It means understanding the underlying needs behind those requests. And sometimes what they need is to not be annoyed by your brilliant, unnecessary “innovations.”
Now that’s user-friendly.
Let’s address the elephant in the design room: business goals sometimes clash with what users want. Users typically want everything free, infinitely flexible, lightning-fast, and ad-free. Meanwhile, businesses need revenue, engagement metrics, and sustainable growth paths.
The mediocre designer sees this as an either/or situation: “Do we please the users or the stakeholders?” They end up playing a sad game of tug-of-war where nobody wins and everybody gets muddy.
The exceptional designer finds the sweet spots where business success and user satisfaction align like perfectly matched puzzle pieces:
Enterprise products:
Consumer apps:
E-commerce:
Startups:
Here’s my battle-tested approach for aligning user needs with business goals:
If your solution makes users happy but bankrupts the company, you’ve solved the wrong problem. And if it makes the company rich but users hate it, you’ve just created an opportunity for your competitors.
The best products aren’t compromises—they’re win-wins that leave users thinking “this company gets me” while stakeholders watch the graphs go up and to the right. That’s the art of user-centered design that actually ships and survives.
Remember: Users don’t care about your business goals, but you can’t serve users if your business fails. The magic happens when you find ways to achieve both in the same elegant solution.
Sometimes the best process is throwing out the process. Not because the process is bad, but because creativity occasionally needs to jump the tracks to find brilliance.
Some warning signs your UX design process needs a shake-up:
Great design teams view the process as a tool, not a religion. They’re not afraid to:
Good designers follow best practices. Great designers know when to break them.
The key is understanding why each step exists before you skip it. Breaking rules without understanding them isn’t rebellious—it’s just uninformed.
How do you know if you’ve created something truly user-friendly? Hint: it’s not about how pretty it looks or even how many people initially use it.
The metrics that matter include:
Gorgeous products fail because they never bothered to measure what happened after launch. They celebrated the launch party, high-fived over the initial downloads, and then scratched their heads when users disappeared faster than free donuts in a design agency.
Your product isn’t successful when it ships—it’s successful when it becomes a natural part of your users’ lives. Nobody opens Instagram to admire its interface. They open it to see photos of their friends’ dogs. If they’re noticing design, you’ve probably failed.
The UX design process should be a compass that keeps you oriented toward true north, not a cage that restricts movement. The best designers aren’t those who rigidly follow every step, but those who understand the purpose behind each phase and adapt accordingly.
Remember:
Next time someone asks you about your design process, resist the urge to recite the standard UX playbook. Instead, tell them: “It depends on the problem we’re solving, the people we’re solving it for, and the constraints we’re working within.” Because in the end, that’s the only design process that consistently delivers the best possible user experience and results.
Robots doing all your work sounds perfect—until they’re stuck in loops, grabbing random tweets, and…
Most emails are forgettable. Great ones hook you fast, look sharp, and drive clicks. Here’s…
We put top AI face swappers to the test—beards, glasses, head tilts, and more. Some…
A deep dive into the smallest images in graphic design: the history of icons, their…
Learn how to use visual hierarchy to guide attention, prioritize elements, and create designs that…
WOKONEO, a puzzle book for kids that blends playful learning with creativity, featuring Icons8’s Color…
This website uses cookies.