Interruption Cost Cut

Add up what interruptions really cost, then cut the worst sources.

Interruption Cost Cut

What this fixes

“My team’s always busy, always slow.” Interruptions each feel small and reasonable - a quick question, a ping, a two-minute favour - so no one adds them up. The real cost is invisible per interruption and only shows in aggregate, which is why a team can lose a startling amount of capacity without ever deciding to. This makes the cost undeniable, so you’re willing to cut the worst sources.

How this works

Example: an engineering team feels permanently busy, yet major features keep slipping. They count their interruptions for one typical week - Slack questions, production support, quick design clarifications, drop-ins, and unplanned meetings. The interruptions themselves don’t look serious, but when they add the recovery time after each one, they discover they’re losing almost two full person-days every week. Seeing that cost in terms of team capacity makes it obvious which interruptions have to change.

 

You count, fast, the interruptions in a typical week - by source, with how long each really takes to recover from (not the interruption itself, but getting back into the work). That gives a total. Then comes the real move: you translate the total out of minutes into capacity you recognise - a share of someone’s week, a sprint, more than your team meeting. ‘163 minutes’ means nothing; the same figure as a share of someone’s week changes the conversation. Then you cut the two worst sources.

The tally is the evidence. The translation is the point. Minutes don’t move people - capacity they recognise does.

Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part. (Works solo too.)

Time required

Solo ✓   Team ✓

About 20–30 minutes, with a facilitator for teams.

The facilitator should read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Bring one recent, typical week - when the team is always busy, but the important work keeps slipping, and interruptions feel like just part of the job.

Use it whenever:

  • the team is ‘always busy, always slow’ and nothing big gets finished
  • interruptions each seem reasonable, so no one questions them
  • there’s a sense that capacity ‘vanishes’ into pings and quick questions
  • you suspect the cost is real, but no one believes it’s big

What you get

  • A fast tally of your real interruption cost, by source
  • That cost translated into capacity you recognise - person-days, sprints
  • The top two sources cut, each with a concrete change and an owner

You’ve done it well when: someone says ‘that’s a whole person a week’ - and the team agrees to cut a source, not just note the number.

What you’ll notice

  • The cost is far bigger than anyone guessed
  • ‘Reasonable’ and ‘unaffordable’ aren’t opposites
  • A couple of sources account for most of the loss

Why this works

Interruptions are a cognitive blind spot: each one is individually trivial, so the brain never sums them - and the real cost isn’t the interruption; it’s the time to get back into deep work afterwards. Counting by source makes the aggregate visible; translating it out of minutes makes it felt. People don’t act on a minute’s figure; they act on the capacity they recognise.

What you need

A recent, typical week. One real week the team can recall - the interruptions must be real, not hypothetical.

One facilitator. They keep the count fast, drive the translation, and push the team to name cuts - not just admire the number.

The tally card. A simple card to log each interruption source, its weekly frequency, and its honest reload time.

The translation key. Converts the weekly minutes into capacity the team recognises - person-days, sprints, meetings. This is where the reveal happens.

Steps

  1. List the interruptions (5 min). Team: appoint a facilitator first. List the interruption sources from a typical week - pings, quick questions, drop-ins, unplanned meetings. Group similar ones.
  2. Count frequency and reload (6 min). For each source: how often a week, and how long to get properly back into the work. Tally the total minutes. Keep it fast.
  3. Translate (6 min). Convert the total out of minutes into something the team recognises - person-days, meetings, sprint capacity. That comparison is what makes the cost land.
  4. Cut the worst sources (8 min). Pick the top two by cost. For each: one concrete change, an owner, a start. Commit them.

Output / Takeaways

You leave with:

  • Your real interruption cost, by source
  • That cost as capacity you recognise - the number that changes minds
  • Two sources cut, each with a change and an owner

Important rules

  • Count by source, not incident - you cut sources, not individual pings
  • Let the team set the reload time - never lead with a multiplier
  • Translate out of minutes - the meaning is the reveal, not the total
  • End with a cut and an owner - not just an awareness of the number

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.