Doc-first teams: when you still need slides

Plenty of teams have stopped making decks for everything. Proposals are written as pages. Decisions happen in comments. Meetings start with ten minutes of silent reading. It works well, and people who’ve worked this way rarely want to go back.

Still, slides haven’t disappeared. Some moments call for them, and doc-first teams can get caught out when they arrive. Here’s how to spot those moments and handle them without abandoning the way you work.

When the page is enough

A written page usually beats a deck when:

• People will read it on their own time. Async reviews, weekly updates and decision logs all work better as text.
• The detail is the point. Specs, policies and technical designs need full sentences and edge cases.
• The group is small and already has context. Five people who know the project can discuss a page directly.
• You want written feedback. Comments on a page are easier to track than remarks made during a talk.

If all of these are true, don’t make slides out of habit. Share the page and ask for comments by a date.

When you’ll want slides anyway

Some situations are hard to run from a page:

Large or mixed audiences. An all-hands, a town hall or a cross-team review has people with very different context. A few slides give everyone the same starting point at the same time.

Rooms where people won’t pre-read. Leadership reviews, client meetings and board sessions often have limited reading time. A short deck carries the headline when the page won’t be opened.

Talks with a fixed slot. Conference sessions, demo days and recruiting events expect slides, and the audience has never seen your page.

Moments that need a shared focus. Walking a room through a timeline, a chart or a single decision is easier when everyone is looking at the same thing.

Sharing outside the company. A page full of internal links and comments rarely travels well. A deck is a cleaner package.

Keep the page as the source

The most useful habit for a doc-first team is to treat slides as a view of the page, not a replacement for it. The page holds the reasoning and the detail. The deck holds the few points the room needs to hear.

That means:

• Write the page first, even when you know a deck is coming.
• Update the page when things change, then refresh the slides.
• Link to the page from the last slide so anyone can go deeper.

This also stops arguments about which version is right. The page wins.

Get from page to deck quickly

If your pages are written well, most of the deck is already there.

Start from the headings. On a well-structured page, the headings read like a talk’s running order. Pull them into a list and you have a draft outline. If the page isn’t structured that clearly, a short guide to writing a presentation outline can help you build one before you touch any slides.

Reorder for listeners. Pages often build towards a conclusion. A talk should state it early and then show why.

Pick one point per slide. Each heading or key paragraph becomes a slide with a sentence headline. Supporting detail goes in speaker notes.

Leave reference material behind. Tables, appendices and long lists can stay on the page. Show the two numbers that matter, not the whole table.

The full process is in how to turn a written document into a presentation.

Run the meeting the doc-first way

You can bring good doc-first habits into a slide-based meeting.

• Send the page before the talk, for anyone who likes to read ahead.
• Keep the deck short. Five to ten slides is often enough for an internal session.
• Save time for discussion, the part a page can’t do on its own.
• Capture decisions back on the page straight after, so the written record stays complete.

For recurring sessions, such as a quarterly goals review, the same split applies every time. Turning an OKR page into a quarterly goals deck walks through one example.

A quick way to decide

An illustrative example. A product team in Hyderabad writes a page proposing a new pricing page layout. For the design review with four colleagues, they share the page and collect comments. For the monthly leadership review, they make a six-slide deck from the same page: the change, the reason, the expected effect, the risks, the cost and the decision needed. For the company all-hands, it becomes a single slide inside a wider update.

One page, three outputs, each sized for its room.

If you’re unsure which you need, ask two questions. Will people read before the meeting? Do they share enough context to discuss the detail? Two yeses mean the page is enough. A no on either is a good reason to make a few slides.

The idea in one line

Write first, present when the room needs it, and let the page stay the version everyone trusts.