A demo is an argument dressed as a fact. The trick is that nobody showed you the conditions.
I have run demos built to land, and I have sat through demos built to land on me. The second is the more instructive seat. You can feel the machinery working even while it works on you.
Here is what matters: nobody in the demo is lying to you. The tool really did do that. The output really was that good. What you are not being shown is the frame around it — the example that was chosen, the prompt that was rehearsed, the three attempts that came before the one you saw, and the absence of everything that makes your actual work hard.
A demo is a controlled experiment
Someone chose the example. The whole result of a demo lives in the setup, and the setup is invisible by design. That isn’t malicious — a good demo is supposed to be clean. But clean is the tell.
The chosen example has no history. No twelve-year-old file with three designers’ fingerprints on it. No brand system with forty rules, half of them unwritten. No stakeholder who looks at the perfect output and says I don’t know, it doesn’t feel like us, and cannot tell you why. The demo removes the exact things that eat your week, and then shows you how fast the remainder goes.
What the room never sees
The demo is always a first attempt at a friendly problem. It is never the second time, when the novelty is gone and the person is tired and the brief contradicts itself. It never includes the moment under deadline when someone abandons the new method and reverts to the one their hands already know — which is the moment that actually decides whether adoption happened.
And it never shows you the person who has to own the output. In the demo, the output belongs to no one. In your organization, someone has to put their name on it, stand behind it in a review, and answer for it when it’s wrong. That person is the whole story, and that person is not on the screen.
How to watch one
You don’t need to be technical to evaluate a demo well. You need three questions, and the discipline to ask them out loud.
What did you not show me? Hand over your file. The ugly one, the real one, the one with the contradictions in it. Then watch what happens to the nine-second number. If the answer is “we’d need to set that up,” you have just found where the cost actually lives.
Whose Tuesday does this land on? Name the person whose working method has to change for this to be real. Are they in the room. Do they want it. Because if adoption depends on someone who wasn’t consulted and isn’t convinced, the demo measured nothing you can use.
What does the second week look like? The demo is a honeymoon. Adoption is a marriage. Ask what happens after the interest wears off and the tool is just one more thing on the list — because that is the only condition under which it has to survive.
None of this makes the demo worthless. A rendering of a building isn’t worthless — it tells you the building is possible, that someone thought it through, that the light will fall a certain way. It just doesn’t tell you what it costs to pour the foundation, or whether the ground will hold it.
So believe the demo about the ceiling. Disbelieve it about the floor. Believe it about what the tool can do at its best, and refuse to believe it about what it will cost you to get there. The distance between those two numbers is not a tooling gap you can close by buying a better tool. It is the entire job.
I write about creative leadership, AI adoption, and the parts of the job nobody puts in a keynote. One post every two weeks.