refoundai Planning Cadence Optimization
Align long-term strategy with short-term execution through structured, tiered planning rituals.
Help the user with planning cadence optimization using insights from 13 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Audit Cadence - Evaluate if your current planning frequency matches your company size and market volatility.
- Design Resolution - Determine which horizons require granular project detail and which should remain high-level strategic themes.
- Select Framework - Choose between W, M, or rolling cycles based on your organization's need for top-down versus bottom-up input.
- Refine Rituals - Implement weekly checkpoints to bridge the gap between quarterly goals and the immediate actions required to move metrics.
Core Principles
Strategy Before Rituals
Shreyas Doshi Live: "And the interesting I found is that because I had a real product strategy, not one of those fake ones, a real product strategy that I had gotten alignment on with everybody, my planning for this major product for Stripe took me like three days."
Efficient planning is a byproduct of having a real, pre-aligned product strategy rather than just completing bureaucratic rituals.
Weekly Momentum Over Deadlines
Christina Wodtke: "I would say, 'What am I doing this week to get closer to our goals?' If you could answer that question, you could give up all the OKR stuff, but if you just asked the question, 'What are we doing this week to get closer to our strategic goals, our longer term goals?' That is the very heart of it..."
Shift focus from distant deadlines to the immediate actions required this week to ensure current tasks move you toward strategic objectives.
Standardize for Variance Reduction
Eeke de Milliano: "Process, by definition, is variance reducing. You're introducing it, because you worry that the variance in your org is too high. You want people to sort of meet a certain standard. And the cost of that is obviously, while you are reducing the standard and bringing folks up to the average, you're also bringing other folks down to the average."
Implement processes specifically to reduce unacceptable variance in standards while shielding high-performers from unnecessary friction.
Enforce Strict Time-Boxes
Jason Fried: "We build products with two people at a time. So every feature we work on in Basecamp, or HEY, or whatever we're building is two people, one programmer, one designer, and they have a maximum of six weeks to deliver the feature that they're working on."
Capping development cycles at six weeks and using small, autonomous teams prevents bloat and maintains organizational momentum.
Rolling Cycle Flexibility
Paige Costello: "Before, we planned annually primarily. Now, we plan every six months, but for a rolling 12 months. So we have higher confidence in the immediate half, lower confidence in the following half, but we just plan every 12 months, every six months because it gives our business more confidence in what's coming and a better opportunity to align our go-to-market and product planning."
Transitioning to rolling planning cycles provides the flexibility to adapt to new information while maintaining long-term alignment.
Tiered Planning Resolution
From "How Notion builds product": "All that said, we roughly plan for each half, with differing resolutions for the two quarters. As an example, at the beginning of this year, we said for Q1, list out all of your projects in detail with a prioritization of the roadmap, and for Q2, just give some high-level bullet points of what you think you’ll be working on."
Detail specific projects for the immediate quarter while keeping the following quarter as high-level bullet points to allow for flexibility.
Big Boulder Alignment
From "How Snowflake builds product": "We spend a good bit of time on planning, and planning frequently, with both quarterly and annual planning cycles. I sometimes joke that if it’s been more than six weeks without some planning exercise, my email must not be working."
Establish a small set of high-level company priorities that all individual team plans must map back to for organization-wide alignment.
Templates & Frameworks
- Snowflake's Big Boulders Planning Framework (How Snowflake builds product) - A company-wide alignment framework where leadership identifies 6-10 'big boulders' annually, product areas create six-pager annual plans mapping to boulders, an
- The W Framework (The Secret to a Great Planning Process — Lessons from Airbnb and Eventbrite) - A four-step planning framework that structures the back-and-forth between leadership and teams during annual or quarterly planning. Named for the 'W' shape of r
- The 'M' Framework for Quarterly Planning (How Gong builds product) - A trimmed-down quarterly planning process shaped like the letter M, typically starting bottom-up from product pods when no new top-down guidance exists
- Half-Yearly Planning with Variable Resolution (How Notion builds product) - A planning approach where the company plans for a full half but with different levels of detail for each quarter
- 75% Weekly Goals (How Perplexity builds product) - A lightweight weekly planning ritual where each team member identifies their top priority and aims to complete 75% of it by end of week, keeping expectations re
- Planning Cadence Evolution by Company Stage (How Ramp builds product) - How to evolve your planning horizon as your company grows from pre-PMF to multi-product portfolio
- Snowflake Annual Product Plan (Six-Pager) (How Snowflake builds product) - The annual plan document structure each product area creates to align with company-level big boulders
- Rolling Six-Month Roadmap with Confidence Tiers (Varun Parmar) - A roadmap process that balances enterprise customer visibility needs with team agility through decreasing confidence levels over time
- Multi-Altitude Planning Cadence (How Figma builds product) - Figma's three-level planning structure: annual company priorities, half-year team roadmaps, and quarterly adjustments.
See references/artifacts.md for the full list with details.
Questions to Help Users
- "What is the current timeframe your teams use for planning and how often are these plans revisited?"
- "Do you have a documented strategy that teams align with before the formal planning process begins?"
- "How do you distinguish between high-level annual bets and granular quarterly tasks?"
- "At what stage of the planning process do senior leaders and individual teams provide their input?"
- "How do you handle high-performing teams that might feel slowed down by standardized planning rituals?"
- "How often do you adjust your roadmaps based on new market information or product performance data?"
Common Mistakes to Flag
- Planning without strategy - Rituals become empty bureaucratic exercises if they are not preceded by a clear and pre-aligned strategic direction.
- Fixed annual roadmaps - Rigidly following a yearly plan prevents teams from responding to new data or market shifts discovered mid-year.
- Uniform resolution - Attempting to plan the next quarter with the same level of detail as the current one leads to wasted effort on speculative tasks.
- Over-standardization - Forcing creative or high-performing teams into rigid processes can stifle their productivity and cause organizational friction.
Deep Dive
For all 17 sourced insights from 13 guests, see references/guest-insights.md
Related Skills
- Roadmap Prioritization
- Goal Setting Okrs
- High Stakes Decisions
- Evaluating Trade Offs