deck
Deck
Core principle
A deck is not a document with pictures. It's a sequenced argument. Every slide answers one question and hands the reader to the next question. If a slide doesn't advance the argument, it doesn't belong. The structure is the product — nail that before touching a design tool.
Step 1: Understand the presentation before structuring anything
Answer these before writing slides:
- Audience: Who is in the room? What do they already know? What do they care about?
- Goal: What decision or action do you want from this presentation?
- Format: Live presentation, leave-behind, or async read? (Changes density and annotation needs)
- Time: How many minutes? Rule of thumb: 2 minutes per slide for live presentations.
- Context: Is this the first time this audience is seeing this topic, or a recurring update?
Step 2: Choose the deck type
Different decks follow different spine structures. Match the type first.
More from iankiku/forwward-teams
medic
(forwward) Interprets medical records, clinical notes, FHIR data, and advises on medical data UI with OCR interpretation, clinical summarization, and drug interaction flags. Triggers on patient records, clinical data, medical PDFs, health-tech products, or medical data presentation.
40ceo
(forwward) Provides CEO-level strategic leadership frameworks for vision, OKRs, hiring, fundraising, resource allocation, and pivot decisions. Triggers on company strategy, growth direction, team scaling, investor relations, or any high-level business decision.
32finance
(forwward) Models unit economics, burn rate, projections, pricing, and revenue forecasting with startup-specific frameworks. Triggers on CAC, LTV, burn rate, runway, pricing analysis, financial models, or any CFO-level financial question.
31legal
(forwward) Drafts terms of service, privacy policies, contracts, IP assignments, and open source licensing after gathering industry and jurisdictional context. Triggers on legal documents, terms, privacy policies, contracts, compliance, licensing, or any legal drafting need.
30team-lead
(forwward) Orchestrates multi-agent engineering and business teams by analyzing tasks, selecting team shapes, assigning specialist roles, and coordinating parallel agent work with skill dispatch. Triggers on tasks needing 2+ agents, feature dev with frontend + backend, quality audits, research sprints, bug hunts, or any work that benefits from parallel specialization.
30devops
(forwward) Configures CI/CD pipelines, Docker, monitoring, alerting, and infrastructure with reliability-first defaults. Triggers on CI/CD, Docker, deployment, monitoring, alerting, infrastructure setup, or production debugging.
29