Product Goals
Measurable, time-bounded changes in customer or business outcomes that translate product strategy into focused team direction.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-goals/
01What it means
Product goals describe important outcomes a product should influence within a decision horizon. They bridge strategy and team action by specifying a desired change, relevant population, measure, timeframe, and guardrails. Unlike feature targets, they leave room to discover the intervention; unlike broad business targets, they should be meaningfully influenceable by product teams.[1][2][3]
- 01Strategic outcomeWhy this change matters now
- 02Population + baselineWho or what starts where
- 03Desired movementInfluenceable measurable change
- 04Timeframe + guardrailsQuality, equity, risk, cost
- 05Evidence reviewRevise action or assumptions, not game metric
A useful goal names the population, baseline, direction, horizon, and guardrails without pretending the product team fully controls the result.
02Why it matters
Goals concentrate learning and force tradeoffs. They help teams compare opportunities, coordinate dependencies, and evaluate whether shipped work changed anything valuable. Well-designed product goals also reveal tensions between customer benefit, commercial performance, operational health, and long-term trust before those tensions become surprises.
03When to use it
Set product goals after strategic choices are clear enough to establish direction and before teams commit to solutions. Refresh them at a cadence suited to the outcome, while preserving longer measurement windows for behaviors such as retention that cannot responsibly be judged in a week.
04How it works
- Derive a small number of outcomes from the product strategy and current evidence.
- Define the affected user or system, baseline, desired movement, and timeframe.
- Check that teams can influence the result without controlling it completely.
- Add guardrails for quality, equity, risk, cost, and unintended behavior.
- Let teams discover solutions while making dependencies and decision rights explicit.
- Review progress using trends and evidence, then revise actions or assumptions rather than gaming the measure.
05A practical example
A clinical scheduling product sets a six-month goal to reduce the share of referred patients who abandon booking from 34% to 24%, without increasing inappropriate appointments or call-center workload. Teams may test reminders, eligibility explanations, and slot matching; shipping any one feature is not itself success.
06Where it breaks
Targets can narrow attention, invite metric gaming, and overstate causal control. Some valuable work protects future capability or reduces poorly measured risk. Goals should therefore be interpreted with qualitative evidence and counter-metrics, not used as mechanical performance contracts for individuals.
Common mistakes
- Expressing a solution or delivery milestone as the goal.
- Choosing a company metric too distant from the team’s influence.
- Omitting baselines, timeframes, or guardrails.
- Changing definitions when results become uncomfortable.
07Sources
- Empower Product Teams with Product Outcomes, Not Business OutcomesProduct Talk · Product discovery guidanceEmpower Product Teams with Product Outcomes, Not Business Outcomes
- Set Goals with OKRsGoogle re:Work · Institutional goal-setting guideSet Goals with OKRs
- Coaching – Strategic ContextSilicon Valley Product Group · Product leadership articleCoaching – Strategic Context