Avium SignalsTeam tier and above

Hand-off Cost — the hidden tax in your assignee changes

A ticket assigned to one person ships fast. A ticket that's been reassigned three times takes 4× longer and reopens 2× as often. Avium counts every hand-off.

Avium SignalsWorkflow / Ping-Pong
Work isn’t a straight line — Avium counts the backward hops that quietly burn the sprint.
↺ 9× reworkTo DoIn ProgressIn ReviewDone

The invisible tax

Every time a ticket changes assignee, three things happen: the new person has to load the context, something gets lost in translation, and the calendar quietly advances. Two hand-offs is usually fine. Three is a smell. Five is a guarantee the ticket will be slow AND wrong.

Nobody tracks this. Jira shows assignee changes in the history view, one ticket at a time. Nobody aggregates. So a process problem that's visible in the data goes invisible in practice.

How teams try to spot hand-off problems

Mostly they don't:

  • Watching for tickets that 'feel hard' — every reassignment feels reasonable in isolation; the pattern only emerges in aggregate.
  • Tracking 'specialty mismatch' — assuming hand-offs are because the wrong person got it first. Sometimes true, often a process issue.
  • Calling them 'pickups' instead of hand-offs — semantic dodge, same problem.
  • Asking the engineer who finally finished the ticket — they're the wrong person to ask; they only saw one leg of the relay.

How Avium Signals computes hand-off cost

Avium reads the ticket field change history and counts assignee transitions per ticket.

  • Hand-offs: number of times the assignee field changed during the ticket's lifecycle. 0 = same person start to finish; 4+ = problematic.
  • Hand-off rate: average hand-offs per ticket across a window. Trends matter more than absolutes — a team that climbs from 1.2 to 2.5 is degrading even if no individual ticket looks bad.
  • Correlation with cycle time + reopen rate: Avium internal models show >2 hand-offs roughly doubles average cycle time and increases reopen risk by ~80%. Visible on the Signal card.
  • Per-ticket detail: the high-cost tickets, the people involved, and which transitions happened mid-sprint vs at planning.

Who reads this Signal

Scrum masters
When your team complains 'work keeps moving around,' this is the number that names the pattern.
Agile coaches
Hand-off cost is one of the top three leading indicators of cycle-time pain. Show the trend, then coach the team to either reduce specialization or improve the hand-off protocol.
Engineering managers
Identifies the engineers who are picking up reassigned work disproportionately. Often the most senior; often the most under-credited. 1:1 input.
VPs of engineering
Hand-off cost climbing across an org usually means the work-allocation model has broken down. Surfaces a structural pattern before it shows up in attrition data.

See your team's hand-off cost

Avium reads your work management tool's assignee change history (Jira today, more integrations on the way) and surfaces hand-off cost on connection. Trend tracking + per-team rollup on Team; AI Briefing narrative on Business.

Start free — no credit card →

Related Avium Signals