C · Value judgment and direction setting

Business outcomes and validation

Connecting work to user and business outcomes, setting baselines and guardrails, and validating impact.

Classification boundary

Include: Include questions that set goals, baselines, and guardrails, then verify user or business outcomes.

Choose a neighboring leaf when: Use metrics/causality for calculation, experiment design, and attribution methods; use this leaf for target outcomes and follow-up decisions.

This capability may appear in standards across different stages. Explore stage expectations

15 questions

Choose a group based on the evidence you need. Groups follow existing question formats, not difficulty or mandatory prerequisites. Each batch has up to eight questions.

Judgment and options15

Compare goals, constraints, options, and trade-offs.

Questions 1–8

The metric was met, but you felt the business did not really get better. Has that happened to you? How did you notice, and what did you do?
After a feature launches, how do you judge whether it met its original goal? When do you review it, and what would you decide differently afterwards?
User mix or external conditions change during a project, making the original baseline incomparable. How would you continue judging the outcome?
The target metric improved, but refunds, complaints, or manual handling also worsened. How would you decide whether the outcome is acceptable?
The initial effect of a feature is strong but fades over several months. How would you distinguish novelty from lasting behavior change?
The final business outcome will take months to appear, but the team must decide whether to continue investing now. How would you use leading indicators?
Several teams changed the product, pricing, and operations at once, and the overall outcome improved. How would you assess each contribution?
An experiment shows no expected lift, but also does not prove the idea ineffective. How would you decide whether to continue, change, or stop?

Questions 9–15

Two projects each meet some goals, but one delivers more user benefit per unit of investment. How would you reallocate resources?
A pilot meets its target, but results vary when expanded to more regions or segments. How would you judge whether the result is replicable?
A redesign improves paid conversion but leaves more users unable to complete a core task. How would you judge whether the growth is worth it?
A new process doubles weekly feature releases, but task completion is unchanged and support tickets rise slightly. How would you decide whether to continue, adjust, or stop?
A project meets its conversion target at launch, but the effect fades six weeks later; the team attributes it to seasonality, while Operations reports more manual intervention. How would you define sustained outcomes, attribution, and follow-up ownership?
A self-service flow reduces agent volume, but users with complex issues wait longer after escalation and total complaints do not fall. How would you define the end-to-end outcome and identify costs shifted by local optimization?
Quarterly revenue reaches target, but many contracts use deferred payment and heavy discounts, extending collection cycles and increasing bad-debt risk. How would you reassess outcome quality and adjust the growth strategy?

Back to the whole domain