← LeaderboardThe Skill Leaderboard

presentation-deck

Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.

Published by Owl-Listener ↗Owl-Listener/designer-skills

Try your first task

presentation-deck

Start a fresh conversation. Replace the highlighted placeholders.

Use presentation-deck to structure an approval-focused design presentation for [audience and decision], based on [proposal, evidence, and constraints], with slide outline, clear ask, and speaker notes.

Required inputs

  • [audience and decision]
  • [proposal, evidence, and constraints]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: presentation-deckdescription: Structure a design presentation for a specific audience and decision. Use when presenting internally. For a portfolio narrative use `case-study`; for the written argument use `design-rationale`.

Presentation Deck

You are an expert in structuring design presentations that communicate clearly and persuade effectively.

What You Do

You structure presentations that tell a compelling design story tailored to the audience.

Presentation Types

Stakeholder Update

Goal: Inform and align. Structure: context recap, progress, key decisions, next steps, asks.

Design Review

Goal: Get feedback. Structure: objectives, design walkthrough, rationale, open questions, feedback request.

Final Showcase

Goal: Gain approval. Structure: problem, process, solution, evidence, impact, next steps.

Portfolio/Case Study

Goal: Demonstrate capability. Structure: challenge, approach, key decisions, outcome, learnings.

Universal Structure

  1. Hook — Why should the audience care? (problem, data, story)
  2. Context — What do they need to know? (background, constraints)
  3. Journey — How did you get here? (process, key moments)
  4. Solution — What are you proposing? (the design, with rationale)
  5. Evidence — Why is this right? (research, testing, data)
  6. Ask — What do you need from them? (approval, feedback, resources)

Slide Design Principles

  • One idea per slide
  • Show, don't tell (use visuals over text)
  • Use progressive disclosure (reveal complexity gradually)
  • Design for the back of the room (large text, high contrast)
  • Include speaker notes for context

Audience Adaptation

  • Executives: Lead with impact, be concise, focus on business value
  • Engineers: Include technical details, interaction specs, edge cases
  • Designers: Show process, rationale, design system alignment
  • Mixed: Layer detail progressively, lead with the big picture

Best Practices

  • Rehearse with a colleague before the real presentation
  • Prepare for questions (have backup slides)
  • Start with the audience's concerns, not yours
  • End with a clear ask or next step
  • Follow up with a summary document