There’s a moment in almost every Investor Day rehearsal when a slide that looked fine for six weeks suddenly doesn’t. The team built it on a laptop, reviewed it on a laptop, approved it on a laptop. Now it’s forty feet wide on an LED wall. The CFO stands in front of it, and the footnote nobody questioned is a grey blur from the third row. Nothing about the slide changed. The scale did.
That’s why presentation design belongs in the production conversation from the start. Investor Day presentation design has to serve three audiences at once: the people reading the stage screen, the investors watching through a webcast player, and the analysts downloading the PDF afterward. One is looking past the CFO’s shoulder. Another has your webcast beside a spreadsheet. The third may open the file weeks later, with no idea what anyone said on stage. You’re asking a lot of one deck.
The practical answer is to build two versions from one design system: a stage deck for distance and camera, and a reference deck for reading. Keep the story and the numbers consistent; give each audience the explanation they need. That distinction sounds small until you try to make a margin bridge work equally well behind a moving executive and inside an investment-committee memo. Same numbers. Very different reading conditions.
The room, the webcast, and the record
In the room
Start with the room. At stage scale, a slide behaves like a broadcast graphic. The person in row twelve may be reading your type from sixty feet away, under stage lighting, while also watching a presenter. They want to follow the argument. Give them a fighting chance: one clear idea, large type, and enough contrast to find the important number before the speaker moves on. If they spend that time squinting at a label, you’ve lost the sentence that was supposed to explain it.
On the webcast
The webcast is a different problem. An analyst who didn’t fly in may have the deck open inside a player window that’s sharing a monitor with a spreadsheet. Stream compression eats hairline rules, thin chart strokes, and low-contrast greys. A table that’s dense in the room can become illegible at 720p in a quarter-screen window. The slide has to survive being small, and the production team needs to know when to give it the full frame. That is part of treating your Investor Day like a broadcast.
In the PDF
Then there’s the PDF, quietly waiting on the IR site after everyone packs up and goes home. The stage deck serves a morning. That file may stay in circulation for years. Analysts reference it in notes, paste its charts into committee memos, and revisit its assumptions when the next quarter’s results arrive. Research tools can use it to summarize your strategy for people who never watched a minute of the event. The PDF has to make its case without the CFO standing next to it.
The deck breaks in the org chart
The trouble usually starts somewhere much less dramatic than the stage: a shared folder. Each business unit builds its own section on its own timeline. By the time the sections come together, you’ve got several shades of the brand blue, three competing chart styles, and financial tables someone pasted straight from a spreadsheet at eight-point type. A designer gets the file two weeks out with a familiar request: “Can you clean this up?” By then, the team has already settled the slide count, the claims, and the charts. The decisions that most need a second look are the ones nobody wants to reopen.
This is the same handoff problem that shows up across investor relations production. Each contributor can finish their part without anyone checking whether the whole thing holds together. The CEO frames the strategy one way, a segment leader introduces a different set of priorities, and the CFO has to reconcile both in the financial section. Matching their fonts won’t solve that.
Why slides get crowded
Then comes density as reassurance. Anyone who has sat through a deck review knows the impulse: add the extra number, keep the backup chart, squeeze in one more footnote. A full slide feels safer. But someone in the audience has to read it while an executive keeps talking. Put the supporting schedules in the reference deck or appendix, where people can actually work through them. Keep the context the room needs to understand the claim. A slide can satisfy every reviewer and still fail every reader.
Why doesn’t an earnings deck work on stage?
An earnings deck often works as a self-contained document. Readers open it on a laptop at arm’s length, move through the tables at their own pace, and stop on the footnotes. That is a reasonable brief for that format. The trouble starts when a team stretches the same template across a multi-hour live event, where the speaker controls the pace and the audience cannot pause the wall.
Put six charts and four footnotes on a projected slide, and the room starts reading while the CEO keeps talking. Now the audience has to choose which argument to follow. Of course, taking everything off the slide doesn’t solve it either. An oversized slogan won’t explain a capital allocation decision. Give the speaker something worth walking through: a useful chart, a precise claim, and enough context to understand the comparison. The design should make the substance easier to follow.
Read the titles on their own
Try this before the next review: read only the slide titles, in order. “Operations,” “Growth,” and “Financial Overview” tell you where you are in the agenda. What do they tell you about the business? A title such as “New capacity supports the next phase of growth” gives the speaker a claim to explain and the chart a job to do. Use it only when the evidence supports it. If the titles promise more than the numbers deliver, better typography won’t close the gap.
Design starts when the narrative does
The useful conversation happens before anyone builds a template. What does each section need investors to understand? Which chart or example will help them understand it? And how much of the explanation belongs on stage versus in the reference deck? Get IR, finance, communications, and production into that conversation while the team can still change the sequence. The Investor Day production playbook puts this work alongside scripting, filming, and rehearsal, where those decisions can inform each other.
- A typographic scale that holds up at distance. Use the wall dimensions, seating depth, and webcast layout to set minimum sizes, then test them before content pours in. A point size on a laptop tells you very little about the experience from the back row.
- One data-visualization language. Define the guidance bridge, margin walk, and segment colors once. Apply them throughout the deck so a chart in section five reads naturally because section two already taught the audience how to read it.
- Builds that pace the story. Animation earns its place when it controls the order in which the audience absorbs information, revealing a chart as the CFO explains the drivers. Give the playback operator clear cues. When animation adds only decoration, cut it.
- A reader’s cut. Plan the reference version at the same time. Decide which slides need more explanation, where the supporting schedules belong, and how the reader will find them. Leaving that work until the export usually means leaving it unfinished.
Ask about the details
This is also the time for the unglamorous questions. Who supplies the source data? Who approves the financial language? Who makes the call when two reviewers want opposite things? Five people sending five marked-up files can consume an afternoon before anyone makes a single change. Name the person who reconciles that feedback at the first review, while everyone still has the patience to agree on a process.
How much context does a financial chart need?
Take a margin-expansion slide. The CFO knows this bridge inside out: pricing adds here, mix moves there, operating improvements close the gap. The audience is seeing it for the first time. They need a visible starting point, a visible destination, and labels that connect each step to what the CFO says. Floating percentages may look clean, but they leave the audience doing mental arithmetic at exactly the moment you want them listening.
In the reference version, imagine someone opening that chart on Tuesday with a colleague asking, “What period does this cover?” Make these details easy to find:
- Period and units: the dates, currency, percentages, or other measures behind the figures.
- Business scope: whether the chart covers the whole company, a segment, or a specific operation.
- Basis of comparison: what the starting point and end point represent.
- Adjusted measures: the definition and supporting reconciliation, when applicable.
Have the content reviewers check both versions together. Moving a qualification off the page may seem like a small design decision until it changes what the number appears to mean.
The same discipline helps when the subject is harder to show. If a segment leader claims that AI improves productivity, a generic architecture diagram will do little to explain the economics. A workflow, a before-and-after comparison, or a short demonstration can give the claim something concrete to stand on. Our AI briefing for IR leaders explores that connection between operational evidence and the investor story. The deck’s job is to make the connection clear enough that an analyst can explain it to someone else.
The camera gets a vote
The front row gives you one view. The camera gives you another. It sees the screen, the presenter, and the lighting as one image; the person at home gets whatever survives at the size of their player window. A template can look terrific in isolation and fall apart in that frame. Bring the camera and lighting teams into the review before everyone falls in love with it. Four details deserve an actual test:
- The wide shot. When the slide shares the frame with the presenter, small type and delicate chart rules can disappear. Test the actual composition. If a figure matters to the argument, the remote viewer needs enough time and screen space to read it. Plan the switch to a full-screen slide when the detail warrants it.
- Brightness against the presenter. A pure-white slide on a large LED wall can become the brightest object on stage. Exposing for the wall can leave the executive looking dark. Test the palette with the lighting and camera teams; dark or mid-tone backgrounds may give them more room to balance the image.
- The safe area. Lower-thirds, captions, and player controls can cover content near the frame’s edges. Confirm the actual overlay positions and leave critical figures clear of them. A footnote in the bottom band is no help if the webcast puts the speaker’s name across it.
- The four-second chart. Treat a quick glance as a useful design test. Can someone identify the takeaway without searching a legend or decoding several axes? Label data directly where possible. Then check that the speaker gives viewers enough time to understand it.
Do you need a separate deck for analysts?
For most Investor Days, yes: build a stage version and a reference version from the same design system. Keep the typography, palette, chart conventions, and approved figures consistent. Plan the differences early, so the reference deck doesn’t become a last-minute export of slides that only make sense with a speaker:
| Design decision | Stage deck | Reference deck |
|---|---|---|
| Explanation | The executive talks through the argument. | The page supplies the explanation without a presenter. |
| Charts and labels | Large labels and a clear takeaway that the room and webcast can follow. | The same figures, with the period, units, scope, and basis of comparison. |
| Supporting detail | Keep qualifications needed to interpret the claim beside the number. | Include supporting schedules and make definitions and reconciliations easy to find. |
| Reading order | Follow the speaker’s delivery and the show cues. | Use descriptive titles, page numbers, and links so readers can find what they need. |
Presentation best practices
That does not mean stripping every qualification off the wall and hoping someone finds it in the PDF. Review each slide for what the audience needs to interpret it correctly. Some detail can move to a supporting page. Some belongs beside the number. Make that decision with the people responsible for the content, then design around it.
Animation needs a little care here, too. A chart that reveals three drivers in sequence can make perfect sense as the CFO talks through it. Export the final frame, and those drivers may pile into a single crowded image with none of the reasoning that connected them. Give the PDF a complete static view or a short sequence of pages that preserves the explanation. A video thumbnail needs the same attention: add a useful description and a working link to the film or replay. “Watch this” is a dead end when there’s nothing to click.
The 9 PM revision needs an owner
It’s 9 PM. The deck has cleared every review on the calendar, and a guidance figure changes. These things happen. A shared layout helps the designer make the fix quickly, but the same number may also appear in a speaker script, a webcast asset, and the PDF waiting on the IR site. Updating the slide is the easy part. Finding everywhere else that number lives takes a process you should agree on well before 9 PM.
Give one person responsibility for the current master and the release list. For each change, record:
- The slide number and affected chart, title, or note.
- The previous figure and its approved replacement.
- The person who approved the change.
- Every file that needs the update, including the stage deck, reference PDF, script, and webcast assets.
Check the chart label, the takeaway title, and the speaker notes together. A corrected bar with yesterday’s number in the headline is still a wrong slide.
Agree on a content cutoff and an exception path before show week. Necessary changes will still arrive. The point is to make sure the right people see them and the playback operator knows which file to load. Use clear version names and confirm the replacement on the primary and backup playback systems. A filename that ends in “FINAL” is not evidence that everyone has the same deck.
What should you test in rehearsal?
Eventually, the deck has to leave the laptop. Rehearse with the real file on the real screen, early enough to fix what you find. Call it the wall test: every slide earns its place at full size or goes back for a rebuild. Walk to the back of the room. Watch the webcast layout on a laptop. That chart everyone approved at the conference table may look very different from either seat. Better to have that conversation during rehearsal than watch an investor lean forward and give up.
This is also where slide counts get honest. Forty slides in a twenty-five-minute agenda block can look manageable in a spreadsheet. Add the speaker’s explanation, transitions, and a pause on the number that matters most, and the math starts to change. Time the actual delivery. If the presenter rushes the same chart every run, stop asking them to talk faster. Work out whether the chart needs a simpler explanation or the argument needs more time.
Run the handoffs, too
Leave time to rehearse the moments that can interrupt a good presentation:
- Slide builds: confirm who advances them and what the presenter sees on the confidence monitor.
- Video playback: run the transition into the film and back to the speaker.
- Speaker changes: practice the handoff and confirm the next deck is ready.
- Q&A: have the operator find a supporting slide while the presenter answers a question.
A leader should not have to discover the clicker behavior in front of investors. Record a portion of rehearsal and review the output the remote audience will actually receive.
Give the PDF to a fresh reader
Finally, give the reference PDF to someone who has not sat through six weeks of review. Ask them to explain the main claim and identify the assumptions behind it. The internal team knows what every abbreviation means and remembers the explanation that disappeared three drafts ago. A fresh reader finds those gaps quickly.
The deck outlives the day
Six months later, someone may open slide 37 without ever seeing slides 1 through 36. An analyst forwards a chart. A new investor checks an assumption. A colleague pulls a page into a briefing. Write takeaway titles that still make sense in those settings, put the reporting period and units beside the figures, and explain unfamiliar abbreviations on first use. The chart needs enough context to travel. You won’t be there to fill in what it leaves behind.
Check the file you actually export
Open the exported PDF and check it as a reader would:
- Can you select and search the text?
- Do the links take you to the right pages, films, or replay?
- Can you read chart labels at a normal viewing size?
- Does the reading order make sense with assistive technology, and do meaningful visuals have useful descriptions?
Export settings can undermine a careful design, especially when slides become flattened images. Selectable text is a useful check, but it does not by itself establish accessibility; review the document structure as well.
Give the deck a durable home alongside the replay and transcript, whether that is the main IR site or an Investor Day microsite. Label the event date and the version clearly. Keep links consistent enough that a follow-up email can take an analyst straight to the relevant material. The person looking for your margin assumptions six months later should not have to reconstruct the event to find them.
Bring the deck into the production plan
And then there’s the impression the whole thing leaves. A coherent deck makes it easier to see a coherent business. When segment colors mean the same thing in every section and the charts speak one visual language, the audience can spend its attention on management’s argument. If each section introduces new conventions, investors have to stop and decode the presentation again. Don’t make them do the work your team should have finished in rehearsal.
Work out the screen dimensions, camera plan, and webcast layout before the design team builds the template. Let the Investor Day production team see the slides as they take shape, and review both versions with IR and finance. That gives everyone a chance to flag a problem before a fix means reopening a deck the whole company has already approved.
If your team is already building the deck, bring a few slides to the production team now. Show them the dense chart, the animation, the slide nobody can agree on. Those are useful conversations to have while there’s still time to do something about them.
