Outcome Template

The Outcome Template is the anatomy of a well-defined outcome. It has four sections that trace through the Product Logic Model, from the behavioral change you’re targeting down to the bets you’ll make to get there.

• Outcome. A 3-5 word title (easy to search and reference) plus a longer description detailing the specific, measurable behavioral or system change. Identify the target persona or market segment and the outcome type (User, Customer, Technical). Keep it high-level and directional; detail lives in Metrics.

• Impact. What business value does this create? Specific lagging indicator targets like revenue +$2M or cost savings $500K. This is the “So what?!” answer. Impacts often operate on a longer time frame of quarters or years

• Metrics. Leading indicators that show early progress toward the outcome. Typically measures of behavior. Directional metrics work best (% increase, % decrease) because they set direction without false precision. One primary indicator plus optional supporting indicators.

• Scope. The bets you’ll make to increase the odds of your outcome happening. Three categories: Discoveries (experiments, research, validations), Deliveries (epics, features, tech investments), and De-risking Measures (spikes, PoCs, prototypes). Scope is the most flexible part of the template; it changes as teams learn.

Each entry on an Outcome-Based Roadmap follows this structure. The template enforces the discipline of connecting scope to outcomes to impact, making the Output-Activity Trap harder to fall into.

Resources

• Product Logic Model — the causal chain the template traces through
• Outcome-Based Roadmap — where outcome templates get placed on a timeline
• Outcome-Based Roadmaps — where teams practice filling these out