Execution Queue Control

Control how much work your team takes on at once.

Execution Queue Control

What this fixes

Every new request gets accepted, so the team keeps starting work but rarely finishes it. The hidden cost is that every new “yes” quietly delays something already in progress - each new thing you start takes attention away from everything else. This activity makes that trade-off visible, and helps the team limit how much work it takes on at once so work gets finished instead of just started.

How this works

Imagine your team already has ten things in progress. A stakeholder arrives with “one quick request.” Someone says yes. Nothing gets cancelled - but everything else slows down. That’s the moment this tool is built for.

As a team, you count what you’ve actually started but not finished. You set a deliberate limit on how many things can be in progress at once - fewer than the team is used to. Then you agree one rule: new work only starts when something finishes. The limit makes the cost of “yes” visible now, instead of weeks later when everything is late.

The real shift is this: the queue already exists. You’re only deciding whether it’s visible or hidden. Most teams run an invisible queue - work piling up inside half-finished tasks - and feel busy all day while little gets finished. This makes the queue visible, so the team can control it.

Time required

Team ✓ · About 25–30 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 must read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

Use it when more work is entering than your team can clear.

Good signs it’s the right tool:

  • the team starts lots of things but finishes few
  • new requests keep cutting in
  • everything is “in progress” and nothing is done
  • delivery slows even though no one is idle

What you get

  • A clear count of what’s actually in progress
  • A work-in-progress limit - how many things the team works on at once
  • One intake rule for when new work is allowed to start

You’ve done it well when: the team agrees a limit and a rule - and starts finishing work before pulling in more.

What you’ll notice

  • The team starts less - but finishes much more
  • Saying “yes” now means choosing what waits
  • Less switching between half-done things

Why this works

Starting work feels productive. Finishing work creates value. When too many things compete for the same attention, everything slows down. Limiting work in progress forces the team to finish before starting something new.

What you need

Your current work in progress. Everything the team has started and not finished - from the board, tracker or what the team knows. This is the critical ingredient, and the hardest thing for teams to count honestly.

A board or wall. Room to lay out what’s in progress, side by side.

Sticky notes and a marker. One note per piece of work in progress.

Roles - Team: a facilitator (counts the work in progress, holds the limit, enforces the intake rule) and participants (list the work, set the limit, agree what waits).

Steps

  1. List what’s in progress (4–5 min). Every piece of work the team has started and not finished. One note each. Put them all up.
  2. Count it (3 min). How many things are in progress right now? It’s usually more than anyone expected.
  3. Set a limit (5 min). Agree how many things the team will allow in progress at once - deliberately fewer than the current count.
  4. Agree the intake rule (4–5 min). New work only starts when something finishes and frees a slot. Write the rule down.
  5. Decide what gives (6–7 min). You’re over the limit now. Agree what to finish first, and what waits until a slot opens. Don’t try to squeeze everything inside the limit - something has to wait.
  6. Make it visible (3–4 min). Put the limit and the rule where the team will see them when the next request arrives.

Output / Takeaways

  • A work-in-progress limit the team agreed
  • One intake rule - new work starts only when a slot frees
  • What’s being finished first, and what waits

Important rules

  • Finish before you start - a freed slot pulls the next thing. This is the whole tool
  • Set the limit lower than you think you need - the limit is the point
  • New work waits until a slot frees - no exceptions as a rule
  • Keep the limit visible - it only works if the team sees it

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

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