Cross-functional sync

Three teams, twelve commitments, one owner each. Thomas knows whose silence is normal and whose is a problem.

Tuesday standup · agent_log12 items
Eng
Ship /transcripts API
Pieter · 72h silent · escalating
Fri
Design
Hand off settings specs
Mariska · 72h silent · normal pattern, holding
Wed
PM
Confirm beta cohort
Lotte · replied Tue · on track
Today
Eng
Webhook retry patch
Tomas · in review
Mon
01

The judgment

Both Pieter on Eng and Mariska on Design went 72 hours without replying to Tuesday's standup commitments. A flat-timer agent would escalate both. Thomas read each owner's reply pattern from prior projects: Pieter typically responds within a day, Mariska answers in three-day batches with a longer note. Same silence, different read.

Thomas escalated Pieter, looped the eng lead in by Thursday morning. He held on Mariska, queued a soft check-in for Friday. Mariska sent her batch reply Thursday afternoon, on schedule for her. No false alarm, no missed real blocker.

"Pieter usually answers in a day. 72 hours is a flag. Mariska answers in three-day batches. 72 hours is normal. Escalated Pieter. Holding Mariska."
Illustrative · names and timing fictionalised · the behaviour is real
02

What changes

Before
  • Set a 48h reminder for every owner in the standup.
  • Either nagged everyone or missed the one who actually went dark.
  • Pinged the eng lead Monday about a blocker that started Wednesday.
After
  • One cadence per person, learned from their own reply history.
  • Escalation goes to the right person on the right day.
  • You see the timeline, not the chase. Thomas owns the work.
03

Try it

Hand Thomas your next standup. He will know who to chase, and when not to.