← All chapters

After the day · Page 60

The week after

For you only

Three moves keep the day alive. All three are yours, because the facilitator's job outlasts the room by about a week.

Send the decision doc within 24 hours, while the room still remembers. One page: the decision, the owner, the date. You photographed it before people left; now it goes to everyone who was in the room, plus the sponsor's boss if the sponsor agrees. If leadership went quiet after the room, send it anyway with a date next to each decision and ask for a yes or no by reply. Silence feeds on vagueness. Dates starve it.

Give the winning team a real next step, not a trophy and silence. Even a small one. The point of the day was to ship, so ship something on Monday: the iterate list goes into the tracker, the second user test gets a calendar date, the go direction gets its first real task. If the day produced more than one go, do not start all of them. Pick the one with the clearest user signal and ship that. Two half-started follow-ups die faster than one whole one.

Tell the story inside the company. Write up what happened and what you learned, with screenshots of the prototypes and one line about what the users did. Put your name on the room you ran. This is how you get invited to run the next one, and how leadership starts seeing you as the person who ships. The wrap-up post skeleton is in Appendix B, and it takes twenty minutes while the photos are still on your phone.

And if it worked, tell me too. I collect these stories and I share them, with credit to you. You ran it, you get the credit.

Sources: "How a Product Build Day runs", productbuildday.com/resources, 2026.