The day · Page 57
16:50, the decision
For you only
This is the difference between a fun day and a day that changes what the company does. Without the decision, it was just a workshop.
The sponsor watched the pitches, saw what real users did, and now makes the call in the room: go, iterate, or no-go. Go: the winner moves forward, with an owner and a date. Iterate: a list of changes and a second test, scheduled now. No-go: kill it, and write down why, because a documented dead end is worth real money the next time someone has the same idea.
No follow-up alignment meeting. No deck sent around for three weeks. The people who needed to say yes were there, and they said it.
Two moves from Amazon's playbook help when the room hesitates. First, remind everyone which kind of decision this is. In Jeff Bezos's framing: most decisions are two-way doors, reversible, and should be made quickly; treating every call like a one-way door is how companies get slow. A build day decision is a two-way door by construction, the prototype cost a day. Second, when a judge disagrees with the direction the sponsor picks, the phrase that keeps the room honest is Bezos's "disagree and commit": say your disagreement out loud, once, properly, then commit to the direction without relitigating it in the corridor. It is not surrender. It is how a team disagrees and still ships.
[SAY SOMETHING LIKE · handing the moment to the sponsor] "You have seen four prototypes and what five real users did with them. The rubric says team three is ahead. The call is yours: go, iterate, or no-go, and whichever it is, we write it on one page with an owner and a date before anyone leaves."
If the sponsor reaches for "let's discuss it next week", do not argue. Shrink it: "what would you need to see to decide today?" Nine times out of ten the answer is small and one of the teams already has it on a screen.
A decision made in hours is more honest than an opinion held for months.