Subtraction Game

Remove complexity wherever it exists at work.

Subtraction Game

What this fixes

A process that once took two approvals now needs six. A quick meeting becomes three. A simple release now needs four sign-offs. Every problem was solved by adding something - until the work became slow and painful. Complexity at work often feels unavoidable - in workflows, systems and products. Often it is not. The team built most of it themselves, one well-meant addition at a time, and never paused to remove anything.

This activity makes that growth visible. Then it forces the one move teams never make on their own - taking things out.

How this works

Think of an expense approval process. It started as “submit, approve”. Then people added a review by finance, a compliance check, and a second sign-off. Now it takes weeks.

Bring a real-world complex system or process to this activity. Write each part of the process on a card - one step, one check, one meeting per card. Then lay the cards in sequence on a board. Now you can see the complexity.

First, ask one question about every card: was this added to fix a problem, or did it remove something? Most teams discover that almost every card is an addition. That’s the first surprise.

Then a removal-only round begins. The only rule: you can only take cards off. No adding. You compare the simpler version against the original.

Team: one person runs the activity using the Facilitator Guide. Everyone else takes part.

Time required

Solo ✓   Team ✓

Solo: 15–20 minutes.   Team: 40–50 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

Bring a real process, plan or workflow that has become heavy and slow - something you find painful.

Use it whenever:

  • work that used to be simple now takes longer than it should
  • you’re about to fix a problem by adding something - another step, tool, meeting or report
  • onboarding someone to the process takes far too long to explain
  • everyone agrees it’s too complicated, but no one can say what to cut

What you get

A simpler process.

  • A count of how your process actually grew - additions versus removals, on one board
  • A simpler, removal-only version of the process, tested against the original
  • One thing you’ll take out this week, with an owner

You’ve done it well when: the team can see that almost everything it ever did was an addition - and that removing a few things improved the process more than adding ten things ever did.

What you’ll notice

  • Removing felt harder than adding - even when it worked better
  • The complexity was built, not inherited
  • “What can we remove?” becomes a question you can actually ask

Why this works

When a problem appears, people reliably add things. They overlook removing - even when removing would work better. The option to remove is genuinely not seen.

Every addition once solved a real problem. The issue isn’t that people made bad decisions - it’s that almost nobody ever removes anything afterwards. Making every change physical, then banning addition for one round, forces the move the mind skips.

What you need

Everything comes in one kit. Here is each part, and when you use it:

Process cards - blank, write-on (core). You write each part of your real process onto a card - one step, check, meeting, report or sign-off per card. One card, one step.

Removal-prompt cards. Use them when the team is reluctant to remove something. Each card has a prompt that helps the team explore what would happen if that part disappeared (“what would break if this step were removed?”).

Starter-situation cards (optional). Short examples of processes that have become heavier over time (for example: “our approval process now has too many sign-offs” or “our release process keeps gaining extra checks”). Use one only if the team doesn’t have a real process of its own to work on. Otherwise, set them aside.

The board. Holds all Process cards and the add/remove tally. Left side = the process as it is today. Right side = the cards removed. What remains and what was removed sit side by side.

Roles - Team: a facilitator (runs the flow, holds the no-adding rule, draws the prompt cards, captures the result) and Participants (map the process, tag it, and choose what to strip). Solo: you run it yourself from this page.

Steps

  1. Set up Team: appoint a facilitator first - they run the activity from the Facilitator Guide. Solo: just begin. Name the one real process you’re going to put on the table. Write it at the top of the board.
  2. Build the process (8–10 min). The team writes every part of the actual process onto a Process card - one step, check, meeting, report or approval per card. One card, one step. Lay the cards on the left side of the board. Arrange them in the order they happen today. Don’t tidy it; show it as it is. This is the current process. Leave the right side empty for now.
  3. Count how it grew (6–8 min). Tag each card: was this ADDED to fix a past problem, or did it REMOVE something? If a part was introduced to solve a problem, count it as an addition. Count the “Added” and “Removed” cards and read the total out loud - “We added eighteen things. We removed two.” Then pause. Most teams discover that almost everything they ever changed was an addition. That is the first thing to notice.
  4. Strip it - adding is banned (10–12 min). This round, the only legal move is to take a card OFF the board. You must not add anything. Starting with the cards that feel least necessary, the team proposes removals one at a time. If the team is unsure about a card, the facilitator draws one removal-prompt card and reads it aloud; after a short discussion, the team decides whether the card stays or comes off. If the team believes the process would still work without the card, remove it. Don’t redesign it yet - just remove it. Place the removed cards on the right side of the board.
  5. Compare the two versions (5–7 min). Look at what remains on the left side and what has been removed on the right. Ask: would the simpler version still work - and might it actually work better? Notice which process you’d rather use tomorrow morning. This is the moment that matters: removing a few things often improves a process more than adding new ones.
  6. Commit (4–6 min). Pick one thing you will take out of the real process this week. Name the owner and the date. Write down the one question to reuse: before adding anything, ask first - what can we remove?

Output / Takeaways

  • The add-versus-remove count for your real process
  • A simpler, removal-only version, compared against the original
  • One removal you’ll make this week - owner and date - and the reusable question

Important rules

  • This round, every fix must remove something - adding is not allowed
  • Don’t redesign while removing - take cards off, don’t replace them
  • One part of the process per card, shown as it really runs
  • If the process would still work without a card, it comes off
  • Compare the simpler version to the original before deciding
  • Leave with one real removal, not just the realisation

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

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