How to present design work to executives

Most design presentations to executives are optimized for the wrong audience. They're built to demonstrate how much thought went into the work. That's not what the room is evaluating.

Executives are evaluating whether the decision behind the design was sound. They want to know what problem you were solving, what constraints shaped your options, what you considered and eliminated, and why you landed where you did. The design itself is evidence for or against that reasoning. It's not the presentation.

What they're actually checking

Someone senior in a room is pattern-matching against decisions they've seen succeed and fail. They're asking: is this person making decisions I'd trust? Did they get the problem right?

"Here's what we designed" doesn't answer those questions. "Here's the problem, here's why the obvious solution wouldn't work, here's what we built and why" does.

The most common design presentation mistake is skipping straight to the solution. By the time you show the design, the executive should already agree with the problem definition. If they don't, the design review turns into a problem definition debate with everyone looking at a half-formed solution.

Structure that works

State the problem in one sentence, then the constraint that made it hard. If you can't do that, the problem isn't clear enough yet.

Show what you didn't do, briefly. A quick pass on the alternatives you evaluated and ruled out. This signals that the work was considered, not that you built the first thing that came to mind. It also gives the executive a chance to surface a direction they think you missed before you're deep into defending the one you built.

Then show what you built, organized around the decisions rather than the screens. "This is the navigation structure, and here's why it's not a sidebar" is more defensible than "here's the navigation."

Close with what's unknown. What are you not sure about? What would change your mind? Executives respect disclosed uncertainty more than uncertainty discovered in Q&A.

On feedback

Feedback from executives tends to be directional, not specific. "This feels too complex" is a reaction. "I'm worried this will confuse new users" is a hypothesis about a specific concern.

When you get directional feedback, your job is to figure out what specific worry is underneath it before doing anything. "What would help me understand that better? Is it the number of steps, the terminology, something about the order?" is a better response than "we can simplify that." Simplifying without knowing what the concern actually is produces a design that satisfies the feedback aesthetically without addressing the underlying issue.

The meeting is over when you leave with a clear answer to whether you can move forward, not when you've gotten agreement that the screens look good.