If you scroll through design Twitter or browse top-tier portfolios on Behance, you will inevitably see The Process™.
You know the one. It’s usually a clean, linear diagram—often a “Double Diamond”—that moves perfectly from Empathize to Define, then Ideate to Prototype, and finally to Test. It looks scientific. It looks safe. It looks like a guarantee that if you just follow the steps, brilliance will emerge at the other end.
But if you work in the real world, you know a secret: Creation rarely happens in a straight line.
We often feel guilty when our actual workflow doesn’t look like the diagrams in the textbooks. We worry that we are “hacking it” or being unprofessional because we skipped a step or jumped straight into high-fidelity pixels.
It is time to let go of that guilt. The truth is, the “perfect” process is a myth. The only process that matters is the one that gets you to the right outcome.
The Map is Not the Territory
Frameworks like Design Thinking or Agile are incredibly useful tools. They provide a common language for teams and a safety net for complex problems. But they are maps, not the territory itself.
When you are deep in a project, the terrain changes. Deadlines shrink. Tech stacks limit possibilities. Clients change their minds. In these moments, rigidly sticking to a pre-defined process isn’t discipline; it’s obstruction.
Sometimes, you don’t need a three-week discovery phase; you need to prototype something broken in 20 minutes to see if the idea even holds water. Sometimes, you don’t need wireframes; you need to jump straight into code or the final UI to understand the interactions.
Permission to Be Messy
The most seasoned professionals don’t follow a script; they follow their intuition, honed by experience.
-
If you think by writing: Start with a Google Doc, not a sketchpad.
-
If you think visually: Go straight to high-fidelity mockups to test the vibe, then work backward to the UX.
-
If you think in code: Build a messy prototype in HTML/CSS (or Flutter/React) to see how it feels in the hand.
The “messy middle” of a project is where the magic happens. It’s the chaotic loop of trial and error that doesn’t look good on a slide deck but is essential for innovation. If your process involves pacing around the room, sketching on receipts, or staring at a blank screen for two hours before a burst of clarity—that is a valid process.
The Outcome is the Only Metric
Your users do not care about your Miro board. They do not care how many sticky notes you used during brainstorming. They care about one thing: Does the final product solve their problem?
If you spent six weeks on a “perfect” design process but delivered a confusing product, the process failed. Conversely, if you skipped three steps but delivered a solution that delights users and meets business goals, your process was a success.
We need to stop fetishizing the performance of design and start valuing the impact of design.
Finding Your Own Flow
“Whatever gets you to the outcome” is not an excuse for laziness or skipping due diligence. It is a call to self-awareness.
To follow your own process, you must know yourself:
-
Know your blind spots: If you naturally skip user research, force yourself to do a sanity check, even if it’s informal.
-
Know your tools: Master your tools so they don’t slow you down when inspiration strikes.
-
Know your team: Your process needs to interface with others. As long as you can communicate your vision clearly to developers and stakeholders, how you arrived at that vision is your business.
Conclusion
Stop trying to force your square peg of creativity into the round hole of a textbook methodology. The world needs your unique perspective, and it needs the solutions only you can build.
So, sketch on the napkin. Jump straight to code. Do the “wrong” thing first to see why it fails. Trust your gut.
If it works, it wasn’t the wrong way. It was your way.
