Skip to main content

​
Overview

Scenarios let you create branched versions of your roadmap to explore alternative plans without changing the source of truth. Use them for “What-if” planning, stakeholder presentations, or comparing different strategic directions.
Scenarios Overview

​
How Scenarios Work

A scenario is a branched copy of your roadmap data. When you create a scenario:
  • Items in the scenario are independent copies — changes don’t affect your main roadmap
  • The scenario uses the same workspace structure (Products, Goals, Priorities)
  • You can switch between your main roadmap and scenarios at any time
Think of scenarios like Git branches for your roadmap. Experiment freely, then keep what works.

​
Creating a Scenario

1

Open the Scenario Switcher

Click the roadmap name or scenario dropdown in the toolbar to open the switcher.
Scenario Switcher
2

Create a New Scenario

Click New Scenario and give it a descriptive name (e.g., “Q2 — Aggressive Timeline” or “Option B: Mobile First”).
3

Start Planning

Your scenario opens with a copy of the current roadmap items. Make changes freely — move dates, reprioritize items, add or remove work.

​
Switching Between Scenarios

Use the Scenario Switcher to navigate between your main roadmap and any active scenarios:
  • Main Roadmap — Your source of truth, shared with the team
  • Scenarios — Independent branches for exploration
Switching Scenarios
The active scenario is always shown in the toolbar so you know which version you’re viewing.

​
Use Cases

​
Strategic Planning

Compare different strategic directions side by side:
  • Option A: Focus on enterprise features
  • Option B: Prioritize mobile experience
  • Option C: Balance both with a phased approach

​
Timeline Exploration

Test different timelines to understand trade-offs:
  • What if we push the launch by 2 weeks?
  • What if we cut scope to hit the original date?
  • What if we add resources to the critical path?

​
Stakeholder Presentations

Prepare multiple roadmap options for leadership review:
  • Create a scenario for each proposal
  • Present them independently
  • Adopt the approved direction into the main roadmap

​
Risk Assessment

Model “what happens if” scenarios:
  • A key dependency is delayed
  • A team member leaves
  • Requirements change mid-quarter

​
Managing Scenarios

​
Renaming a Scenario

Click on the scenario name in the switcher to rename it. Use descriptive names that communicate the intent (e.g., “Conservative Timeline” vs. “Scenario 2”).

​
Deleting a Scenario

When you no longer need a scenario, delete it from the scenario switcher. This permanently removes the branched items. Your main roadmap is unaffected.
Deleting a scenario cannot be undone. The branched items are permanently removed.

​
Best Practices

Use descriptive names that communicate the “what-if” being explored, like “Q2 — Mobile First” rather than “Scenario 1”.
Each scenario should explore a single question or alternative. Too many changes in one scenario make it hard to compare.
Clean up stale scenarios periodically. If a scenario hasn’t been updated in weeks, it’s probably no longer relevant.
Scenarios are perfect for preparing stakeholder meetings — create one per option and present them as distinct alternatives.

Saved Views

Configure different perspectives on your roadmap.

Share Links

Share specific roadmap views with stakeholders.