A workshop to make stopping a project safe and routine
Together, we map what's running, agree on what each project must prove and by when, and plan how we'll call a stop and share it.
The outcome is a simple way to stop projects that fits your current stage gates and frees up budget for work that deserves it.
Map the current portfolio
What's running, and what should have stopped by now?
REQUIREMENTS
Everything currently running
What each is waiting for
How long it has waited
What it costs to keep going
Agree the stop points
What must each project prove, and by when, to keep going?
REQUIREMENTS
What each must prove
The deadline and the bar
What triggers a stop
Who gets to call it
Make stopping safe
How do we stop the first project without blaming the team?
REQUIREMENTS
Pick a first project
Set its bar in the open
Agree how stops are shared
Move the budget on
Clear stop points for every running project, agreed before anyone has to argue
A way to announce a stop that credits the team, even when it's your own project
A way to stop and reinvest that fits your current stage gates
An owner and a date for the first stop, and a plan for the rest of the portfolio
