FAQ, sources, licence · Page 79
FAQ (2 of 2)
Can we run it remotely? It works best with everyone in one room. The energy, the pairing, and the same-day user test are all easier in person, even though the build tools themselves run in any browser. If remote is the only way your team exists, run it remotely rather than not at all: video on, pairs in breakout rooms, users tested over screen-share. Expect to work harder for the energy, and expect the decision to need extra protection from "let's discuss async".
Is one day really enough for user testing? For reactions, yes, and be honest that reactions are what you get. Five users surface most usability problems, per Nielsen Norman Group's research, and a reaction from a real stranger beats another opinion in the room every time. If your company needs longer sessions, split the format: build on day one, test and decide on day two. Same shape, more air.
What if the users cannot come? Run the day anyway, for alignment, and test within days. A build day with no test is still worth running once. A build day habit with no testing habit is theatre; do not let it become the norm.
What does it cost? Close to nothing in money: a room, snacks, and a tool subscription or a day of credits. The real cost is one day of eight people's time, and the honest comparison is what the alternative costs: the average stuck decision eats that much time in meetings inside two weeks, and delivers no prototype and no user contact at the end.
What do we walk out with? Up to four tested prototypes, real user reactions, a decision made by someone with authority, one page that records it, and a room of people who now know they can build. The last one is the sleeper. It changes random Tuesdays for months.
Where do I start? Write one challenge for your own product in the user, context, goal shape. Aim for 31 words. Read it to one colleague; if they start describing what they would build, pitch the day to your manager this week. Chapter 7 has the script.