product-strategy

Roadmap Decision Brief

Helps product leaders and owners package competing options, constraints, and recommendations into a decision-ready document.

Open this workflow

Version 1.0.0

Inputs

- Decision Context
- Options and Tradeoffs
- Constraints and Deadlines

Output schema

- Decision Summary
- Options Reviewed
- Tradeoffs
- Recommendation
- Dependencies
- Risks
- Follow-up Questions

Downloadable assets

- Prompt pack (Markdown)
- Template definition (JSON)
- Decision review checklist

Overview

How this module works

Roadmap Decision Brief

Convert roadmap choices, constraints, and tradeoffs into a decision-ready product brief.

Best for

Quarter planning decisions
Scope tradeoff reviews
Investment or prioritization discussions
Leadership decision prep

Source material

Decision context
Options being considered
Tradeoffs, dependencies, and impact notes
Constraints or deadlines

What this workflow produces

Decision summary
Options reviewed
Tradeoffs
Recommendation
Dependencies
Risks
Follow-up questions

Why teams use it

It helps product leaders and owners package complex choices more clearly. Instead of scattered notes on tradeoffs and timing, the team gets one decision brief with explicit recommendation logic.

Instructions

Usage guidance

Instructions

Recommended workflow

Describe the decision in plain language before listing options
Capture the actual tradeoffs instead of forcing a clean answer too early
Include deadlines or commitment pressure if they affect the recommendation
Review the recommendation with a PM, PO, or leadership sponsor before final circulation

What good output looks like

The decision summary is easy to understand quickly
Options are compared in a structured way
Tradeoffs are explicit rather than implied
Risks and follow-up questions make uncertainty visible

Customization tips

Add customer or revenue context if leadership needs it
Add capacity assumptions when delivery constraints matter
Shape the recommendation tone to be more exploratory or more directive depending on the audience

Common mistakes

Writing a recommendation without showing the tradeoffs behind it
Treating missing information as certainty
Hiding dependency risk in a long narrative section

Assets

Export and packaging notes

Downloadable Assets

Markdown prompt pack
JSON template definition
Decision review checklist

Recommended channel adaptations

Notion: add headings for recommendation, rationale, and open questions
Email: place the recommendation and decision summary first
Decks: keep options and tradeoffs short enough for a leadership discussion slide

Notes

Use this workflow when the team needs a cleaner decision artifact, not just a meeting recap. It is especially useful when capacity, commitments, and customer timing all influence the choice.

Examples

Production examples built into this workflow.

Expansion strategy decision brief

Shows how a product owner can package competing roadmap options into a structured recommendation with explicit tradeoffs.

standardFlagship workflow example

Source input

Need a decision on whether the next quarter should prioritize admin analytics for procurement leaders or deeper vendor onboarding automation. Leadership wants a recommendation tied to customer impact, delivery complexity, and near-term renewals.
Option A: Admin analytics. Faster to explain to renewal-risk accounts, medium engineering effort, stronger exec visibility, but less direct day-one workflow improvement. Option B: Deeper onboarding automation. Higher implementation value for operations teams, larger engineering scope, more dependency on platform events, but stronger workflow stickiness.
Quarter planning closes Friday. Two enterprise customers are asking for better admin visibility before renewal discussions in six weeks.

Structured output

decision summary

A decision is needed on whether to prioritize admin analytics or deeper onboarding automation in the next quarter.

options reviewed

Option A - Admin analytics; Option B - Deeper onboarding automation

tradeoffs

Admin analytics offers faster executive value and supports near-term renewal conversations; Onboarding automation may create stronger long-term workflow value but requires more scope and dependency management

recommendation

Prioritize admin analytics next quarter because it better supports the renewal timeline and has lower delivery risk in the current planning window.

dependencies

Platform event availability for onboarding automation; Customer-facing renewal timeline for enterprise accounts

risks

Delaying onboarding automation may slow long-term workflow value creation; Prioritizing automation now may create delivery risk against the quarter-planning deadline

follow up questions

Can a smaller onboarding automation slice still fit behind the analytics work?; What minimum analytics view would satisfy the enterprise renewal conversations?

Capacity tradeoff review

A realistic strategy brief where team capacity, commitments, and dependency timing all need to be weighed together.

standardOperational scenario

Source input

The product owner needs to decide whether the team should use remaining quarter capacity for support-facing reporting improvements or for completing the saved views experience requested by customer success.
Reporting improvements reduce manual support investigation work and close a service pain point. Saved views directly support recurring account reviews for customer success, but require more UI polish and preference storage work. Both options compete for the same frontend capacity.
One frontend engineer is unavailable for half the month. Support leadership is asking for reporting relief this quarter. Customer success wants saved views before the annual account-planning cycle.

Structured output

decision summary

The team needs to choose between support-facing reporting improvements and completing the saved views experience within limited frontend capacity.

options reviewed

Support-facing reporting improvements; Saved views for customer success

tradeoffs

Reporting improvements may relieve operational pain faster; Saved views may create stronger planning value for customer success but require more UI and storage work

recommendation

Prioritize the support-facing reporting improvements first because they address a current operational pain point with tighter capacity constraints, then reassess saved views once frontend capacity stabilizes.

dependencies

Frontend capacity; Reporting data availability; Preference storage work for saved views

risks

Deferring saved views may disappoint customer success timing expectations; Taking on saved views now may increase delivery risk due to limited frontend availability

follow up questions

Can saved views be narrowed into a smaller exploratory slice?; What reporting improvement would create the biggest support impact in the current quarter?

Messy roadmap decision notes

messy

Source input

Need to decide if alerts or dashboard thing comes first maybe because leadership asking and ops also wants faster workflow
alerts maybe easier? dashboard more visible. not sure on capacity. someone said data team not ready.
quarter plan soon

Structured output

decision summary

A roadmap decision is needed, but the current notes do not provide enough clarity on impact, scope, or capacity to support a firm recommendation.

options reviewed

Alerts enhancement; Dashboard enhancement

tradeoffs

Alerts may be easier to deliver; Dashboard may be more visible to leadership; Data-team readiness is still unclear

recommendation

Do not make a final recommendation yet; first clarify the business impact, capacity, and dependency readiness for both options.

dependencies

Data-team readiness - unclear; Team capacity - unclear

risks

Choosing now could create avoidable planning risk because the options are not well defined

follow up questions

Which option solves the bigger current business problem?; What capacity is actually available this quarter?; Is the data dependency blocking one option more than the other?

Incomplete prioritization note

incomplete

Source input

Need priority call for onboarding improvements.
There are two options.

Structured output

decision summary

A priority decision is needed for onboarding improvements, but the source does not include enough detail to compare the available options.

options reviewed

Two options are referenced, but not described

tradeoffs

Tradeoffs not provided in the source material

recommendation

Do not recommend a direction until the options, impact, and constraints are documented more clearly.

dependencies

Unclear from source

risks

A low-information decision could create avoidable roadmap churn

follow up questions

What are the two options?; What business outcome does each option support?; What deadline or commitment is driving the choice?

Decision brief adapted for Notion strategy page

Shows how the decision brief can be reused in a collaborative planning document with recommendation and follow-up prompts.

channelNotion strategy adaptation

Source input

Need to decide whether to expand the renewal-risk workflow into shared team watchlists or stay with individual views for the next release.
Shared team watchlists increase collaboration and leadership visibility but require ownership rules and permission design. Individual views are faster to ship but may limit team-wide coordination.
Leadership wants the recommendation in next week's planning review. Engineering can support only one moderate-scope enhancement in the release.

Structured output

decision summary

A choice is needed between shared team watchlists and individual views for the next release.

options reviewed

Shared team watchlists; Individual views only

tradeoffs

Shared team watchlists improve collaboration and visibility but require more design complexity; Individual views are faster to deliver but offer less team coordination value

recommendation

Prioritize individual views in the next release unless leadership determines that team coordination is a higher immediate priority than speed to market.

dependencies

Permission and ownership design for shared watchlists; Release capacity for one moderate-scope enhancement

risks

Delaying shared watchlists may reduce team coordination value; Taking on shared watchlists now may introduce design risk and release delay

follow up questions

Would lightweight sharing satisfy the collaboration need?; How strongly does leadership value team-wide visibility in this release?