Strategy & Outcomes
Strategy that connects to the work, all the way down
Strategy lives in a deck, execution lives in a tracker, and nothing connects them, so the two drift the moment the offsite ends. Six months later the roadmap is full of features nobody can trace to a goal, and the strategy is full of goals nobody can trace to work. UPG types the whole cascade, from vision and mission, through themes and outcomes, down to a measurable key result, around the outcome as the anchor. Every objective names the change it chases, every feature names the outcome it serves, and every bet underneath is a node the team can find again.
“An outcome is a change in human behavior that drives business results.”
The vision and mission at the top of the cascade
A visionvisionA long-term aspirational statement of the future state is the destination; a missionmissionThe purpose and reason the product exists is the orientation. The vision is realised through the mission and guides the strategic themestrategic_themeA high-level strategic focus area for a planning period nodes that focus the work, while the mission is supported by the strategic pillarstrategic_pillarA foundational principle that guides decisions it stands on.
A graph holds one of each, no more. A vision that points in two directions leaves the cascade below it ambiguous, since every theme, outcome, and objective inherits whatever focus the top two nodes set.
the destinationvisionA long-term aspirational statement of the future statemissionThe purpose and reason the product existsstrategic_themeA high-level strategic focus area for a planning periodstrategic_pillarA foundational principle that guides decisionsA vision names the destination; a mission makes it operational. The vision is realised through a mission and guides the strategic_theme entities that focus the work, and the mission is supported by the strategic_pillar entities it stands on. UPG holds one vision and one mission per product.
Themes focus the work into a few strategic bets
Two to four strategic themestrategic_themeA high-level strategic focus area for a planning period nodes focus the work; more than four spreads it back out. A theme carries real edges: it delivers an outcomeoutcomeA desired business or user outcome, contains the objectiveobjectiveA strategic goal (OKR) nodes that chase it, pursues the initiativeinitiativeA large coordinated effort to achieve a strategic goal that executes it, requires a capabilitycapabilityAn ability that enables value delivery, and is measured by a key resultkey_resultA measurable result tied to an objective.
This is the focusing layer of the whole graph. Everything downstream rolls up to one of a handful of themes, so the strategic bet a given piece of work belongs to is always a traversal away.
strategic_themeA high-level strategic focus area for a planning periodstrategic_themeA high-level strategic focus area for a planning periodstrategic_themeA high-level strategic focus area for a planning periodoutcomeA desired business or user outcomeobjectiveA strategic goal (OKR)initiativeA large coordinated effort to achieve a strategic goalcapabilityAn ability that enables value deliverykey_resultA measurable result tied to an objectiveA strategic_theme is the focusing layer of the cascade. Each one delivers an outcome, containsthe objectives that pursue it, pursues the initiatives that execute it, requires the capabilities it depends on, and is measured by a key_result. The rest of the cascade rolls up to a theme, so a graph with two to four themes keeps the work attributable to strategy.
The outcome is the anchor the region converges on
Most planning tools anchor on output: a list of features, shipped or not. UPG anchors the region on the outcomeoutcomeA desired business or user outcome, the change the work is meant to cause. The rest of the region converges on it: a featurefeatureA product capability or feature delivers an outcome, an objectiveobjectiveA strategic goal (OKR) advances it, a metricmetricA unified metric that measures progress, health, or behaviour across the product measures it.
The traceability runs both ways. The question “why is this being built?” resolves to the outcome a feature delivers; the question “is this outcome real?” resolves to the metric measuring it. A feature with no path to an outcome stands out as exactly that: output with no purpose attached.
The outcome is the hub the rest converge on: features deliver it, objectives advance it, metrics measure it. So “why are we building this?” is one traversal, and a feature with no path to an outcome stands out as exactly that. Strategy and execution sit one edge apart, not in two documents that drift.
Objectives and key results, made measurable
An objectiveobjectiveA strategic goal (OKR) advances an outcomeoutcomeA desired business or user outcome and is achieved through two to four key resultkey_resultA measurable result tied to an objective nodes, each quantified by a real metricmetricA unified metric that measures progress, health, or behaviour across the product. The metric is what turns the objective from a stated ambition into a number every check-in reads against.
Status lives on the node. Confidence and progress are properties of the objective itself, so a quarterly review is a traversal of the graph rather than a manual reassembly. The OKR framework is a lens over exactly these edges.
outcomeA desired business or user outcomekey_resultA measurable result tied to an objectivemetricA unified metric that measures progress, health, or behaviour across the productkey_resultA measurable result tied to an objectivemetricA unified metric that measures progress, health, or behaviour across the productAn objective advances an outcome, and it is achieved through two to four key_result entities, each quantified by a metric. Confidence and progress are properties on the objective node, so a check-in reads the current values from the graph.
Vision down to a number, every tier typed
Seen end to end, the tiers line up as one chain: a visionvisionA long-term aspirational statement of the future state sets direction, a strategic themestrategic_themeA high-level strategic focus area for a planning period focuses it, an outcomeoutcomeA desired business or user outcome names the change being pursued, an objectiveobjectiveA strategic goal (OKR) commits to it within a horizon, and a key resultkey_resultA measurable result tied to an objective makes it measurable. Each is a typed node linked to the one above it.
Every link in the chain is a real edge, so no tier can quietly detach from the one above it: a key result always names the objective it serves, and a vision always names the work carrying it.
visionA long-term aspirational statement of the future statestrategic_themeA high-level strategic focus area for a planning periodoutcomeA desired business or user outcomeobjectiveA strategic goal (OKR)baseline 31% -> target 70% by Q3key_resultA measurable result tied to an objectiveVision down to a number, every tier a typed node linked to the one above it. The chain is not a slide that goes stale; it is structure, so a key result always names the objective it serves, and a vision always names the work carrying it.
The assumptions and decisions a strategy rests on
An initiativeinitiativeA large coordinated effort to achieve a strategic goal is a work stream the team commits to. It drives the outcomeoutcomeA desired business or user outcome it chases, realises the value propositionvalue_propositionA unique value offered to customers behind it, and unlocks the revenue streamrevenue_streamA source of revenue it is meant to, but it also assumes an assumptionassumptionA belief taken as true that underpins a strategy: the thing it is betting on.
That last edge is the one most plans leave implicit. With the assumption typed, an invalidated bet lets the graph point straight at every initiative that rested on it. Paired with the decisiondecisionA recorded decision with context, rationale, and consequences nodes a team ratifies, the reasoning behind a direction stays attached to the work it shaped, available long after the meeting that set it.
a work stream the team commits toinitiativeA large coordinated effort to achieve a strategic goaloutcomeA desired business or user outcomevalue_propositionA unique value offered to customersrevenue_streamA source of revenueassumptionA belief taken as true that underpins a strategyAn initiative drives the outcome it chases, realises the value_proposition behind it, and unlocks the revenue_stream it is meant to, and it also assumes the assumption it rests on. When an assumption is invalidated, a traversal over initiative_assumes_assumption returns every initiative that depended on it. The decision entities that ratify a direction record the reasoning alongside it.
The cascade links out to the rest of the lifecycle: down into delivery, up into the portfolio, and across to the evidence underneath the bets.
The strategy and outcomes region in full: vision, themes, outcomes, objectives, key results, and every edge between them.
How an initiative becomes features, epics, and shippable work that drives the outcome.
The cascade across many products: metric and OKR rollups to the company top line.