domains / families / business / presentation-deck

presentation-deck

combined

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`. Build an evidence-linked slide register after context-first intake. Use when an SME needs a presentation deck, speaker notes, or a structured business story.

When to use

• presentation, deck, slides, pitch, pitch deck
• "we have to present to a bank", "investor deck", "client pitch"
• what should our slides say, story structure, narrative
• sales deck, proposal deck, board update, team briefing
• speaker notes, timing, rehearsal
• turning a report into a presentation

When not to use

• This is a content plan. It does not build slides, attach a template, or open a deck
• It has no access to the business's accounts, analytics, CRM or platform, so it cannot
• It cannot build a financial projection. Projections require assumptions, a stated basis
• It cannot design the template. Layout names in `Template Layout` are the names in the
• Deck length depends on the slot, not on a rule. Ten is a recommendation for a 15-minute
• Design tools, animation, video and transitions are out of scope.
• The visual balance of a deck cannot be judged from a table. Someone has to look at the
• Accessibility of a projected deck - colour contrast, minimum type size, a text version

Skill page

Conflict

The two skills overlap in the goal of structuring a persuasive presentation, but they are not interchangeable. The first copy is a design-focused guide that defines presentation types (stakeholder update, design review, final showcase, portfolio), a universal 6-part narrative arc, slide design principles, and audience adaptation for executives, engineers, and designers. The second copy is a business/SME-focused workflow that emphasizes context-first intake, strict validation of facts (marking unknowns as Unknown rather than inventing them), a specific 10-slide recommendation for a 15-minute slot, and the generation of a structured 'slide register' in formats like CSV, SQL, or JSON. The first copy lacks the rigorous intake and data-source validation steps of the second, while the second lacks the design-specific presentation types and visual design principles of the first. Combining them captures both the structural design advice and the rigorous business data validation.