Present your design work for maximum impact

Great work doesn’t speak for itself. You have to speak for it. But too many designers present their work in ways that don’t connect to what stakeholders care about.

Whether it’s presenting your work, looking for a new job, or trying to get buy-in for an idea, storytelling is critical. One concept that will help you every time: make “why”, not “what”, the focus.

Structure your presentations around a simple narrative: context, problem, solution, impact. Frame your work in a way that makes people care.

The four-part structure: context, problem, solution, impact

Every effective design presentation follows this structure. It’s simple, but most designers skip steps or get the order wrong.

1. Context: what’s the situation? why does this matter?

Start with context. Help your audience understand the situation: what’s happening, why it matters, and what’s at stake. This sets the stage for why your work exists.

Good context includes:

• The business goal or opportunity this work supports
• Relevant background: what led to this project, what’s changed
• Stakeholders involved and their concerns or priorities
• Constraints or parameters that shaped the work

2. Problem: what’s broken or what opportunity exists?

Clearly define the problem you’re solving. This isn’t just “users are confused”: it’s a specific problem with evidence and consequences.

A strong problem statement includes:

• Who is affected by the problem
• What the specific problem is (be concrete, not vague)
• Evidence that the problem exists (data, research, feedback)
• Why it matters (what happens if we don’t solve it)

3. Solution: how did you address it? (keep this brief)

This is where many designers spend too much time. Don’t walk through every design decision in detail. Instead, focus on the key choices that solve the problem you defined.

When presenting your solution:

• Show the solution clearly (don’t make people work to understand it)
• Explain the key design decisions that address the problem
• Tie each decision back to the problem you defined
• Keep it concise: show what’s important, not every detail

Remember: you’re not showing off your process. You’re showing how you solved the problem.

4. Impact: what changed? what did we learn? what’s next?

End with impact. This is where you connect your solution to outcomes. If you have data, share it. If you don’t, explain what you expect to see and how you’ll measure it.

Impact might include:

• Results: metrics that improved, behaviours that changed
• Learnings: what you discovered through the work
• Next steps: what happens next, what you’ll iterate on
• Business connection: how this supports business goals

Using Minto’s pyramid structure

Another powerful framework is Minto’s Pyramid, which flips the traditional structure:

1. Conclusion first: Lead with impact and outcomes. Tell them what you achieved before explaining how.
2. Key arguments: Support with problem and results. Give them the main points that support your conclusion.
3. Detailed information: Research, process, and methodology come last. Only if they want to dive deeper.

This structure respects busy stakeholders’ time. They get the answer first, then the reasoning, then the details if they want them.

Make “why” the focus, not “what”

The most common mistake is focusing on “what” you designed instead of “why” it matters. Your stakeholders don’t care about your design process: they care about outcomes.

Tailoring your presentation to your audience

Different audiences care about different things. Tailor your presentation accordingly:

For executives and business leaders

Focus on business impact. Lead with revenue, cost, or strategic goals. Keep design details minimal. Use their language: metrics, goals, outcomes.

For product managers

Focus on user problems and product metrics. Show how the design addresses user needs and connects to product goals. They care about both user value and business value.

For engineering teams

Focus on feasibility and implementation. Show constraints you’ve considered, technical implications, and how the design scales. They care about buildability and maintainability.

For other designers

You can go deeper on craft and process. But even here, connect decisions to outcomes. Show how design choices serve goals, not just aesthetics.

Common presentation mistakes

Mistake 1: starting with the solution

Don’t jump straight into showing designs. Without context and problem definition, stakeholders won’t understand why your solution matters. Always start with context.

Mistake 2: burying the impact

Don’t save impact for the end if you’re presenting to busy stakeholders. Use Minto’s Pyramid: lead with what you achieved, then explain how.

Mistake 3: focusing on process over outcomes

Your design process is interesting to other designers, but stakeholders care about results. Keep process details brief unless specifically asked.

Mistake 4: using designer language

Avoid jargon that only designers understand. Frame everything in terms stakeholders can relate to: problems, outcomes, metrics, goals.

Practice: structure your next presentation

Before your next presentation, structure it using the context-problem-solution-impact framework:

Remember: make people care

The goal of a presentation isn’t to show off your design skills: it’s to make people care about the work. Structure your presentation to tell a story that connects to what matters to your audience.

When you frame your work around context, problem, solution, and impact, you’re not just showing designs: you’re showing how design creates value. And that’s what gets people to care.