A demo is evidence of possibility. It is not evidence of readiness.
This matters because demos borrow from the future. The dataset is clean. The user is cooperative. The network works. The operator knows exactly where to click. The product looks real because every source of entropy has been removed.
Deployment is where the entropy returns.
The missing checklist
Before a demo becomes a launch plan, answer these:
- Who owns the first failure? Name the person, not the team.
- What gets rolled back? Code, config, data, customer state, or all of it?
- What will support say? If the answer is “we will brief them later,” later has already arrived.
- What metric tells us to stop? Launches need brakes.
The demo can skip these because the demo is theater. Production cannot.
Good teams enjoy demos and distrust them. They treat applause as a signal that the idea is worth hardening, not proof that the hardening happened.
The distance between demo and deployment is where most product risk lives. Put it on the plan.