Escalation Speed is how fast being stuck turns into a question someone else can actually answer. In a shared office, this barely registers as a skill — a stuck moment gets resolved in the time it takes to lean over and ask. Distributed, the same delay can cost a full working day, because the person who could answer is asleep by the time the question finally gets asked.
The Cost That Only Shows Up Distributed
Being stuck for twenty minutes is nearly free in a shared room — the fix is a few steps away. Across time zones, the same twenty minutes of silent stuckness can become a full day of lost time if the question that would have unblocked it does not get asked before the relevant colleague's working hours end.
That is what makes escalation speed a distinct, distributed-specific habit rather than a general trait of asking for help — the skill is not willingness to ask, it's the speed of turning stuck into something asked in time to matter.
What Low Escalation Speed Looks Like
It rarely looks like stubborn independence. More often it looks like a stuck moment that sits for hours while the person waits for a natural pause to raise it, tries a few more things alone first, or drafts a question and doesn't quite send it — not refusal to ask, just a delay in the turn from stuck to asked.
That delay is invisible from outside until the window it cost becomes obvious — a day slips, and in hindsight the blocker had been sitting, answerable, since the previous afternoon.
Speed Is Not the Same as Skipping the Attempt
High escalation speed does not mean escalating immediately on first contact with a problem — trying a reasonable first pass alone is still worthwhile. The habit is about not letting that first pass turn into an open-ended, unbounded attempt that quietly eats the window during which someone else could have answered.
The useful version sets an implicit limit on the independent attempt, and turns to a written question the moment that limit is reached, rather than when it feels comfortable to ask.
Reading an Escalation Speed Score in Context
Escalation Speed pairs naturally with Timezone Coordination — both concern the cost of delay across time zones, one from the asker's side and one from the planner's side. A low score on both together points at the same underlying blind spot: not accounting for how long a message takes to reach someone in a different working day.
The Distributed Work Habits test scores Escalation Speed out of twelve chances, one of four independently reported facets, so a low result here reads as a specific, coachable pattern rather than a verdict on someone's independence.