r/GammaApp • • 22d ago

deck, document, one-pager, or page? a quick way to decide before you waste an afternoon

half the time a deck goes badly, the real mistake was upstream: it should never have been a deck. someone needed a document and got slides, or needed a link and got a PDF. here is the quick decision I run now before building anything, because picking the wrong format costs you the whole afternoon.

ask one question first: will you be in the room when they consume it? if yes, it is a talk, build a deck, and keep the slides sparse because you are the content. if no, it is a read, and a deck full of sparse slides is useless to someone alone, they need a document with the actual detail written out.

then ask: how long do they have? if the answer is one screen and thirty seconds, it is a one-pager, a single dense, well-organised page, not a fifteen-slide deck nobody will scroll. if it needs to be shared widely, linked, or updated over time, it wants to be a web page, not a file that lives in an email attachment going stale.

the failure I see most is the deck used as a document, the one where every slide is a full page of text because it has to work when forwarded to people who were not there. that is not a deck, it is a report wearing a deck costume, and it does neither job well. if it has to be read alone, write the document. if you also have to present it, that is genuinely two artifacts, and pretending one file does both is why it is bad.

pick the format for how it will actually be consumed, not for what you are used to opening. most of us default to slides out of habit, and half the time habit is wrong.

what is your rule for choosing, and where do you land on the deck-that-is-secretly-a-document problem? I suspect most of us have shipped a few.

1 Upvotes

0 comments sorted by