A strategic initiative is a major, often cross-team effort meant to move an objective. Managing them well means treating each as a bet with a hypothesis and an owner, tied to the goal it serves, rather than a standing project that runs forever. This playbook shows how to run initiatives so they shift the numbers they were created for instead of drifting.
Goals tell you where to go; initiatives are how you get there. Yet in most organizations the two live in different worlds. The OKRs sit in one tool and the big projects in another, and the link between them is a hopeful assumption. So initiatives accumulate, outlive their purpose, and consume capacity long after anyone remembers what objective they were meant to serve. This playbook treats an initiative as what it should be, a testable bet on moving a goal, and shows how to run it that way.
Before an initiative gets a budget or a team, name the Key Result it is meant to move and by how much. An initiative that cannot point to a single goal it advances is either someone's pet project or business-as-usual wearing a strategic label. The link to the goal is the first filter, and it kills more bad initiatives than any other step.
State it plainly: we believe that doing X will move metric Y, and we will know within Z weeks. Framing an initiative as a hypothesis rather than a fixed deliverable changes how you run it. You watch for evidence, and you are willing to stop early if the bet is clearly not paying off. A project framed as a guaranteed output cannot be killed without someone losing face.
Every initiative needs a single accountable owner and a date by which it either delivers or is reassessed. Open-ended initiatives are the ones that quietly become permanent. The end date is not a deadline to punish; it is a forcing function to decide whether the bet is still worth the capacity it consumes.
Teams can run only so many initiatives at once before each one starves. Rank them by expected impact on the goals and start the top few; queue the rest. The trap is the parallel-everything approach, where ten half-resourced initiatives all crawl and none lands, instead of three fully backed ones that actually move.
In reviews, the question is not whether the initiative's tasks are on schedule but whether the metric is moving. An initiative can be perfectly on plan and still failing its purpose, because the hypothesis was wrong. Watching the goal rather than the task burndown is what tells you to double down or change course while there is still time.
When an initiative hits its date, force a decision: it worked and ends, it needs one more defined push, or the bet failed and you stop. The most expensive initiatives are the undead ones that neither deliver nor die, drawing people and attention for quarters. Closing them, win or lose, frees the capacity for the next bet.
A goal is the outcome you want, expressed as a metric and target; an initiative is a body of work you bet will move that goal. Goals describe the destination, initiatives are the route. Keeping them distinct is what lets you change the route without losing the destination.
Few enough that each is genuinely resourced, usually two or three major ones per team per quarter. More than that and they compete for the same people until all of them slow down. It is better to finish a few than to keep many half-alive.
When the evidence says the hypothesis is not holding and no reasonable change will fix it. If you framed the initiative as a bet with a metric and a date, this decision is far easier, because you set the conditions for stopping before you grew attached to it.
Vindaris connects every goal to the traceable work moving it, so the cadence in this playbook runs on real progress instead of hand-typed status. Start free, no credit card.
Sign Up for Free