Why agree on the rules first?
I see it happen in workshops. A management team choosing its goals, its priorities, its must-win battles. It ends in design by committee: the lowest common denominator. Nobody can really be against it. But nobody is really for it either.
The fix is not a better list. It is agreeing on the rules before anyone writes a single battle.
When do I use it?
In my experience, must-win battles work very well. But I do not see them as something every organisation needs. If your normal portfolio management and prioritisation process already help you make clear choices and act on them, use that process.
I use must-win battles when that process is not working well. They are a catalyst: a way to bring focus back, make the important choices explicit and accelerate action. The point is not to add another layer of priorities to a system that already works.
What is inside.
- Why agree on the rules firstOpen
- When I use itOpen
- The rulesMembers
- How to run itMembers
- What you walk out withMembers
- Pillars or battlesMembers
- VariationsMembers
The rest opens right here.
Your account has no access to the tools yet.
Opening the rest of this page…
Sign in, or ask for access once. You come back to this page, and it opens further.
Ask for it once and I will get back to you personally. You come back to this page, and it opens further.
Peter Killing, Thomas Malnight and Tracey Keys, Must-Win Battles: How to Win Them, Again and Again (IMD). The workshop steps are my own practice.

