SG-03
Worklog Signal — Multi-Person Handoff Pattern
Signal Chart
Default severity: medium
ProcessMetricsQualityEffort
What it detects
Worklog entries on a single issue were made by more than the configured number of distinct authors across the issue\'s active lifetime — indicating multiple handoffs. Handoffs increase context-switching cost and are a major hidden source of cycle time inflation. worklog_authors = DISTINCT(worklog.author, issue=I)
Detection formula
IF COUNT(worklog_authors) >= config.sg.handoff_author_threshold // default: 3 distinct authors THEN FLAG multi_handoff compute handoff_dates = dates where author changed between consecutive entries FOR each_handoff: record days_idle_at_handoff (gap between last entry by prev author and first by next) IF AVG(days_idle_at_handoff) > config.sg.handoff_idle_threshold // default: 3d THEN CRITICAL (significant idle time at each handoff)Examples in practice
- A team shows worklog entries on a single issue were made by more than the configured number of distinct authors across the issue\'s active lifetime while handoff author threshold is set to 3 distinct authors.
- Example signal: Worklog entries on a single issue were made by more than the configured number of distinct authors across the issue\'s active lifetime — indicating multiple handoffs.
Suggested response
Use worklog shape (gaps, bursts, handoffs) to coach sustainable pacing and clarity.
Coaching playbook
Symptom
Worklog entries on a single issue were made by more than the configured number of distinct authors across the issue\'s active lifetime — indicating multiple handoffs. Handoffs increase context-switching cost and are a major hidden source of cycle time inflation. worklog_authors = DISTINCT(worklog.author, issue=I)
Why it matters
When "Worklog Signal — Multi-Person Handoff Pattern" keeps appearing, the team is signalling a repeatable process gap. Left unexamined, the pattern hides where work really stalls and makes improvement metrics harder to trust.
What you can achieve
Use worklog shape (gaps, bursts, handoffs) to coach sustainable pacing and clarity.
Facilitation questions
- What system change would stop "Worklog Signal — Multi-Person Handoff Pattern" from firing again?
- What do the cited issues have in common — same root cause or same workaround?
- Who owns the two-week experiment and how will we verify on the next import?
Run this rule against your own tracker data with Flow Analyzer.