The day · Page 34
9:30, the build: first version, not final
[GIVE THIS TO THE ROOM · say it before the clock starts]
Today you build the first working version of a product, not the finished one. Its job is to put something in front of a real user at 15:30 that they can click and react to. For that it does not need accounts, payments, settings, or clean code. It needs one believable path through the idea.
For you only
Jake Knapp's Sprint book set the old expectation for what one day of building buys. In 2016, building was expensive, so his prototype day was openly about illusion: stitch together screens that look real from the front, like an Old West movie set, and test on that. Daniel Burka, who worked on sprints at Google Ventures, gave the quality target a name I still use: Goldilocks quality. Polished enough that a user believes it, rough enough that you finish today.
Vibe coding changed what the same day buys. Your teams are not stitching a facade. They are building a working early version of the product, live and clickable from the first prompt, something a 2016 sprint team would not have believed. The Goldilocks rule still holds, it just moved from realness to scope: build the slice of the product that proves the idea, and nothing more. Just enough product to learn from, and nothing anyone is too precious about to rebuild next week.
And expect every team to build something that works but confuses. That is normal. Earlier this year I audited a PM's vibe-coded tool. It worked. The screens were full of colourful buttons, the flow went nowhere, and as a first-time user I was completely lost. Shipping faster does not mean shipping good, and the user test this afternoon exists precisely to catch it.
Just because it works does not mean it is useful.