Teams commit to work before they know what it really costs them. The commitment is concrete - a named project, a promised date. The capacity it will eat is vague. So the team says yes, again and again, and only finds out it is over capacity once the work is late and people are stretched. This makes the hidden cost of each commitment visible up front, so the team can see what it can actually afford before saying yes.
An engineering team commits to six roadmap items for the quarter. Everyone agrees they’re important, and the plan looks achievable. Two weeks later, production incidents eat into the team’s time; two engineers are pulled into customer escalations, and one feature turns out to be twice as complex as expected. By the end of the month, the team is already overloaded. The problem wasn’t that it worked too slowly - it committed before it knew what the work would really cost.
So picture your team’s real capacity as a fixed pool of tokens. That pool is all you have - and some of it is already used up by work in flight. Now picture the commitments you’ve taken on, each with its real cost turned face down.
The team spends its capacity tokens on those commitments - guessing the cost. Then the real costs are turned over. Almost always, they add up to more capacity than the team has: you’re already over before adding anything new. So you take commitments off the table until you’re back within what you actually have. The ones you remove are the ones you wanted but can’t afford - and that is the moment the lesson lands: we said yes before we knew the cost.
Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.
Team ✓
Team: 45–90 minutes, with a facilitator. Best run at a planning or commitment point, with the people who own the work.
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.
Bring the real set of commitments you’re about to take on - a quarter, a release, a roadmap - before you’ve said yes, not after.
Use it whenever:
You’ve done it well when: the team can see it was already over capacity, can point to what it dropped and why, and leaves with a set of commitments it can deliver.
Teams don’t overcommit because they’re greedy - they overcommit because the commitment is concrete and visible while its cost stays hidden. You can’t say no to a real list with an imaginary limit. Once every commitment has a real cost and your capacity is a fixed pool you watch run out, the gap stops being a guess and becomes real - and saying yes and saying no become realistic decisions.
Everything comes in one kit. Here is each piece, what it is, and when you use it:
Capacity tokens (one pool for the team). Small tokens that stand for your team’s real capacity - for example, one token = half a person-week. You count out the team’s true capacity in tokens at the start. This is all the team has to spend.
“Already in flight” markers. A few tokens in a different colour for the work the team is already doing. You set these aside first - they are spent before any new commitment, so the team sees how little is really free.
Commitment cards (with a hidden cost). One card per piece of work the team is taking on. Each card has its real capacity cost printed on the back or under a flap, so it stays hidden until the reveal. The team writes its own commitments on blank cards; the facilitator sets the hidden cost.
The board. A simple surface with two areas: a capacity area where the token pool sits, and a commitments area where the cards are laid out. You place cards and move tokens between the two as you go.
Capture space. Room to write down the final set of commitments the team can afford, and the ones it dropped.
Roles - Team: a facilitator (counts out the capacity tokens, sets the hidden costs, runs the spend and the reveal, keeps time) and participants (write the commitments, spend the tokens, decide what to drop).
Output / Takeaways
Important rules
Planning to facilitate this activity? Access the resources below to get started.