Roadmap Focus Toolkit
For when priorities are unclear.
- Time
- 45-75 minutes with Product + Engineering + Design.
- Who
- Product manager, engineering manager, design lead, and one operations/program partner.
- Decide now
- Decide what to keep, pause, and speed up this cycle.
- What it gets you
- A roadmap that fits the team you have, with the trade-offs and the paused work written down.
- What you leave with
- Published focus memo with not-doing list and escalation owners.
What to do at each pace
- • Do now in tighter conditions: Ship only the roadmap items that show customer value within six weeks; pause the rest.
- • Do now in easier conditions: Relax constraints only on bets with impact inside 90 days and a named owner checking in.
- • Go ahead when: Proceed when team load, critical dependencies, and review checkpoints are within plan.
- • Pause if: Stop adding scope when any team passes its agreed work-in-progress limit or funding pressure crosses the pause line.
- • Restart when: Reopen paused work after two improving weekly briefs or one month with funding pressure below the pause line.
By pace: When conditions say slow down, narrow the scope; when they say speed up, reopen adjacent options with a stop rule on each.
Prep checklist
- • List all in-flight initiatives with owner, stage, and expected customer impact.
- • Bring current team capacity assumptions (headcount, PTO, support/on-call load).
- • Identify any date commitments that cannot move without external impact.
Run sequence
Map
Objective: Make current commitments and hidden dependencies visible.
Prompts
- • Which initiatives consume the most critical path capacity?
- • Where does one delayed team block multiple outcomes?
Deliverable: Dependency heatmap across current quarter initiatives.
Prioritize
Objective: Choose what to keep, pause, or speed up under this week's guidance.
Prompts
- • Which item matters most in the next 90 days?
- • What can be paused with the smallest customer/regret impact?
Deliverable: Keep/Pause/Accelerate board with named owners.
Commit
Objective: Lock scope and communicate what will not happen this cycle.
Prompts
- • What are we explicitly saying no to this quarter?
- • Which trigger would cause us to re-open a paused stream?
Deliverable: Focus memo shared with leadership and execution teams.
Signs it worked
- • The quarter has a published "not doing" list that teams can reference.
- • Critical path dependencies are reduced or given explicit escalation owners.
- • Each team has a work-in-progress limit, reviewed weekly.
What's in this toolkit
Common mistakes to avoid
- • Adding projects without explicit trade-offs