Run a rolling roadmap quarterly re-plan

Rolling Roadmaps Survive Contact With Reality

Annual roadmaps die at the first OKR miss or market shift — and then the team spends Q2 pretending the Q1 plan is still valid. Atlassian's OKR and agile planning writing argues that rolling planning — fixed strategy, rolling execution — is the only cadence that survives contact with reality. Reforge's product strategy research makes the same point: strategy pillars should be durable (18-36 months), execution plans should refresh quarterly.

How the Run a rolling roadmap quarterly re-plan Prompt Works

The prompt separates strategy pillar drift from execution re-planning so the team does not rewrite strategy every quarter, audits last quarter before planning next, and uses three commitment levels (committed / planned / directional) so stakeholders know what they can bet on. The "one assumption we'd bet against" output surfaces the highest-risk item for the next quarter.

When to Use It

• Quarter end is 2-3 weeks away.
• An annual roadmap has obvious gaps after one quarter.
• A new PM inherits an outdated plan.
• Leadership is asking for refreshed 6-month commitments.
• Teams are confused about what is firm vs. tentative.

Common Pitfalls

• Rewriting strategy every quarter. Durable pillars are the point. Re-write execution, keep pillars.
• No audit of last quarter. Re-planning without audit means the same patterns repeat. Audit first.
• Committing all three quarters. Q+3 commitments are theater. Use directional labels so surprises don't break trust.

Sources

• OKRs — Atlassian
• The Product Strategy Stack — Reforge
• Agile Metrics — Atlassian
• Google re:Work — Google