When a team argues: note-and-vote

For you only

Somewhere around late morning, one pair will hit a real fork: two ideas, both plausible, both half-argued, minutes burning. Your default move is the coaching question ("which one can the user test at 15:30?"). When that does not settle it, borrow the cleanest small-group decision tool I know: note-and-vote, from Jake Knapp and John Zeratsky, the Sprint authors.

The full version, for when a bigger group needs it:

1. Frame the question in one sentence, in writing.
2. Everyone writes their own answers, silently, a few minutes.
3. Answers go up where all can see them, without speeches.
4. Everyone votes, silently. Two or three dots each.
5. Brief debate only if the result is unclear.
6. One named decider makes the call, and may overrule the votes.

The silence is the design. Writing before talking means the quiet person's idea competes fairly with the loud person's, and voting before debating means the group commits in minutes instead of circling for an hour. Knapp built it to stop the loudest voice in the room winning by default, which is exactly the failure mode of a stuck pair at 11:40.

For a pair on a build day, the pocket version takes ninety seconds: both write their version of the next screen in one sentence, both read them out, and the decider calls it. Who is the decider? The teammate closest to the user in the brief. If that is genuinely unclear, whoever wrote the sticky-note assumption the fork hangs on. The point is not perfect fairness. The point is that a decision in ninety seconds beats a debate for forty minutes, and either idea can still be killed by a user at 15:30, so the stakes are exactly one afternoon.

You will also use note-and-vote at room scale: picking between two challenges in a scan-mode day, or breaking a judging tie (Chapter 25).

Sources: Jake Knapp and John Zeratsky, "Note-and-Vote", from the Sprint method, Google Ventures, 2016.