← All chapters

The day · Page 33

9:15, the brief

For you only

The brief goes up at 9:15 and the whole slot is about fifteen minutes, questions included, because the clock starts at 9:30. Print it big and tape it where every team can see it from their table. You will point at it all day.

The shape of the fifteen minutes. Read the brief out loud, twice. Take it apart the way Chapter 13 takes apart the Zara brief: this is the user, this is her moment, this is the finish line, and notice what it does not say, because that part is yours. Then Q&A, then teams, then go.

Treat the Q&A as your last diagnostic. Clarifying questions about the user and the goal are healthy; answer them and move. "Build what, exactly?" at this stage means the one-person test got skipped, so tighten on the spot: restate the user, the moment, and the finish line, and start the clock. No questions at all is often the opposite problem, a brief so tight there is nothing left to ask.

Forming teams. Announce the pairs you planned (Chapter 8), cheerfully, as a done thing. Silly team names, thirty seconds, non-negotiable in a friendly way. It sounds like a warm-up game. It is actually the first act of ownership: a pair that has named itself has started being a team, and the name gives the scoreboard a place to live at 16:50.

Setting psychological safety, on purpose. Google spent two years studying what made its own teams work, a project called Aristotle, and the single strongest factor was not seniority or talent density. It was psychological safety, Amy Edmondson's term for a shared belief that the team is safe for interpersonal risk-taking. A build day asks non-coders to build software in public and show it to leadership the same afternoon. That is interpersonal risk all the way down, so you set the belief out loud at 9:15 ("everything is a draft, nothing is wrong yet") and then you prove it by how you greet the first weird idea of the morning. The room watches what you do with the first person who sticks their neck out. Greet it with curiosity, and you have safety. Wince once, and you have eight careful, boring prototypes.

At 9:30, point at the wall, start the clock, and say the six words: "See you at half past three."

Sources: Google re:Work, Project Aristotle, 2016 · Amy Edmondson, "Psychological Safety and Learning Behavior in Work Teams", Administrative Science Quarterly, 1999 · Charles Duhigg, "What Google Learned From Its Quest to Build the Perfect Team", The New York Times, 2016.