Academic defenseLive + Q&A
Nine months after the dike breach
A committee defense: one question, one field study, and the limits of a nine-month answer.
Presentation skill · fictional cases
Eight decks. Eight occasions.
A presentation is an argument an audience can follow and act on. These decks are built to be inspected: narrative, evidence, language, time, visual design, and speaker notes in one self-contained file each.
NarrativeOne takeaway; an arc the titles can carry.
EvidenceNumbers with sources, dates, and comparisons.
LanguageSpoken, written, and slide registers.
TimeBudgets, must-cuts, Q&A, rehearsal.
VisualProjection scale, honest charts, grayscale.
AccessAlt text, reading order, captions, contrast.
The decks
Pick the occasion.
Each card opens a self-contained HTML deck. Use ← → to navigate, N for speaker notes, and print to PDF for a handout. The requirements link explains the brief behind the deck.
Series A pitchLive
Tidewise — flood-risk intelligence
A ten-minute investor pitch: the maps are older than the storms, and utilities need asset-level risk.
Incident postmortemHybrid readout + written report
Checkout outage — 47 minutes
A blameless postmortem readout: timeline, root cause, actions, and the systemic lesson.
Architecture reviewLive + Q&A
Streaming event ingestion at Meridian
A decision review: batch is breaking, streaming is expensive, and the trade-off is operational.
KeynoteLive
Design for the worst day
A twelve-minute keynote: the best day is a demo; the worst day is the product.
WorkshopLive facilitation
Design review that catches what CI cannot
A 90-minute workshop: evidence triangulation, two exercises, and three rules to take back.
Business reviewLive readout + written one-pager
Q3 business review — Lumen
A quarterly readout: revenue is up, SMB churn is the signal, and the ask is a decision.
Product launchLive demo + Q&A
Atlas 2.0 — the field is the product
An eight-minute launch: offline-first field service, a three-scene demo, and a clear CTA.
What it proves
Different rooms, same discipline.
The deck changes; the standards do not. These cases cover evidence, persuasion, learning, governance, demo, and craft.
EvidenceAcademic
Defend a claim, not a method
One question, two results, explicit limits, and a recommendation the committee can act on.
PersuasionPitch
Make the ask inevitable
Bottom-up market, traction, a business model, and a specific ask — one number per slide.
LearningPostmortem
Learn without blaming
Impact, timeline, trigger, amplifier, actions with owners, and a systemic lesson.
DecisionArchitecture
Make the trade-off explicit
Options, criteria, a recommendation, a migration plan, and a rollback the board can trust.
StoryKeynote
One idea, one action
A hook, a single idea, three pieces of evidence, three practices, and a close that lands.
TeachingWorkshop
Make the room do the work
Objective, warm-up, concept, example, two exercises, share, and three rules to take back.
GovernanceBusiness review
Surface the variance
Headline, KPI table, drivers, actions, and three asks with owners and dates.
LaunchProduct
Demo the value, not the features
Problem, insight, three-scene demo, pilot evidence, availability, one CTA.
Production loop
Built like a deck, not a document.
The same loop the presentation skill asks for: fix the stage, settle one sample, write in batches, check a contact sheet, and keep one source for the notes and the time budget.
1 · Stage + tokens16:9, type scale, color roles, safe margins.
2 · Skeleton + sampleOne slide proves the layout before thirty follow.
3 · Section dataTitle, budget, notes; generate counter and notes.
4 · Contact sheetBatch screenshots; inspect the sheet, then the page.
5 · Assets + factsOfficial source first; comparison matches the claim.
Context
The decks have requirements, not just slides.
Each case has an inferred requirements document: audience, intent, narrative, evidence, language, visual rules, time budget, verification, and open questions. Read it before a redesign or a review.
A committee defense academic-defense
A ten-minute investor pitch series-a-pitch
A blameless postmortem readout incident-postmortem
A decision review architecture-review
A twelve-minute keynote keynote
A 90-minute workshop workshop
A quarterly readout business-review
An eight-minute launch product-launch
Use the skill.
The presentation skill is part of the design bundle. It covers live, written, and hybrid presentations, from a ten-minute pitch to a ninety-minute workshop.
npx skills add kimmywork/skills --skill presentation
claude plugin install design@kimmywork-skills
Fictional cases. Each deck is one self-contained HTML file with speaker notes and a time budget. Photos via Unsplash; credits in assets/CREDITS.