2. The day building got cheap

§ 2.1Two days, four people, two products#

§In 2026 a multi-brand hospitality group, more than twenty brands, ran a discovery sprint on a customer product. Ten people were in the room. Four of them built, and none had ever prototyped anything. None was a designer. None was a developer.

§They had a requirements document written to be uploaded rather than read: named personas, business rules the team had already decided, and a paste-ready set of plausible content, real dish names, real prices in local format, real-sounding customer names. They had a pack of eleven numbered prompts. They had two off-the-shelf AI tools, one to think and design with, one to make the result navigable on a phone.

§By the end of the second working day, both teams had a product a stranger could tap through on a phone with nobody explaining anything. That was the bar. Both cleared it.

§ 2.2A hundred comments, none about design#

§On demo day, each prototype was walked through once. Everyone wrote comments on a board, one per note, and the notes were sorted into two piles: design and scope.

§The design pile said clean, simple, premium, and nothing else. Every substantive comment was about scope. Whether the loyalty unit was money or something else. Whether check-in was a scan or something else. Whether one program could serve more than twenty brands. Six decisions were left open and written down, each with an owner.

§This is the first thing that changes when building gets cheap. Fidelity stops being the conversation. Teams that used to spend demo day on visual taste spend it on what the product should do, which is the argument they always needed and rarely got, because the prototype used to be too rough to argue about anything except the prototype.

§ 2.3What the field said#

§Twelve people who owed the team nothing used the prototypes over three afternoons: six customers, six operations staff. Two people per interview, a moderator who spoke and a note-taker who did not. Tasks were given as situations, never as instructions, in the manner the third whitepaper describes.

§Six of six customers did not understand the loyalty unit. Six of six failed the check-in gesture; one said she would rather close the app. Four of six thought a section labeled My card stored credit cards. Five of six loved reservations, especially seeing the group's other restaurants when there was no table. Five of six operations staff named the customer profile card as the most valuable thing they saw. Nobody needed to be paid for their information; they filled it in gladly, because they understood it would get them served better.

§ 2.4The decision nobody in the room made#

§The team entered the sprint with payments as pain number one. It left proposing to leave payments out of the first version. The memo proposed two acts: first the customer builds a profile and sees her tier, nothing else, because it depends on no one and ships in weeks; then the operation reads that profile before serving, in one restaurant, read-only, because the operation had asked for exactly that in five of six interviews. Payments later, not discarded, because it needed the check-in that failed six of six.

§Nobody in the room decided that. Twelve people outside it did, and the room let them.

§ 2.5Why one case, in numbers#

§This essay uses one engagement, told in numbers rather than as a walkthrough, because it happens to make every stage of the collection visible at once: research that found who tried before, conversations about behavior, a prototype as a question, strangers who broke it, a position that excluded, a business assumption that turned out false, and a decision that let evidence beat the vote. The chapters that follow read those stages back through the six whitepapers, and this sprint is the thread they are strung on.