UX Designers: Stop Presenting Screens. Start Presenting Outcomes.
If you're a UX designer who's been presenting work to stakeholders and getting polite nods but no real engagement or buy-in, I know why.
You're presenting screens.
I know, because I did it for years. I'd spend a week designing a new onboarding flow. I'd build a careful deck showing the before state, the research insights, the design decisions, the after state. I'd walk through each screen. I'd explain the rationale. Stakeholders would nod. They'd say things like "looks good" or "I like the colors." The meeting would end with a vague commitment to "move forward."
And then nothing would happen. Or something would happen, but the final design wouldn't resemble what I presented. Or the work would ship and immediately feel somehow beside the point.
The problem wasn't the design. The problem was the presentation.
Screens Are a Means. Outcomes Are the Point.
Stakeholders — product managers, executives, commercial leads — don't actually care about screens. They care about outcomes. Growth. Retention. Revenue. Efficiency. The screens are a means to those outcomes. But when you present screens as the primary object of discussion, you're asking stakeholders to make a mental leap from what they're seeing to why it matters.
Most of them won't make that leap. Not because they're bad at their jobs. But because that leap is your job, not theirs.
What an Outcomes-First Presentation Looks Like
Here's a structure that works.
Start with the metric. "This work is about our activation rate. Right now, 34% of new users complete their first meaningful action within 7 days. Our target is 55%. The gap costs us approximately $18,000 in monthly recurring revenue through increased churn."
You've now told the room exactly what's at stake. Everyone in the meeting is immediately oriented. They know what success looks like before you've shown a single screen.
Explain the root cause. "Through user research and session recording analysis, we identified three specific moments where users abandon the flow: [moment A], [moment B], and [moment C]. Each of these has a specific cause."
Now you're doing diagnosis, not just showing work. The stakeholders can evaluate whether your diagnosis is right. This is where they engage.
Show the design as a solution, not a presentation. "Here's how we're addressing moment A..." Then show the screen. But show it as a response to a specific problem, not as an artifact to be admired.
The design review becomes a discussion about problem-solution fit, not about aesthetic preferences. And problem-solution fit is a conversation where designers have much more standing.
Close with the expected impact. "If our diagnosis is correct and this design change reduces friction at these three moments, we project activation to improve by 15–25%. That's $8,000–$14,000 in monthly revenue impact."
You're not promising a number. You're projecting based on reasoning. But putting a number on it is what makes the work feel real to the business. It's also what gets budget approved and decisions made.
The Objection You'll Get
"But I don't have access to those numbers. I don't know our activation rate."
Find them. Ask your PM. Ask your data team. Ask your head of product or growth. The act of asking these questions — and showing that you're oriented to business outcomes — is itself a career accelerator. People notice when a designer asks "what metric is this work supposed to move?" instead of waiting to be briefed.
If the numbers genuinely don't exist, you can still use approximate reasoning. "Our conversion rate from trial to paid is lower than industry benchmarks for similar products. This work is aimed at the activation drop-off that's driving that gap."
It's less precise. But it's still an outcomes frame. It still tells the room that you're thinking about the business, not just the screens.
This Is Also How You Get Promoted
The difference between a designer who executes and a designer who leads is, in large part, this shift. Executors present work and ask for feedback. Leaders present problems and their solutions, with a view to outcomes and impact.
It's not about title or experience. I've seen senior designers who still present like executors, and mid-level designers who already present like leaders. The difference is mindset and habit.
Start with your next presentation. Before you open the deck, write one sentence that answers: what metric is this work supposed to move, and by how much?
If you can't answer it, find it before the meeting. That process alone will make you a better designer and a more effective collaborator.
If you can answer it, put it on your first slide. Lead with it. Build everything that follows around it.
That's not just how you present design. It's how you lead with it.
Moving from screen-presenter to strategic designer is exactly what UX coaching focuses on. See how it works →