The best format for a product roadmap session — outcome-first, not feature-first.

Most roadmap sessions fail because they start with features. Someone writes "redesign the onboarding flow" on a sticky note, and the next 90 minutes is spent debating whether that's Q2 or Q3 — while the underlying question (what metric are we trying to move, and why?) never gets asked.

Format 1 — Now/Next/Later (most common). Three columns on the whiteboard. Now = committed work this quarter. Next = high-confidence work next quarter. Later = directions we're confident in but haven't scoped. Outcomes live in the columns; features are sub-bullets under outcomes. The benefit: it communicates direction without false precision. A later item doesn't have a deadline, just a direction.

Format 2 — Opportunity/Outcome/Output. Three columns: Opportunity (customer problem), Outcome (metric we want to move), Output (what we'll build to create that outcome). This format forces the team to define success in metric terms before committing to a feature. Particularly useful when stakeholders push for specific features — mapping them back to an opportunity and outcome surfaces whether the feature is the right solution.

Format 3 — Opportunity Solution Tree (Teresa Torres). A branching diagram. The root is the desired outcome. First-level branches are opportunity areas (customer problems that would move the metric). Second-level branches are solution ideas for each opportunity. Third-level branches are experiments to test whether the solution is the right one. OST sessions take 2–3 hours and require more facilitation skill, but produce the clearest thinking about why a roadmap item should exist.

The roadmap session agenda.

1. State the product goal for the period (15 min) — what outcome is the roadmap meant to produce?
2. Review current themes and ongoing work (15 min)
3. Brainstorm opportunities — customer problems that would move the goal metric (20 min, silent writing)
4. Cluster and prioritize opportunities (20 min)
5. Map solutions to top opportunities (20 min)
6. Place solutions in Now/Next/Later columns (15 min)
7. Check for dependencies and conflicts (15 min)

What the output should be. A whiteboard with 3 columns, 3–5 items per column, each item an outcome with solution sub-items, each item with a named owner and a success metric. Not a Gantt chart. Not a feature list with dates.

Snap the roadmap whiteboard with BoardSnap. The AI reads the column structure, outcome items, and sub-features and produces a clean roadmap summary with action items per quarter.