It is the most important meeting we run
Thirty minutes, every Friday, everyone. Demos are the forcing function for everything that matters — shipping cadence, cross-team awareness, narrative quality.
It is also the only meeting we have never cancelled. That consistency is most of the value: a forcing function that moves is not a forcing function.
Three rules
The rules have not changed in two years:
Only ship things — if it is not on production behind a flag, it does not get demoed.
No slides. Ever. If you cannot show it, you cannot explain it yet.
Eight minutes maximum per team, hard stop, timer visible.
The eight-minute limit is not about time. It is about forcing someone to decide what the point is before they start talking.
What it fixed
Cross-team awareness, obviously. But the bigger effect was on scope: a team that has to show something every Friday stops shipping four-week invisible refactors without saying so.
It also killed a category of politics. When everyone watches the same thirty minutes, "what is that team actually doing" stops being a question people ask in private.
And it made the product better in a literal way — about one in five demos ends with someone from another team pointing out a screen they already built that does half the job.
How a demo actually runs
One person shares a screen and drives. No handoffs mid-demo — if two people built it, one of them talks and the other answers questions afterwards.
The structure that works, and that we now suggest to new joiners: what it does, who asked for it, the thing that surprised you while building it. Thirty seconds, four minutes, three minutes.
Questions go in the chat during and are answered in the last five minutes, not interleaved. That single rule bought back about a third of the runtime.
What it costs
Thirty minutes times everyone, every week, is not cheap: with 40 people it is roughly half an engineer's year. We have run the arithmetic and kept the meeting.
The other cost is quieter: work that is hard to demo — infrastructure, security, the compliance backlog — feels less visible. We handle it by giving those teams the first slot, not the last, and by demoing dashboards and incident timelines instead of screens.