Quick Framework

Quarterly planning happens in three phases:

  1. Review: What happened last quarter? Did features ship on time? Did they move the business needle?
  2. Prioritize: Using framework of choice (RICE, CoD, Kano), decide: What ships this quarter?
  3. Commit: Lock the roadmap. Communicate it. Measure against it.

Actionable Steps

1. Schedule 2-Day Planning Session Quarterly

Day 1: Review + analysis Day 2: Prioritization + commitment

2. Invite Product, Engineering, Leadership

Diverse perspective prevents blind spots.

3. Lock Roadmap; Don't Add Mid-Quarter

Additions happen, but they mean deletions. Strict "in/out" discipline.

Key Takeaways

  • Quarterly rhythm creates predictability. Customers know when to expect updates. Team knows sprint targets.
  • Lock the roadmap to prevent drift. Addition without deletion = expanding scope = missing deadlines.

The Three-Phase Quarterly Planning Process

Phase 1: Pre-Work (2 weeks before planning session)

Collect data:

  • Feature shipping dates (were we on time?)
  • Engagement metrics (did features move the needle?)
  • Customer feedback (what's working? What's not?)
  • Technical debt assessment (what slowed us down?)
  • Market signals (what changed in competitive landscape?)

Document findings:

  • What shipped last quarter vs. plan (±5% target)
  • Which features drove business impact (revenue, retention, engagement)
  • Which features disappointed
  • What technical/organizational blockers emerged

Prepare options:

  • 5–10 feature/initiative options for next quarter
  • Estimated effort for each
  • Estimated impact

Phase 2: Planning Session (2 days)

Day 1 Morning: Review

  • CEO/leadership shares strategy (1 hour)
  • Product reviews last quarter's metrics (1 hour)
  • Engineering reviews blockers/velocity (30 min)
  • Team discusses: "What worked? What didn't?" (30 min)

Day 1 Afternoon: Prioritization

  • Score features using framework (RICE/CoD/Impact-Effort)
  • Debate top 5 (1.5 hours)
  • Build preliminary roadmap
  • Identify risks/dependencies

Day 2 Morning: Finalization

  • Engineering refines effort estimates
  • Lock roadmap
  • Define success metrics for each initiative
  • Communicate inter-dependencies

Day 2 Afternoon: Commitment

  • Present roadmap to full org
  • Address questions
  • Get leadership buy-in
  • Schedule review cadence (weekly standups)

Phase 3: Communication & Tracking

Immediately after:

  • Document and share roadmap (public + internal versions)
  • Share with customers (Now-Next-Later format)
  • Kick off sprints

Weekly:

  • Status updates (on-track, at-risk, blocked)
  • Re-prioritization if blockers emerge

Mid-quarter:

  • Pulse check: "Are we hitting targets?"
  • Course-correct if needed

End-quarter:

  • Full retrospective
  • Start next quarter pre-work

Real-World Case Study: Quarterly Planning That Worked vs. Failed

The Company That Planned (Success)

Q1 Planning:

  • Spent 2 days in dedicated planning session
  • Reviewed Q4 metrics
  • Prioritized using RICE
  • Locked 10 features in "Now"
  • Communicated Now-Next-Later to customers

Result:

  • Q1 shipped all 10 features by day 3 of Q2 (on time)
  • Average feature impact: +2–5% engagement
  • Team morale high (clear expectations)
  • Customer satisfaction +8%

The Company That Didn't Plan (Failure)

Q1 Approach:

  • CEO had priorities. Communicated via email.
  • No dedicated planning session.
  • Roadmap was a living list (always changing)
  • Features added mid-quarter as requests came in

Result:

  • Q1 shipped 6 features (originally planned 10)
  • Team constantly context-switching
  • Engineer burnout (unclear priorities)
  • Customer satisfaction declined (unclear direction)
  • Revenue impact: No feature had measurable business impact

The Output Artifacts: What You Need to Document

After quarterly planning, you should have:

  1. Roadmap Document (Now-Next-Later with dates)
  2. RACI Matrix (who owns what)
  3. Success Metrics (how you'll measure each initiative)
  4. Dependency Map (which features block which)
  5. Risk Register (what could derail us)
  6. Customer Communication (external roadmap)

Anti-Patterns: Quarterly Planning Failures

Anti-Pattern 1: "Planning without data"

You plan based on gut feeling. No review of last quarter's metrics.

Result: You repeat mistakes. You don't learn from shipping success.

Fix: Pre-work. Collect data. Review metrics. Make evidence-based decisions.

Anti-Pattern 2: "Planning without engineering"

Product plans. Engineering wasn't involved. Now engineering says "This will take 2x longer than estimated."

Result: Mid-quarter crisis. Roadmap falls apart.

Fix: Involve engineering in planning. Effort estimates are their responsibility.

Anti-Pattern 3: "Not locking the roadmap"

You plan. Then mid-quarter, CEO adds "Just one more feature." Then sales requests a customer custom build. Scope expands.

Result: You ship 70% of planned features. Demoralizing.

Fix: Enforce: "Additions require deletions." Make trade-off explicit.

Prodinja Connection (Updated)

Quarterly planning only works if the prioritization behind it can survive being challenged in the room. Prodinja's RICE scoring tool is designed to let your team score every roadmap candidate together — reach, impact, confidence, effort — and watch the ranking re-sort live as people push back on an estimate, instead of re-litigating the same argument for the third time. Kano tagging alongside those scores can help separate the features that are genuinely table-stakes from the ones a stakeholder is just advocating hardest for. You can walk out of the two-day session with a roadmap ranked by something more durable than whoever spoke last, and a record of the inputs everyone agreed to — so next quarter's planning starts from a shared baseline instead of from scratch.

Key Takeaways (Updated)

  • Quarterly planning requires pre-work, a dedicated session, and post-planning discipline. Rushed planning produces wish lists, not war plans.

  • Lock the roadmap and enforce trade-offs. Additions mid-quarter must mean deletions. Strict discipline prevents scope creep.

  • Track execution weekly and review quarterly. You plan, you execute, you learn. The cycle repeats.

  • Involve product, engineering, and leadership. Diverse perspectives prevent blind spots and improve commitment.

  • Adapt your planning process based on what works. First quarter might be messy. By Q4, you've refined the cadence and process.

The Three-Phase Quarterly Planning Process

Phase 1: Pre-Work (2 weeks before planning session)

Collect data:

  • Feature shipping dates (were we on time?)
  • Engagement metrics (did features move the needle?)
  • Customer feedback (what's working? What's not?)
  • Technical debt assessment (what slowed us down?)
  • Market signals (what changed in competitive landscape?)

Document findings:

  • What shipped last quarter vs. plan (±5% target)
  • Which features drove business impact (revenue, retention, engagement)
  • Which features disappointed
  • What technical/organizational blockers emerged

Prepare options:

  • 5–10 feature/initiative options for next quarter
  • Estimated effort for each
  • Estimated impact

Phase 2: Planning Session (2 days)

Day 1 Morning: Review

  • CEO/leadership shares strategy (1 hour)
  • Product reviews last quarter's metrics (1 hour)
  • Engineering reviews blockers/velocity (30 min)
  • Team discusses: "What worked? What didn't?" (30 min)

Day 1 Afternoon: Prioritization

  • Score features using framework (RICE/CoD/Impact-Effort)
  • Debate top 5 (1.5 hours)
  • Build preliminary roadmap
  • Identify risks/dependencies

Day 2 Morning: Finalization

  • Engineering refines effort estimates
  • Lock roadmap
  • Define success metrics for each initiative
  • Communicate inter-dependencies

Day 2 Afternoon: Commitment

  • Present roadmap to full org
  • Address questions
  • Get leadership buy-in
  • Schedule review cadence (weekly standups)

Phase 3: Communication & Tracking

Immediately after:

  • Document and share roadmap (public + internal versions)
  • Share with customers (Now-Next-Later format)
  • Kick off sprints

Weekly:

  • Status updates (on-track, at-risk, blocked)
  • Re-prioritization if blockers emerge

Mid-quarter:

  • Pulse check: "Are we hitting targets?"
  • Course-correct if needed

End-quarter:

  • Full retrospective
  • Start next quarter pre-work

Real-World Case Study: Quarterly Planning That Worked vs. Failed

The Company That Planned (Success)

Q1 Planning:

  • Spent 2 days in dedicated planning session
  • Reviewed Q4 metrics
  • Prioritized using RICE
  • Locked 10 features in "Now"
  • Communicated Now-Next-Later to customers

Result:

  • Q1 shipped all 10 features by day 3 of Q2 (on time)
  • Average feature impact: +2–5% engagement
  • Team morale high (clear expectations)
  • Customer satisfaction +8%

The Company That Didn't Plan (Failure)

Q1 Approach:

  • CEO had priorities. Communicated via email.
  • No dedicated planning session.
  • Roadmap was a living list (always changing)
  • Features added mid-quarter as requests came in

Result:

  • Q1 shipped 6 features (originally planned 10)
  • Team constantly context-switching
  • Engineer burnout (unclear priorities)
  • Customer satisfaction declined (unclear direction)
  • Revenue impact: No feature had measurable business impact

The Output Artifacts: What You Need to Document

After quarterly planning, you should have:

  1. Roadmap Document (Now-Next-Later with dates)
  2. RACI Matrix (who owns what)
  3. Success Metrics (how you'll measure each initiative)
  4. Dependency Map (which features block which)
  5. Risk Register (what could derail us)
  6. Customer Communication (external roadmap)

Anti-Patterns: Quarterly Planning Failures

Anti-Pattern 1: "Planning without data"

You plan based on gut feeling. No review of last quarter's metrics.

Result: You repeat mistakes. You don't learn from shipping success.

Fix: Pre-work. Collect data. Review metrics. Make evidence-based decisions.

Anti-Pattern 2: "Planning without engineering"

Product plans. Engineering wasn't involved. Now engineering says "This will take 2x longer than estimated."

Result: Mid-quarter crisis. Roadmap falls apart.

Fix: Involve engineering in planning. Effort estimates are their responsibility.

Anti-Pattern 3: "Not locking the roadmap"

You plan. Then mid-quarter, CEO adds "Just one more feature." Then sales requests a customer custom build. Scope expands.

Result: You ship 70% of planned features. Demoralizing.

Fix: Enforce: "Additions require deletions." Make trade-off explicit.

Prodinja Connection (Updated)

Quarterly planning only works if the prioritization behind it can survive being challenged in the room. Prodinja's RICE scoring tool is designed to let your team score every roadmap candidate together — reach, impact, confidence, effort — and watch the ranking re-sort live as people push back on an estimate, instead of re-litigating the same argument for the third time. Kano tagging alongside those scores can help separate the features that are genuinely table-stakes from the ones a stakeholder is just advocating hardest for. You can walk out of the two-day session with a roadmap ranked by something more durable than whoever spoke last, and a record of the inputs everyone agreed to — so next quarter's planning starts from a shared baseline instead of from scratch.

Key Takeaways (Updated)

  • Quarterly planning requires pre-work, a dedicated session, and post-planning discipline. Rushed planning produces wish lists, not war plans.

  • Lock the roadmap and enforce trade-offs. Additions mid-quarter must mean deletions. Strict discipline prevents scope creep.

  • Track execution weekly and review quarterly. You plan, you execute, you learn. The cycle repeats.

  • Involve product, engineering, and leadership. Diverse perspectives prevent blind spots and improve commitment.

  • Adapt your planning process based on what works. First quarter might be messy. By Q4, you've refined the cadence and process.