Presenting your UX work can feel just as important as doing the work itself.
Whether you’re showing early wireframes or a full prototype, your goal is to help stakeholders understand, trust, and support your design decisions. But explaining UX to non-designers—product managers, marketers, executives—requires more than showing screens.
In this guide, you’ll learn how to present UX work effectively, tailor your message for stakeholders, and lead conversations that result in real buy-in.
1. Know Your Audience
Before crafting your presentation, ask:
- Who are the stakeholders? (e.g. execs, devs, marketing, sales)
- What do they care about? (e.g. KPIs, timeline, brand, user needs)
- How familiar are they with UX?
Tip:
Adjust your vocabulary. Use fewer design terms and more business language if presenting to executives.
2. Start with the Problem
Don’t just show what you designed—start with why you designed it.
Frame the problem:
- What user pain points did you discover?
- What business goal are you solving for?
- What research or data supports the need?
This sets context and aligns your design with real-world impact.
3. Tell a Story, Not a Feature List
Use storytelling to walk stakeholders through the user journey.
Structure:
- Before: Describe the user’s struggle or frustration
- During: Show how your design improves the experience
- After: Explain the outcome or benefit to users and business
Use empathy to make stakeholders feel the user’s experience—not just see it.
4. Show the Process, Not Just the Final Screens
Stakeholders need to see how you arrived at the solution.
Include:
- Key research findings (surveys, interviews, analytics)
- Personas or user scenarios
- Sketches, wireframes, and iterations
- Design constraints or technical considerations
This shows your thinking and builds credibility and transparency.
5. Focus on Outcomes, Not Just Aesthetics
It’s easy to get caught up in colors and fonts, but stakeholders care more about results.
Emphasize:
- Increased conversions
- Fewer support requests
- Higher task completion rates
- Better user retention
- Shorter onboarding time
Back your claims with usability test results, metrics, or before/after comparisons if available.
6. Keep It Simple and Visual
Avoid walls of text. Use:
- Slides with clean visuals
- Screenshots and mockups
- Clickable prototypes (Figma, Adobe XD)
- Short video walkthroughs (Loom)
Highlight key areas with annotations or cursor guidance.
7. Anticipate Questions and Objections
Stakeholders might ask:
- “Why did we remove this feature?”
- “Is this design responsive?”
- “How does this impact timeline or budget?”
Prepare for:
- Alternative flows
- Edge cases
- Technical constraints
- Trade-off decisions
Being proactive earns trust and keeps the meeting focused.
8. Invite Feedback (But Set Boundaries)
Make space for stakeholder input without letting the session become a free-for-all.
Try:
- “We’re open to feedback on this flow’s clarity.”
- “We’re testing this layout, but visual polish will come next.”
- “We’re following accessibility guidelines—feedback on copy tone is welcome.”
Guide the type of feedback you’re seeking, and separate personal preference from user data.
9. Use a Live Prototype or Walkthrough
Whenever possible, present a live walkthrough of the user journey.
Use tools like:
- Figma prototypes
- Loom videos
- Clickable demos
Let stakeholders experience what users will see—this builds empathy and excitement.
10. Summarize Next Steps and Ask for Buy-In
End with:
- What decision you’re seeking (e.g. approval, greenlight, user testing)
- What’s happening next (e.g. dev handoff, another test round)
- A quick recap of user and business benefits
Make it easy for stakeholders to say yes or ask smart questions.
FAQs: Presenting UX Work to Stakeholders
How long should a UX presentation be?
Aim for 15–30 minutes of presentation and leave time for questions. Shorter is better—focus on impact.
What should I do if a stakeholder dislikes a design?
Stay calm. Ask what concern they have, then explain your rationale. Offer to test both versions with users if necessary.
Should I show unfinished designs?
Yes—early feedback is valuable. Just make it clear what’s conceptual vs. finalized to avoid confusion.
What tools are best for presenting UX?
- Figma (with comments and prototypes)
- Loom (for walkthrough videos)
- Notion or Google Slides (for structured storytelling)
What if stakeholders ask for too many changes?
Set clear goals for the session. Remind them of the user research and offer to validate changes through testing instead of guessing.
Conclusion
Great UX presentations don’t just show screens—they communicate impact.
By leading with user problems, tying your work to business goals, and telling a clear story, you’ll earn stakeholder trust and keep your project moving forward.
