Cascade vision through themes, outcomes, objectives, key results, and the bets you are making to get there.
objectivev0.2.0When to run it
When the team has accumulated work without a unifying direction, or when a new quarter / cycle is starting and last quarter's objectives have drifted. Also the right move after a strategy refresh — the playbook captures the new strategy in graph form so it's queryable, not just slide-deck-shaped.
What you'll have at the end
A small set of objective entities, each connected to key_result entities that make the objective measurable, and outcome entities that name the broader change in the world the objectives are pursuing. Every objective should have a clear chain down to metrics.
Common starting point
One objective for the next 90 days, written as a verb-first statement of intent. Decompose into 2-4 key results.
Sequence summary
One step: run the strategy domain creation sequence — objectives, key results, outcomes, strategic themes. Hands off to the Hypothesis Validation playbook when a key result's validation gap surfaces.
Name what you are building toward and how you will get there. Vision is the destination; mission is the orientation. One of each, no more.
Choose 2–4 strategic themes that focus the work. Past four, you have lost focus, not gained coverage.
Frame the changes in the world the product is trying to cause: shifts in behavior, perception, or position. Not features shipped.
Translate outcomes into directional bets the team commits to within a horizon. An objective is an ambition with a deadline attached.
Give each objective 2–4 measurable key results. Without measurement, the objective is a wish.
Group features and work streams into initiatives the team will actually execute. Name the capabilities they build.
Capture the bets you are making (assumptions) and the choices you have ratified (decisions). These guard the work against silent drift.
Gap: → playbook:discovery-validation-hypothesis-cycle