"Good at remote work" gets treated as a single trait, the way "team player" does — a vague compliment that describes almost nothing. The Distributed Work Habits test breaks it into four separately scored habits: Async Handover, Self-Visibility, Escalation Speed and Timezone Coordination. It then does something most tests don't: it refuses to add those four numbers into one score, because doing so would hide more than it reveals.
Async Handover: Writing That Survives Your Absence
Async Handover is whether your writing survives your absence — whether a document, ticket or message you leave behind gives the next person what they need without you there to fill in the gaps live. It is the habit distributed teams depend on most and notice the absence of last, usually right when someone is on leave and a project stalls waiting for a question only they could have answered.
It is not the same as writing a lot. A long handover that buries the one decision someone actually needs is a worse handover than three clear sentences that state it plainly.
Self-Visibility: Being Legible Without Being Asked
Self-Visibility is whether people can tell what you're doing without asking. On a distributed team, silence is genuinely ambiguous — it can mean deep focus, it can mean stuck, it can mean gone for the day, and nobody can tell which from the outside unless the person makes it visible themselves.
This is the habit most sensitive to overcorrection. Constant status updates are their own failure mode — they read as noise rather than visibility, and can crowd out the moments that actually need flagging.
Escalation Speed: Turning Stuck Into a Resolvable Question
Escalation Speed is how fast being stuck turns into a question someone else can actually answer. On a co-located team, being stuck for twenty minutes barely registers — someone taps a shoulder. Across time zones, the same twenty minutes of silent stuckness can cost a full working day if it is not turned into a written, answerable question before the window closes.
Low escalation speed rarely looks like an unwillingness to ask for help. More often it looks like waiting for a good moment to ask that keeps not arriving, while the actual blocker sits untouched.
Timezone Coordination: Planning Around Other People's Clocks
Timezone Coordination is whether you plan around other people's working hours rather than your own by default. It shows up in small, repeated choices — when a meeting gets proposed, how a message is timed, whether a request accounts for the fact that the person receiving it may not see it for another eight hours.
It is the habit most likely to be invisible to the person doing it well, because getting it right just looks like things going smoothly, and invisible to the person doing it poorly, because a missed handoff usually gets blamed on the other three habits instead.
Why There Is No Total Score
Most of the thirty pairs in this test trade one habit against another — choosing the statement that reflects strong Async Handover often means giving up a statement that would have counted toward Self-Visibility. That is deliberate: it is what makes the pairs informative instead of something everyone agrees with. But it also means the four numbers are not independent, and adding them into a single score would mostly reflect how the pairs were built, not the person answering.
The Distributed Work Habits test reports four bands instead, each out of twelve, plus a note if the familiarity block suggests the answers were generous rather than accurate. Read the low band, not the average — that is where the actual conversation is.