Frequently Asked Questions
How long does the Distributed Work Habits test take?
About 8 minutes for 38 questions. Thirty of them are pairs of statements where you pick the one more like you, and the last eight ask whether you have used a specific way of working. At the end you get four habit bands — Async Handover, Self-Visibility, Escalation Speed and Timezone Coordination — with the count behind each one.
What do the bands mean?
Each habit is on offer in exactly twelve of the thirty pairs, so each is scored out of twelve. Choosing it 0-4 times reads as "seldom your first move", 5-7 as "mixed", 8-10 as "usually your first move", and 11-12 as "nearly always your first move". The band is defined on the raw count, not on a percentage, and the count is shown next to it so you can see what produced the label.
Does the result say whether I am suited to remote work?
No, and it will not say it in either direction. There is no norming sample behind this instrument and no study linking these four habits to remote-work outcomes, so nothing here is reported as a percentile and no line of the result tells anyone they are or are not cut out for it. What you get is a description of which habits you reach for first, which is a different and more modest claim.
What happens if I skip a question?
The habit that question belonged to comes back with no result rather than a low one. A facet needs all twelve of its pairs answered; if even one is missing, that facet is reported as unscored instead of being rescaled from the pairs you did answer. Rescaling nine answers up to a twelve-point band is how a half-finished sitting turns into a confident number that nobody can spot afterwards.
How is this different from the Remote Work Style test?
Remote Work Style asks what you prefer — async or synchronous, solo or team, structured or flexible, deep or multitasking — and returns a style, with no better or worse end. This one asks what you actually do when the two options are both defensible, and it scores four specific behaviours whose cost goes up when the team is spread out. Preferences and habits often disagree, which is the point of taking both.
My whole team is in one timezone. Does Timezone Coordination still apply?
The items are about planning around other people's clocks — sending early enough for someone else's morning, confirming a time in both directions, protecting the hours you overlap. If your team shares a working day you get fewer chances to practise that, so a low band there is telling you less about you than the other three are. Read it as context, not as a gap to fix.