"The Process" vs. The Real World
"The Process" vs. The Real World
What textbooks teach vs. what actually happens
Every designer learns a “perfect” process:
Research → Define → Ideate → Wireframe → Prototype → Test → Iterate → Deliver.
It’s neat, logical and predictable.
It’s also almost never how things go in real life.
After years of working across teams, clients and products, I’ve realized that design rarely follows the ideal flow. Time, budget, changing requirements and human chaos always intervene. Our job isn’t to protect the process; it’s to adapt it intelligently without losing clarity or our sanity.
A senior designer’s value isn’t just in knowing how to design; it’s in knowing how to adapt when things aren’t ideal.
The Process (in theory)
We've all seen the perfect product design framework before, or some variation of it.
There’s no need to rehash the step-by-step version here; you can find countless diagrams of it online.
What matters more is understanding how it actually behaves in real projects: almost never linear, always looping back, sometimes compressed into a week.
In my work, I start from the basic foundation but adjust based on:
- Project size and timeline
- How much user data we actually have
- Team composition
- And how clear or mature the product vision is
For example:
- If there’s no research budget, I make assumptions and validate through quick prototyping
- If there’s no real feedback from the existing product, I start by analyzing it myself; reviewing flows, identifying friction points and looking for inconsistencies or missed opportunities before deciding what actually needs to change.
- If requirements change mid-sprint, I shift from deliverables to alignment conversations
Lessons From the Real World
Even with experience, these situations still happen; not because of poor planning but because every project has its own mix of constraints, people and moving targets. What matters is how you respond. Over the years I’ve learned where flexibility helps and where skipping steps comes back to bite later. Here are a few examples that shaped how I approach process today:
1. Skipping Wireframes
We once jumped straight into high-fidelity screens because we already had a half-built design system.
The problem? The flows weren’t clear yet. We iterated endlessly, wasting time changing full-color mockups when what we actually needed were quick wireframes to clarify structure and logic first.
Lesson: Wireframes aren’t optional, they’re the cheapest way to figure out what you’re even building.
2. Designing Without Understanding the Problem
On one project, we started redesigning an app UI without a clear grasp of what the client actually needed. Communication was fragmented and assumptions filled the gaps. We ended up with polished visuals, for the wrong goals.
Lesson: Design direction should come from clarity, not assumptions. Good communication is a design skill.
3. Designing Before Copy
I’ve worked on many teams where design starts before content. It’s never made sense to me. Copy shapes tone, structure and even layout. Great words can spark visual ideas you’d never have otherwise.
Lesson: Design and copy should evolve together. Collaboration creates alignment and stronger storytelling.
4. The “Just Add a Button” Trap
A stakeholder says, “Can we just add a small button to do X here?”
But that button opens a whole chain reaction. It needs an undo state, error handling, confirmation, new screens and logic. Suddenly that “small” change touches multiple flows.
Lesson: Experience teaches you to see the ripple effect early, and to know when to push back or reframe the request before it grows uncontrolled.
5. Too Many Stakeholders, Too Many Opinions
Sometimes projects derail not because of design problems, but because of people problems. Too many voices, conflicting directions, unclear ownership.
Lesson: Clear leadership, facilitation and communication can save weeks of chaos.
6. Clients Who Don’t “Speak Design”
Not every client understands the why behind design decisions, and that’s okay. It’s our job to bridge that gap.
Lesson: Presentation skills, empathy and clear communication are as essential as color theory. How you explain design often matters as much as the design itself.
Experience = Adaptability
These aren’t horror stories, they’re reminders that design happens in the real world, where constraints, people and priorities constantly shift.
Experience isn’t about following the perfect process, it’s about recognizing when to bend it and how to guide others through the ambiguity.
That’s the difference between “knowing design” and leading it.