presentation-designlisted

# Presentation Design A slide is seen for as long as it takes to say one thing. That constraint drives every rule here. A deck is not a document with page breaks. If the content only makes sense when read closely, it is a document — say so and use `analytical-document-design` or `writing-documents` instead. Converting a document into slides by cutting it into pieces produces a deck that is bad to present and worse to read. ## One idea per slide The title states the idea as a **claim**, not a topic. Everything else on the slide supports that claim. - "Ingestion is our concentration risk" — a claim. The audience knows what to look for. - "Ingestion metrics" — a topic. The audience has to work out what they are meant to conclude. If a slide needs two titles, it is two slides. Slides are free; attention is not. ## Reading and presenting are different jobs Decide which deck this is, because the answer changes the design and you cannot have both in one artifact: **Presented** — you are speaking over it. Slides carry few words, large type, and one visual. The detail lives in what you say. **Read** (sent, not presented) — nobody narrates it. Slides need enough text to stand alone, which means more words and smaller type, and the deck is longer. When both are needed, build the presented deck and pair it with a document, or add a speaker-notes block that prints but does not project. Do not compromise into a deck that is too dense to present and too sparse to read alone — the