Presentation Deck

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

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`.

AI-generated overview

Structures design presentations for a specific audience and decision, covering deck types, slide principles and audience adaptation.

What it does
This skill provides guidance for structuring design presentations that communicate clearly and persuade effectively. It defines presentation types such as stakeholder updates, design reviews, final showcases and portfolio case studies, each with a suggested structure. It also offers a universal six-part structure, slide design principles, audience adaptation advice and presentation best practices.
When to use it
Use it when preparing an internal design presentation and you need help organizing the narrative for a particular audience and decision. It suits stakeholder updates, design reviews, final showcases and portfolio or case study decks.
Requirements
No tools, packages or credentials are required; it is instructions only and ships no scripts.

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

Source and attribution

Source:owl-listener/designer-skillsindesigner-toolkit/skills/presentation-deckat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Presentation Deck Agent Skill | SourceWeft