title: The Demo → Demo Loop url: https://daverupert.com/2022/06/demo-to-demo-loop/ hash_url: 9f8c0e75066c1882a3b4ce084e3223ed archive_date: 2024-01-09 og_image: https://daverupert.com/images/opengraph/demoloop.png?reset=1 description: The personal blog of Dave Rupert, web developer and podcaster from Austin, TX. favicon: https://daverupert.com/favicon.ico language: en_US

The design squiggle with a tightening loop overlayed

I’m 100% convinced that working demo-to-demo is the secret formula to making successful creative products.

Video games have a strong history of ritualizing prototypes, play testing, and following the fun. There’s even some data that suggests prototypes increase your chances of success.
Mentioned in Creativity, Inc and exemplified in the Frozen II documentary Into the Unknown, Pixar and Disney Animation use “dailies” to demo work in progress. Each animator shares their progress every day on the five seconds of film they’re responsible for.
Outlined in Ken Kocienda’s book Creative Selection, Apple’s clandestine “Project Purple” that made the iPhone embraced frequent demos when creating iOS, but at the speed at which they were working “hallway demos” would happen hours or minutes after a previous demo.
A core part of Design Sprints is getting a functioning prototype in front of users so your team can prove and vet an idea in a week rather than months.

Or as IDEO famously put it…

A prototype is worth a thousand meetings
— IDEO

Demos improve meetings. I’ve found “Demo First” meetings are life-giving because they start with something tangible, as opposed to discussing some hypothetical future scenario until time runs out and you have to schedule more meetings. Start meetings by showing progress. Better yet, a demo doesn’t always need to be a call or a meeting; thirty second screencasts are as good as gold.

Demos improve workflows. Breaking up large tasks into “what can I demo next” is an exciting way to work. There’s always an immediate goal for me to find a demo-able checkpoint where I can get tactical feedback frequently. It can save a lot of rework and we can catch ourselves going down a bad path early.

Demos improve project scoping. Demos and prototypes give you a good idea of what’s easy and what’s hard in the underlying system. Demoing often means you and others may be able to spot problems far off or find “fast paths” mid-flight. Often slight corrections or adjustments to the design can save weeks or months of work without sacrificing quality or user experience.

If I’m honest, “Dailies” are probably overkill, but I wouldn’t hate it. I would certainly prefer daily demos over vague, ritualistic standup-speak. It’s worth noting here that not all days or weeks are bangers. What’s important is establishing an organizational practice of demo’ing and honing your skills and confidence at providing demos.

The point is, do whatever is a right fit for your organization but never wait too long to demo. Allow room for ad hoc “hallway” demos to happen. And move the needle closer to daily.