They Asked for a Quick Design Audit

The metrics weren’t terrible, just comfortably mediocre. A few users had called the app "confusing." One even described it as "polite but lost." I’m still deciding whether that was poetic or damning.

Anyway, they reached out. Said they needed a quick design audit. Just a light skim of the Figma file. Maybe a new shade of blue. Nothing major. Nothing philosophical.

What They Expected:

• A short PDF

• Bullet points with words like "streamline" and "spacing"

• A calm sense that design had been "looked at"

What They Got:

• Questions about user journeys they hadn’t really mapped

• Comments like "What’s the goal of this screen?" followed by silence

• A Loom video gently pulling apart the sign-up flow in five minutes flat

• The phrase "misleading interaction pattern" (their words, not mine, but yes, it did sting)

At some point, someone on their team whispered, "Are we the bad interface?"

Things the Audit Uncovered:

• Onboarding was four screens of features no one cared about

• The main CTA was buried, apparently by decree from an old marketing OKR

• The design system was more myth than system

• Every dropdown was styled differently (they called it "playful")

In the end, it wasn’t a bad product (just not modular yet). Just one of those quietly confused ones, drifting along with no strong opinions and too many inherited decisions.

Did the Audit Fix Everything?

Not exactly. It just revealed where things were broken.

Which, if you’re doing your job properly, is the real point. Audits aren’t makeovers. They’re mirrors.

They help teams name the fog. Give designers cover to ask better questions. Turn vague dissatisfaction into design intent.

Would I Do It Again?

Every time.

Though I might stop calling it "quick."

What they asked for was a tidy little review. What they got was the start of a better product.