presentation-deck
owl-listener/designer-skills
Structure design presentations that persuade your specific audience and drive decisions.
What is presentation-deck?
A skill for organizing design presentations tailored to different audiences—stakeholders, reviewers, executives, or portfolio contexts. Use this when presenting internally or seeking approval; for written design arguments use design-rationale, and for portfolio narratives use case-study.
- Provides four presentation templates: Stakeholder Update, Design Review, Final Showcase, and Portfolio/Case Study
- Applies a universal six-step structure: Hook, Context, Journey, Solution, Evidence, and Ask
- Adapts messaging and detail level for executives, engineers, designers, or mixed audiences
- Offers slide design principles including one idea per slide, visual-first approach, and progressive disclosure
- Includes audience-specific guidance on what to emphasize and how to layer information
How to install presentation-deck
npx skills add https://github.com/owl-listener/designer-skills --skill presentation-deckHow to use presentation-deck
- 1.Choose your presentation type (Stakeholder Update, Design Review, Final Showcase, or Portfolio/Case Study)
- 2.Identify your primary audience and their concerns (executives, engineers, designers, or mixed)
- 3.Structure your slides using the universal six-step framework: Hook, Context, Journey, Solution, Evidence, Ask
- 4.Apply slide design principles: one idea per slide, prioritize visuals over text, reveal complexity gradually
- 5.Adapt language and detail level to match your audience's priorities (business value for executives, technical specs for engineers)
- 6.Prepare speaker notes for each slide and create backup slides for anticipated questions
- 7.Rehearse with a colleague before presenting
Use cases
- Present design progress and decisions to internal stakeholders for alignment
- Conduct a design review session to gather feedback from peers or leadership
- Pitch a final design solution to gain approval and secure resources
- Showcase a completed project in a portfolio or case-study context
- Adapt the same design work for different audiences (executives vs. engineers vs. designers)
- Product designers and UX/UI designers presenting internally
- Design leads or managers conducting design reviews
- Anyone seeking approval or feedback on design work
- Portfolio builders documenting case studies
presentation-deck FAQ
Use presentation-deck for live presentations to internal audiences or when seeking approval. Use case-study for portfolio narratives and design-rationale for written design arguments.
Start with the universal structure, then adjust: lead with business impact for executives, include technical details for engineers, emphasize process for designers, and layer detail progressively for mixed groups.
Speaker notes provide context and talking points for each slide—background information, key messages, anticipated questions, and transitions between sections.
Follow the one-idea-per-slide principle and show visuals over text. Use progressive disclosure to reveal complexity gradually, with detailed information available in backup slides or speaker notes.
The Hook answers 'Why should you care?' with a problem, data point, or story. Context answers 'What do you need to know?' with background, constraints, and relevant information.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: presentation-deck
description: 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
- Hook — Why should the audience care? (problem, data, story)
- Context — What do they need to know? (background, constraints)
- Journey — How did you get here? (process, key moments)
- Solution — What are you proposing? (the design, with rationale)
- Evidence — Why is this right? (research, testing, data)
- 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
Related skills
More from owl-listener/designer-skills and the wider catalog.
prototype-strategy
Choose the right prototype fidelity and method to answer your design question efficiently.
readable-measure
Set optimal line length (45–75 characters) for comfortable reading across devices and type sizes.
research-repository
Organize research findings so teams stop redoing studies and build on accumulated evidence.
responsive-design
Design layouts and interactions that adapt across screen sizes and input methods.
search-ux
Design search experiences that help users find what they need with minimal friction.
service-blueprint
Map service delivery across frontstage actions, backstage processes, and supporting systems.