Most “demo days” or “show-and-tells” inside companies die the same death. The first one has energy. People show real work. By the third one, it’s a 90-minute slide presentation where eight projects report status updates to a half-empty room.
The format isn’t broken. The execution is.
A good demo day is the cheapest possible way to build cross-team context. It replaces weeks of “I didn’t know you were working on that” with a 15-minute live walkthrough that everyone in the company can absorb.
The Format That Doesn’t Decay
Time-box the Whole Thing — Hard
30 minutes total. Three demos. Ten minutes each.
Any longer and attendance collapses. The constraint is what makes it work. People will fight to keep their ten minutes, and that fight produces better demos.
Make It Live, Not Slides
The audience should see the actual thing — the tool, the dashboard, the workflow, the spreadsheet. If you can’t show it live, you don’t have a demo; you have a status report. Slides are a fallback, not a default.
If your demo is “we added a button to the home page,” *show the button*. Click it live. Show the analytics tab that proves it works. Don’t show PowerPoint about the button.
Require Three Things From Every Demo
Every presenter answers, in order, in under 10 minutes:
- What is the user problem? — One sentence. If you can’t say it in one sentence, you don’t know the problem yet.
- What did you ship? — Live demo of the actual thing.
- What did you learn? — Not “we learned a lot.” A specific, falsifiable insight that the team would not have had three months ago.
Skip #1 or #3 and you’re back to a status update.
The Roles That Keep It on Track
Three roles per session:
- Host — Introduces the demo, controls the timer, asks the one hard question at the end of each slot.
- Presenter — 1-2 people, no more. They bring the live thing and the one key insight.
- Audience — Required to send one follow-up question or “what I learned” note within 24 hours. This is non-negotiable. It’s what makes the demo day actually create cross-team context instead of being a passive broadcast.
Anti-Patterns to Avoid
Status-only demos. “We’re on track for Q3, blocked on X” is not a demo. That’s a Slack update. Cut it.
Demos without a clear owner. If three people tag-team, the energy diffuses and the timeline explodes. One main presenter; one backup.
Recorded demos. Recording kills the live energy. Do it live, every time, even if attendance varies. The live format is the point.
Endless Q&A. “Questions?” is an open invitation to a 45-minute discussion that loses the room. Better: “Send your question in #demo-day Slack and we’ll follow up.” Time the discussion; don’t let it bleed.
Why It Works
Demo day is one of the few company-wide rituals that scales linearly with size. A 30-person company can run it perfectly. A 500-person company can run it perfectly with one camera and a screen-share link.
The benefit compounds: after six months, your team has a running archive of what’s been built, what’s been learned, and who’s been doing the work. People leaving the company don’t take their context with them — it’s been broadcasted.
The cost: 30 minutes a week or month. That’s it.