Attention Boundary System

Protect your focus before it gets interrupted.

Attention Boundary System

What this fixes 

A “quick question” costs two minutes - but getting back into the work costs more. Across a day, that getting-back-in time quietly reduces your focus time. Most people blame the interruption. The real cost is the recovery: the interruption wasn’t expensive - getting back into the work was. This activity makes that cost visible, then proves that a boundary - not switching faster - is what protects the work. 

How this works

You’re finally making progress on a difficult design document. A Slack message arrives. Two minutes later, you’re back - but it takes another five minutes before you’re thinking clearly about the document again. That second five minutes is the hidden cost, and it happens every time. 

So you run two short work blocks on a real task. In the first, you just notice: every time something pulls you away, you make a tally mark and note how long it took to get back in. You add it up and see the true cost. Then you set one boundary and run a second block - same kind of work, but the interruptions mostly don’t get through. The difference between the two blocks is the whole point: you feel the cost, then watch a boundary stop it. 

No special kit: all you need is a real task, a timer, and something to tally on - paper or a notes app. 

Time required

About 60 minutes: two blocks of around 25 minutes, with a short look at your tally in between. You can also split it across two days - block 1 one morning, block 2 the next - as long as the work is the same kind. 

The time required is indicative and will depend on the nature of the problem. 

When to use

Bring a real piece of focused work you actually have to do - not a made-up task. Use it whenever: 

  • you keep losing focus time to interruptions and “quick” asks 
  • you feel busy all day but your real work doesn’t move 
  • you’re about to start a stretch of work that genuinely needs protecting 
  • you want to know what an interruption really costs you 

What you get

  • A real measure of what an interruption costs you - including the time to get back in 
  • One boundary you’ve proven protects your work 
  • A short list of boundaries to set before your next focus block 

You’ve done it well when: you’ve seen the cost in your own tally, set a boundary, felt the second block go differently, and can name a few boundaries you’ll actually use. 

What you’ll notice

  • An interruption costs far more than its surface time 
  • Most of the cost is getting back into the work, not the interruption itself 
  • The interruption was never the problem - the missing boundary was 

Why this works

Every interruption creates a cost: getting back into the work takes longer than the interruption itself. Boundaries work because they stop the interruption from landing in the first place. The activity proves it by comparison - the same kind of work, with and without a boundary. You don’t read about the cost of interruption; you measure your own. 

What you need

A real delivery with a deadline and competing demands on the same people. If nothing is competing for attention, there’s nothing to protect. The tool only works on a live delivery under pressure, not a hypothetical. 

A board or wall. Space for two columns - protected and yields - side by side. 

Sticky notes and a marker. One note per piece of work or demand. 

Roles - Team: a facilitator (runs the activity, holds the yield rule, keeps time) and participants (find the pacing work, sort protected versus yields, agree on the rule). 

Steps

  1. Name the deadline that matters (4–5 min).The one delivery you’re protecting and its date. 
  2. Find what paces it(7–9 min). Which few things actually set that date - the work that the finish waits on? Mark them. Keep it to a few; most work isn’t pacing. 
  3. Build the protected column (7–9 min).Put the pacing work there - and the people on it, and the time it needs. These cannot be interrupted. 
  4. Build the yields column (7–9 min). Anything that does not move the deadline - requests, meetings, nice-to-haves. That’s the test the whole tool turns on: if it doesn’t move the deadline, it yields. Be honest; yielded work is deferred, not killed. 
  5. Write the yield rule (5–6 min).One rule for next week’s “urgent” ask: it yields to the protected column unless it moves the deadline itself. Name who holds the line. 

Output / Takeaways

  • The protection charter - protected versus yields 
  • The yield rule, and who owns holding it 
  • A charter you keep visible where new requests arrive 

Important rules

  • Protect a few things, not many - if everything’s protected, nothing is 
  • Protect the people and time, not just the task 
  • New work yields unless it moves the deadline itself 
  • Keep the charter visible, and name who holds the line 

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

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