Outcome

Origin & evolution

The idea has roots in the logic models long used in programme evaluation, where inputs lead to outputs, outputs to outcomes, and outcomes to impact. Product management borrowed the chain and made the middle link its centre of gravity. Josh Seiden gave the field its working definition in Outcomes Over Output (2019): "an outcome is a change in human behaviour that drives business results." The constraint🔒ConstraintStrategyA constraint entityView reference → in that sentence is doing the work. A feature⭐FeatureProduct SpecificationA product capability or featureView reference → shipped is an output; users saying they like it is a sentiment; a measured shift in what they actually do is an outcome.

Seiden paired the definition with three questions a team uses to find one: which user behaviours drive the business result, how do we get people to do more of those behaviours, and how do we know we are right. The framing built on the outcome-oriented thinking in his and Jeff Gothelf's Lean UX (2013), and it aligns with Marty Cagan's argument that empowered teams should be handed problems to solve and outcomes to achieve, not features to build. The debate that followed was about measurability. Critics noted that "behaviour change" can be slippery, so the discipline tightened: a usable outcome names the specific behaviour, the direction of change, and the metric🔢MetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference → that detects it, before any solution🔧SolutionDiscoveryA proposed approach to address an opportunityView reference → is proposed.

How it works in practice

A B2B analytics product wants to grow expansion revenue. Revenue is the business result, too far from the team's hands to be a daily target. So the team names the outcome one layer up: more accounts add a second team to their workspace within 30 days of signing up. That is a behaviour, it is measurable, and the team has plausible ways to influence it.

The outcome reframes the roadmap🛣️RoadmapProduct SpecificationA strategic plan of features and milestonesView reference →. The team stops asking "what should we build?" and asks "what would make a first team invite a second?" Candidate answers (a shareable dashboard🎛️DashboardData & AnalyticsAn analytics dashboardView reference →, an invite prompt at the moment of insight🔦InsightUser ResearchA synthesised finding from researchView reference →, role-based permissions) become bets against the outcome, each testable. Six weeks in, second-team adoption moves from 12% to 19% of new accounts. The team has not booked the expansion revenue yet, and they can already prove the behaviour they believed precedes it is shifting in the right direction.

Outcome vs. its neighbours

• Output: an output is what the team produces, a feature, a release🚢ReleaseProduct SpecificationA shipped version of the productView reference →, a page. It is fully within the team's control and easy to count, which is exactly why counting outputs feels productive while saying nothing about value. An outcome measures the behaviour the output was supposed to cause.
• Impact: impact is the longer-term, larger-scope business or mission🧭MissionStrategyThe purpose and reason the product existsView reference →-level result, like sustained revenue growth or market share, often the sum of many outcomes over time. An outcome is the nearer, more attributable behaviour change a single team can move this quarter and trace to its work.
• Objective🏁ObjectiveStrategyA strategic goal (OKR)View reference →: an objective is the qualitative direction with no number attached. An outcome is its measurable cousin, carrying a target and a measurement method by definition, which is why a team can hold one objective and several outcomes beneath it.

In the graph

In the Unified Product Graph, outcome🏆OutcomeStrategyA desired business or user outcome is a hub in the Strategy & Outcomes region and the anchor of its creation sequence: teams are guided to name the outcome before the objective, the key results📈Key ResultStrategyA measurable result tied to an objectiveView reference →, or any feature. It quantifies through outcome_measured_by_metricOutcomemeasured byMetrichierarchy and outcome_tracked_by_metricOutcometracked byMetrichierarchy, and it exports across region boundaries via outcome_delivered_by_featureOutcomedelivered byFeaturecross-domain into product delivery and outcome_reveals_opportunityOutcomerevealsOpportunitycausal into discovery. Those export edges are what keep outcomes from floating free: an outcome🏆OutcomeStrategyA desired business or user outcome with no connected feature is unbuilt, and one with no connected metric is unprovable, both visible as gaps the moment the graph is queried.