The three signals

Detection is triangulated, not single-metric.

Three independent behavioral indicators, each on a distinct operational dimension. One signal is noise. Three signals moving together is the pattern.

SIGNAL 01+18% OVER BASELINE

Response latency

Time between request and response across functions — Engineering ↔ Product, and beyond. Rising latency is coordination friction: teams talking more and deciding less.

Measures
Cross-functional response and handoff timing
Early signal of
Bottlenecks, unclear process, escalation patterns
Example
4.2h → 4.96h · +18%
Typical onset
Days 7–14 of drift
Response latency · 70-day trace
BASELINE 4.2h
SIGNAL 02+85% ESCALATIONS

Dependency concentration

How many critical conversations and decisions flow through a small number of people. When those people leave or become unavailable, execution stalls.

Measures
Coordination-load distribution across the org graph
Early signal of
Bus-factor risk, knowledge silos, unsustainable load
Example
11 of 340 ICs · 62% of load
Typical onset
Days 7–21 of drift
Coordination graph · hot nodes highlighted
CRITICAL NODE HOT EDGE
SIGNAL 03+27% CYCLE TIME

Cycle-time drift

Sprint velocity, rework frequency, completion consistency. Degrading delivery metrics surface here two to three weeks before KPIs flag them.

Measures
Cycle time, rework events, sprint consistency
Early signal of
Rework loops, quality issues, rising complexity
Example
5.6d → 7.1d · rework +147%
Typical onset
Days 14–28 of drift
Cycle time per sprint · 12 weeks
BASELINE 5.6d
When signals converge

One signal is noise. Three is certainty.

All three moving together — persistent and increasing — is the escalation criterion. The composite drift score crosses its threshold only when the dimensions align.

+18%
Response latency
+85%
Dependency concentration
+27%
Cycle-time drift
71 composite drift score · threshold 62 · crossed over 24 days
ELEVATED · 94% CONFIDENCE
How detection works

Non-invasive. Metadata only.

Message timing, meeting frequency, ticket cycles, response patterns. The behavioral shape of work — never its content.

Observed · metadata
Message and response timing
Meeting frequency and density
Cross-team handoff timing
Cycle time, rework, escalation frequency
Never observed
Message content or chat bodies
Documents, files, or attachments
Calendar text or email bodies
PII or identifiable communication content