There is no "design process"

Why a flexible, strategic approach matters—and what happens when we default to a one-size-fits-all process.

Hey, Miranda here 👋

Whether you’re jumping straight into UI when you should be starting with discovery research or you’re doing a full process parade when you could be doing rapid iteration.

Let’s talk about why a flexible, strategic approach matters—and what happens when we default to a one-size-fits-all process.

The Problem With Process for Process' Sake

Most design teams have some kind of process—which is good! But the problem comes when that process becomes the default for every project, regardless of scope or impact.

The result?

• Timelines bloat with unnecessary steps

• Designers burn time (and stakeholder patience)

• Design loses credibility as being "slow" or "too precious"

Instead, the best designers know how to match the approach to the project.

Let’s break this down by looking at a few common project types and how your process should flex accordingly.

---

Micro Optimizations (e.g., Improving a CTA or Fixing a Drop-Off Point)

🛠 What it needs: Speed, clarity, small-scale validation
🧠 Common pitfall: Over-researching or over-documenting
✅ Smart approach: Jump into the known data, make a quick mock-up, run a lightweight usability test or experiment. Get it out the door fast.

Example: If 60% of users are dropping off after clicking “Next,” we probably don’t need a full design sprint—we need a better “Next” interaction.