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.
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.
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.
Bring a real process, plan or workflow that has become heavy and slow - something you find painful.
Use it whenever:
A simpler process.
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.
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.
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.
Output / Takeaways
Important rules
Planning to facilitate this activity? Access the resources below to get started.