Protect the Critical Path

Protect the work that sets your deadline from urgent distractions.

Protect the Critical Path

What this fixes

You have a deadline, and a handful of things genuinely set it. But every week, something more urgent-feeling pulls people off that work - and the deadline quietly slips. Teams don’t miss deadlines because they can’t spot the critical work. They miss them because they keep sacrificing them to whatever seems most urgent. This names the work that paces delivery, protects it, and sets one rule for what yields when something new competes.

How this works

A release is scheduled for Friday. On Tuesday, two production support requests arrive, and a senior stakeholder asks for “just one small enhancement.” Engineers leave the release work to deal with the urgent requests. By Friday, the enhancement is finished-but the release slips by a week. The team didn’t miss the deadline because the work was difficult. It lost it because the work that determined the deadline wasn’t protected. Protect the Critical Path identifies that work in advance and creates one rule: unless new work changes the delivery date itself, it waits.

As a team, you find the few things that actually pace your deadline. You put them in a protected column - these cannot be interrupted - and put the work that can wait in a yield column. Then you agree on one yield rule for every future interruption: when new work arrives, it yields to the protected column unless it moves the deadline itself. That rule - decided in advance, before the pressure arrives - is what makes this protection and not just prioritisation.

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

Time required

Team ✓ · About 30–45 minutes, with a facilitator.

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

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

When to use

Use it before every major delivery cycle - when a real deadline meets competing demands.

Good signs it’s the right tool:

  • you’re heading into a delivery with a date that matters
  • everything feels like a priority and the same people are pulled between competing demands
  • the work that sets the finish date keeps getting bumped by “urgent” asks
  • you keep saying yes to interruptions and wondering why the deadline slips

What you get

  • A protection charter - what’s protected versus what yields
  • The pacing work, and the people on it, protected
  • One yield rule for when new work competes

You’ve done it well when: the team has a charter it will actually hold - and can say no to the next “urgent” ask without re-litigating it.

What you’ll notice

  • The deadline-setting work stops getting interrupted
  • “Urgent” asks have a clear answer - they wait
  • Less weekly re-prioritising; the rule already decided

Why this works

Urgent work naturally grabs attention, even when it doesn’t determine the delivery date. By deciding in advance what is protected and what must yield, the team avoids making the same priority decision again every time something urgent appears.

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.