Outcome Based Planning: Roadmap Template and Examples

9 min read ยท 2026-11-02

Outcome based planning means you plan around the measurable change you want to cause, such as more new accounts reaching their first report. Features and projects become bets that might cause that change. An outcome based roadmap is the visual version of this plan. Each row is an outcome with a metric, a baseline, a target and a deadline, and the work sits underneath as candidate solutions.

The idea is easy to say and harder to apply. "Launch a new onboarding checklist in Q2" is an output. "Increase 30-day activation from 42% to 60% by the end of Q2" (illustrative numbers, use your own baseline) is an outcome. This guide gives you a six-phase plan to convert your current roadmap in about three weeks, a template you can copy row by row, examples for six teams, and a way to handle stakeholders who still want dates.

The roadmap at a glance

Goal: Replace a feature-list roadmap with an outcome based roadmap that guides next quarter's decisions and holds up in front of leadership. Duration: About 3 weeks of setup, then a 13-week quarter of measuring and adjusting.

  1. Align on vision and strategy (Days 1 to 2)

    Agree on what the business needs from your team this quarter before you write a single outcome.

    • Write down the company or department goal your team supports this quarter.
    • Ask your sponsor which result would make the quarter a clear success.
    • List the fixed constraints: contracts, compliance deadlines, partner launches.
    • Name one owner for the roadmap and one decision maker for trade-offs.

    Milestone: A one-page brief with the strategic goal, the constraints and the decision maker, approved by your sponsor.

  2. Audit the current roadmap (Days 3 to 5)

    Find out what your existing feature list is actually trying to achieve.

    • List every planned feature or project and who asked for it.
    • For each item, ask: what user or business change should this cause?
    • Group items that share the same intent into candidate outcomes.
    • Flag items nobody can link to any outcome as candidates for removal.

    Milestone: A sheet that maps every current item to a stated purpose or a removal flag.

  3. Define outcomes and metrics (Days 6 to 9)

    Turn the candidate groups into three to five measurable outcomes.

    • Write each outcome as a change in behavior: who does what, in which direction.
    • Pick one leading metric per outcome that can move within weeks.
    • Record today's baseline from your analytics, CRM or ticketing tool.
    • Set a target and a deadline, then agree on both with the decision maker.

    Milestone: Three to five outcomes, each with an owner, a metric, a baseline, a target and a deadline.

  4. Discover and prioritize bets (Days 10 to 14)

    Find several possible solutions per outcome before committing to any.

    • Review user interviews, support tickets and usage data for the root problem behind each metric.
    • List at least two solution ideas per outcome with design and engineering.
    • Size each bet as small, medium or large effort.
    • Pick one or two bets per outcome and write the evidence that would make you stop each one.

    Milestone: A ranked list of bets under each outcome, each with a stop rule.

  5. Publish and present (Days 15 to 16)

    Share the roadmap so every audience sees outcomes first and solutions second.

    • Lay outcomes out in Now, Next and Later columns.
    • Show baseline and target next to each outcome.
    • Put fixed-date commitments in their own lane.
    • Walk leadership, sales and support through it in one session.

    Milestone: A shared roadmap that the decision maker has reviewed and that every team can open without asking for a new deck.

  6. Measure and review (Weeks 1 to 13)

    Use metric movement to decide which bets continue.

    • Check outcome metrics every two weeks next to what shipped.
    • Stop bets that hit their stop rule and start the backup bet.
    • Log each roadmap change with a one-line reason.
    • Run a quarter-end review comparing results with targets.

    Milestone: A quarter-end report showing the movement of each outcome and the lessons for next quarter's plan.

Outcome vs output: what outcome based planning changes

An output is something you deliver: a feature, a campaign, a migrated server. An outcome is a change in what people do because of it: more customers finishing setup, fewer billing tickets, faster month-end close. Impact is the business result those outcomes feed, like revenue or retention.

Outcome based planning works at the middle layer. Impact moves too slowly to steer weekly work, and outputs can be marked "done" without anything improving. Josh Seiden's book Outcomes Over Output defines an outcome as "a change in human behavior that drives business results," and suggests writing it as: a specific group of customers will do a specific behavior a specific amount more or less. A related method, Impact Mapping, created by Gojko Adzic, links each feature to the business goal and the behavior change it is supposed to support.

Outcome based roadmap vs feature roadmap vs goal-based roadmap

These three are often mixed up. The difference is in what each one commits to.

A quick test: if you can mark a row complete without opening any data, it is a feature or goal roadmap with new labels.

  • Feature roadmap: commits to building specific things by specific dates. Success means it shipped.
  • Goal-based roadmap: groups work under broad goals like "improve onboarding" but often has no metric or baseline.
  • Outcome based roadmap: commits to moving a specific metric from a known baseline to a target. Success means the number moved.

How to create an outcome based roadmap from a feature list

Most teams already have a feature list. Run each item through the four questions below to turn it into an outcome.

Example: "Build a Slack integration" becomes "Increase the share of new teams that receive project alerts in their chat tool, from the current baseline to the agreed target, by end of Q3." The integration stays on the roadmap as one bet under that outcome.

  • Who is this for? Name the segment, such as new trial accounts or regional managers.
  • What behavior should change? Pick something observable, not a feeling.
  • Where are we today? Record the baseline before you set a target.
  • By when? Use the quarter as the default time box.

Outcome based roadmap template (copy this structure)

Use one row per outcome and fill the fields listed below in order.

Filled example for Now (illustrative numbers, use your own baseline): Outcome "More new accounts activate in their first month." Metric: 30-day activation rate. Baseline 42%. Target 60%. Deadline end of Q2. Bets: guided first project, onboarding checklist. Stop rule: no movement after four weeks of release.

As a chart or graphic, three layouts are common: a hierarchy (vision, then outcomes, then bets), a timeline, and a release view. Now, Next and Later is the easiest to present because it signals priority without promising dates. It works the same in a slide, a spreadsheet or a visual board.

  • Column: Now, Next or Later
  • Outcome: the behavior change, in one sentence
  • Metric: the single number you will track
  • Baseline: today's value
  • Target: the value you aim for
  • Deadline: end of quarter or a specific date
  • Owner: one named person
  • Bets: one or two solutions, plus a backup
  • Stop rule: the evidence that ends a bet

Outcome based roadmap examples by team

The method is not only for product teams. Here is one before and after per function.

Each line below needs its own baseline from your data before it goes on the roadmap.

  • Product: "Launch onboarding checklist" becomes "Raise 30-day activation from the current baseline to the agreed target by end of Q2."
  • Marketing: "Run a webinar series" becomes "Increase the share of webinar attendees who book a demo within 14 days."
  • IT: "Migrate the helpdesk tool" becomes "Cut average time to resolve password tickets by the end of the quarter."
  • Data: "Build a sales dashboard" becomes "Increase the number of regional managers who check pipeline data weekly."
  • Operations: "Automate invoice entry" becomes "Reduce days needed to close the month."
  • HR: "Redesign the onboarding handbook" becomes "Raise the share of new hires who complete their first project within 30 days."

Outcome based planning for consultants, project managers and new managers

Consultants can use outcomes to frame an engagement. Agree with the client on two or three results with baselines in the first week. Then present each workstream as a bet toward one of them. This keeps the steering committee on value rather than on activity reports.

Project managers can keep their delivery plan and add an outcome layer above it. Milestones still track the work, and the outcome tells the sponsor why the project exists. A manager starting a new role can write a 30-60-90 day plan the same way. Use the first 30 days to set baselines, the next 30 to pick outcomes and bets, and the last 30 to show the first movement.

How to present outcomes to executives who want dates

Executives and clients usually ask "when will it ship?" Answer in three parts. Give the outcome and its deadline, which is a date. Show the current bets underneath so the work feels concrete. Then show the fixed-commitment lane with the dates that cannot move.

Outcome based does not mean date-free. It means dates go only where they are truly needed. This approach is a poor fit when most of your work is contractual or regulatory with fixed scope. In that case, keep a delivery plan and add outcomes only where you have freedom. Be honest about the other drawbacks too. Plans can become too fluid if nobody holds the stop rules. Broad goals can be hard to break down into outcomes a team can move. The roadmap takes more time to maintain because metrics need regular checks. And if one metric becomes the only focus, real user needs can slip out of view.

Common mistakes to avoid

  • Writing outcomes as disguised features, like "Launch integrations," hides the goal, so describe the user behavior you want to change instead.
  • Setting a target without a baseline makes progress impossible to judge, so measure the current value first.
  • Choosing lagging metrics like annual revenue hides progress for months, so pick leading indicators that move within weeks.
  • Listing ten outcomes per quarter kills focus, so cap it at three to five per team.
  • Committing to a single solution per outcome removes flexibility, so keep a backup bet ready.
  • Hiding the bets from stakeholders makes the roadmap feel vague, so show them clearly under each outcome.

Frequently asked questions

What is an outcome based roadmap?

It is a roadmap built around measurable changes in user or business behavior, not around a list of features. Each outcome has a metric, a baseline, a target and an owner. Features appear underneath as bets that might move that metric.

How do you create an outcome based roadmap?

Start from the strategic goal, then audit your current feature list and group items by intent. Turn each group into an outcome with a metric, baseline, target and deadline. List bets for each outcome, publish the roadmap in Now, Next and Later columns, and review the metrics every two weeks.

Can an outcome based roadmap include dates?

Yes. Each outcome has a deadline, usually the end of the quarter. Hard external dates like contracts or compliance go in a separate fixed-commitment lane, so everyone knows which dates are firm and which items are flexible bets.

How does outcome based planning relate to OKRs?

They fit together. The objective sets the direction, the key results act as the outcome metrics, and the roadmap shows the bets made to hit them. Many teams use their quarterly key results directly as the outcome rows.

How many outcomes should a team have per quarter?

Three is a practical default for one team, and five is a sensible upper limit. Beyond that, effort spreads too thin and you cannot tell which work moved which metric. If leadership wants more, rank them and work on the top ones first.

Generate this roadmap with AI