Cutting a 60-Minute Roadmap Deck to a 20-Minute Keynote
Your B2B SaaS company has a 60-minute, 45-slide product roadmap presentation built for a small analyst briefing. Marketing now wants to reuse it as a 20-minute segment in the opening keynote at a 400-person customer conference. The room is 60% existing customers (mostly IT administrators), 25% prospects, and 15% implementation partners. The speaker is the VP of Product, who tends to improvise and run long. A six-minute live demo is already promised on stage. Sales has asked for the pricing slide to stay in "because prospects are in the room." Product wants to show three roadmap items that have not been announced and are still under NDA. Legal requires a forward-looking-statements disclaimer for any roadmap content. The current deck has 14 slides of feature detail, 9 customer-logo slides, and 5 internal metrics slides. Rehearsal is in four days.
1. Define the audience outcome and decide what stays, what moves, and what is cut. Justify each decision against the three audience segments.
Read the worked answer
Outcome: attendees should leave able to name the three priorities for the next 12 months and know what they must do to prepare. That outcome, not the original deck's completeness, governs every cut.
Keep: the problem statement, the three priorities, the demo, one proof point per audience, and a single closing ask. The 14 feature-detail slides become three priority slides plus a backup appendix; administrators need upgrade and migration timing, so keep one compatibility slide and one support-timeline slide. The nine logo slides collapse to one credibility slide with six logos and a verbal reference to the rest. The five internal metrics slides are cut entirely: they answer an analyst question, not a customer question, and expose numbers Sales has not cleared.
Pricing: prospects are 25%, but a public keynote pricing slide creates commitment risk and bores the 60% existing customers. Move pricing to a post-keynote breakout and a one-line "talk to your account team" close; give Sales the pricing slide in a separate follow-up deck.
Roadmap: do not show NDA items to a mixed, recorded audience. Replace them with capability themes that are already public, and keep specific dates in the NDA briefing. Add the legal disclaimer once on the roadmap slide and once on the closing slide.
2. Build a minute-by-minute run of show for the 20 minutes, including the demo and a buffer. Explain where the disclaimer and pricing content sit.
Read the worked answer
0:00–2:00 - Hook: one customer problem and the outcome of the segment. 2:00–6:00 - Three priorities, one slide each, 75 seconds per slide. 6:00–12:00 - Live demo, with a pre-recorded 90-second fallback queued. 12:00–15:30 - Proof: one administrator story, one partner story, one prospect-relevant result. 15:30–18:30 - Roadmap themes with the disclaimer visible on the slide and spoken once in plain language. 18:30–20:00 - Closing ask and handoff to the breakout sessions.
That totals 20 minutes but includes no slack. Build a 90-second buffer by scripting the demo to 4:30 and pre-building the proof slides so the VP can drop the third proof point if running late. Mark those two slides as optional in the run sheet, not hidden in the file.
The disclaimer belongs on the roadmap slide as a readable footer and on the closing slide, and the speaker should say one sentence such as "These are directional themes, not commitments." Do not read the legal text aloud. Pricing stays out of the keynote and appears only in the breakout deck and the Sales follow-up, so the stage segment never creates a public price commitment.
3. The VP says the 45-slide deck is "the source of truth" and wants to keep every slide in the file, hiding the ones not used. Evaluate that approach and recommend an alternative.
Read the worked answer
Hiding slides is the wrong tool for a timed keynote. Hidden slides still ship inside the file, appear in Presenter view navigation, can be revealed by a stray keyboard action, and add weight and cognitive load for whoever presents next. They also blur ownership: the 20-minute deck and the 60-minute analyst deck start to diverge silently, and the "source of truth" becomes whichever version was edited last.
Recommend three artifacts instead. First, a 20-minute keynote file containing only what will be delivered, with optional slides clearly marked in the run sheet rather than hidden. Second, a Q&A appendix file with the feature detail, internal metrics, and extra logos, opened only if a question demands it. Third, the original 45-slide analyst deck, frozen and labeled as the source of truth with a date and owner.
Use a custom show if the same file must serve both audiences, but test it on the actual presentation machine. The test is simple: can a replacement presenter run the 20-minute version without knowing which slides are hidden? If not, split the files.