Team Signal

8 members · 30-day window · updated 4m ago

This week's move· Move on this on conflict surface rate

Schedule disagreement instead of hoping it surfaces.

Add a 20-minute 'red team' slot to one weekly meeting. Assign someone to argue against the current direction. Healthy teams don't have less conflict — they have earlier conflict.

Watch next cycle: Number of explicit disagreements logged in meetings. Zero is not healthy — it's suppression.

Receipts
What changed since you committed.

No commitments yet. The first one starts the receipt — a week from now you'll see whether the signal moved.

Pattern worth naming

Response latency and conflict surface are moving together. In the data, that pairing precedes a departure within ~60 days about 1 in 3 times. The move above is the highest-leverage response — not a guarantee, just the best lever you own.

The signals behind it

Tap any to open its move
+ 2 dimensions holding steady

Signal Feed

LAST 14 DAYS · 7 PATTERNS
  • TUE · 9:47AM
    response latency

    Over the last 14 days, Jordan has not responded to any thread initiated by Marcus. Pattern spans 7 conversations across #atlas-platform and DMs.

  • MON · 8:12PM
    decision velocity

    The Q3 roadmap decision (owner: Maya) has been open 19 days with no resolution. Team average is 4 days. The Notion doc has been reopened 11 times.

  • SUN LATE
    participation balance

    Leo's async participation has dropped 62% since the Atlas all-hands on Sept 3. No PTO is on record in Rippling for this period.

  • FRI 10/10 · 11PM
    feedback tone

    Maya's 1:1 messages to Leo have grown from 84 to 312 words on average over 6 weeks. Directive verbs down 41%; hedging phrases up 3.1×.

  • WED OCT 8
    conflict surface

    Iris, Sam, and Leo have each cut async participation by 40%+ since the Atlas all-hands on Sept 3. No disagreement was logged in that meeting.

  • 10/4 · EARLY
    response latency

    Cross-functional reply latency with the Design pod has grown 1.8× over 21 days. The loop appears to be routing through Priya rather than Leo.

  • SAT SEPT 28
    decision velocity

    Eight decisions opened by Tariq's pod last sprint; two closed. Unresolved-decision backlog in Linear is the highest since June.

Team Map

COMMUNICATION DENSITY · 30D
MCMAYAJRJORDANMBMARCUSPSPRIYALPLEOSOSAMIVIRISTHTARIQ
Hover a node to inspect.
active channel
broken / suppressed
isolation alarm
This is a simulation

Connect your real team and the move on this page becomes the move on your team.

Use your real team →
Interpreter
Ask the signal

A grounded interpretation of the signals on screen. Cites patterns, not opinions.