How do you run a standup thumb check when the team isn't in a room?

What the thumb check is

At the end of standup, someone asks the question — usually about confidence in the sprint goal — and everyone responds at once with a hand.

• Thumbs up: good, clear on what I'm doing, no blockers.
• Thumbs sideways: unsure, or minor concerns worth watching.
• Thumbs down: blocked, overwhelmed, or at real risk of missing the goal.

It takes under thirty seconds and requires nothing. Its virtues are worth naming precisely, because they're what any remote version has to preserve.

It's fast enough not to be a ritual. Nobody resents thirty seconds.

It's safe for quiet people. This is the underrated one. In a standup round, saying "I'm worried about the sprint" out loud requires a level of confidence and social capital that not everyone has, particularly if they're new or junior. Holding a thumb sideways requires neither.

It's a trigger, not a report. The sideways thumb doesn't explain anything. It says ask me after, which is exactly the right amount of information for thirty seconds.

What breaks remotely

Simultaneity — the one that quietly ruins it

In a room, everyone's hand goes up at the same moment. That's not incidental. It's the same mechanism that makes planning poker work: cards are revealed simultaneously so the first answer can't anchor everyone else's.

On a video call, this collapses. Some cameras are off. Some people are on a phone. Thumbs appear over three or four seconds, and the people slower to respond have now seen two thumbs up before deciding. Nobody is being dishonest — anchoring doesn't require dishonesty. The result is a check that reads as consensus when it's partly an echo.

The Slack-emoji version of this is worse, because responses arrive over minutes and are permanently visible as they accumulate.

No record

A thumb check evaporates. Nobody writes it down, so there's no way to answer the genuinely useful question: is this better or worse than a fortnight ago?

Slow drift is invisible without a record. A team going from all-up to mostly-sideways over five weeks experiences five ordinary standups. There was never a day where things noticeably changed.

No reach

The signal stays in the room. That was fine when the room contained everyone who needed it — but it means a leader responsible for a dozen teams gets nothing, and the teams depending on this one get nothing either.

And the standup itself splits

The practice also has a scale limit. Three separate developers in our research described the same thing:

"Fifteen members in our standup — it became too long, too big. We split it into three."

Once a standup splits into three, the thumb check reflects a third of the team, and the cross-team awareness that made it valuable is exactly what's been lost.

How to reproduce it asynchronously

The requirements follow from what broke.

• Ask each person privately. A prompt to the individual, not a thread everyone watches fill up. This restores the simultaneity property — not by making responses arrive at the same moment, but by making the order irrelevant, since nobody sees the others.
• Keep it to one action. One click. Adding a mandatory comment turns a thirty-second practice into a status report, which is the thing you were trying to avoid.
• Record it. The comparison with previous weeks is the part the in-person version could never provide, and it's free once responses are collected in a system.
• Use more than three options. Up, sideways and down is coarse. On a one-to-five scale, a shift from 4 to 3 registers movement that would otherwise have to wait until someone was ready to turn a thumb sideways — a bigger, more public step.
• Let it travel. The team should see their own pattern; the people depending on the team should be able to see the signal too.

What you lose, honestly

The asynchronous version gives up something real: the moment. In a room, a sideways thumb is visible to everyone including the person's colleagues, and often prompts an immediate "what's up?" from a teammate rather than from a manager. That immediacy is genuinely valuable and doesn't survive the translation.

The trade is that you gain a record, reach beyond the room, and protection against anchoring. For a co-located team of six that still fits in one standup, the in-person thumb check may well be better and you should keep doing it. The case for the asynchronous version gets stronger the more distributed the team, the larger it is, and the more people outside it depend on its work.

How Genchi does this

Genchi is close to a thumb check that persists. Each team member gets a prompt in Slack, email or the app at the cadence you set, asking a single question: how confident are you that we'll achieve our goal? One to five, one click, about two seconds.

Responses are private, so nobody's answer is anchored by anyone else's. They're aggregated and kept, so the team and their leadership can see the current reading, the spread of individual values, and the trend across recent check-ins. And the signal reaches beyond the standup — other teams and leadership see it without joining the call.