Why Your Design Reviews Feel Off and How to Fix Them

Hey UI Collective,

This isn’t a newsletter about flashy UI trends or whatever Figma feature dropped this week. I want to talk about something that matters more than most people realize: how you present your work.

But before that, a quick note for those following along with UI Collective Academy.

🎁 Stakeholder Management Course Now Available

We just launched a brand new course inside the Academy focused on stakeholder management; how to handle difficult feedback, present with clarity, and get alignment across product, engineering, and leadership. Now included in the All Access Pass.

The response has been incredible and so many of you reached out asking for more time to join at the early price.

So we’re reopening founding member pricing through June 14th. Additional courses are on their way including our Design Leadership Course, Getting Hired in Design, and much more!

Now let’s talk about how most design presentations miss the mark — and how to fix them.

Why Most Design Presentations Fall Flat

It’s not because the work isn’t good. It’s because the setup doesn’t give people enough to react to.

If you walk into a review and say something like:

“Here’s the old version. Here’s the new one. What do you think?”

You’re inviting feedback with no direction. And when people don’t have direction, they give you whatever comes to mind — color tweaks, alignment nudges, surface-level stuff.

That’s not feedback. That’s guessing.

The Missing Piece: Framing

The best feedback happens when people understand the problem you’re trying to solve, not just what you pushed around in Figma.

Start there.

Tell them why this work even exists. Was it a drop in conversion? A support complaint? A broken onboarding flow? Ground the conversation in something real.

You’re not showing options. You’re walking the room through a story.
Good design is context-driven — your presentation should be too.

Talk Constraints Before You Talk Solutions

Here’s where you build trust.

Don’t pretend you had unlimited time and freedom. Tell them what you were working around. Time. Tech. Legal. Team capacity.

This doesn’t make your work look weaker. It shows maturity. It prevents unhelpful feedback like “why didn’t you redesign the whole flow” when that was never on the table.

Be upfront. It shifts the tone of the entire conversation.

Make the Thinking Visible

Don’t assume people can see your decisions just by looking at the screen.

Explain what changed and why. Not a laundry list of tweaks. Just the key moves and your reasoning.

“We merged the review and confirmation steps to reduce friction, and removed two optional fields that weren’t being used.”

That one sentence is better than ten slides of "before and after."

What Happened After You Built It?

If you tested it, say what you learned. If you haven’t yet, explain what you expect and how you’ll know it worked.

Even rough feedback helps.

“In moderated testing, users completed the flow with fewer questions. Early signals show a drop in abandonment.”

This is the part that makes the difference between a design and a decision. When you bring data, even light data, you earn confidence.

Say What You Need

This is the part most people skip.

Don’t just end with “thoughts?” Say what the next step is.

“Are we aligned on this direction?”
“Do we feel confident handing this to dev?”
“Is there anything we need to test before this moves forward?”

That’s the ask. That’s the reason you’re presenting. Don’t bury it.

Don’t Memorize a Format. Learn the Rhythm.

There’s no one perfect way to present work, but here’s the rhythm I keep coming back to:

• Why this work exists

• What shaped the solution

• What changed and why

• What happened (or what we expect)

• What we need next

This isn’t a template. It’s just how strong design stories are told. Give people the right story, and they’ll give you the right support.

➡️ What Should We Add Next?

What content do you actually want to see?

More interview prep? Real-world case studies? Pricing your freelance work? Deep dives into Figma workflows?

Let me know what you'd find most helpful — whether it's for UI Collective Academy, the YouTube channel, or anything else we're building.

Just reply to this email. No form, no filter. Your input helps shape what we launch next.

Thanks for all your support, everyone. Two years ago I couldn’t have imagined how successful UI Collective was to become.

Kirk