Planning Cadence Optimization
Align long-term strategy with short-term execution through structured, tiered planning rituals.
The Guide
5 key steps synthesized from 6 experts.
Set the Strategic North Star
Identify 6 to 10 strategic bets or boulders at the leadership level each year to frame investments. Document these in a narrative format that covers the product's state and success indicators while connecting them to customer scenarios.
Featured guest perspectives
"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."— Lenny Rachitsky
"The yearly company OKRs define our biggest strategic bets and highest-priority investments for the next year. ... Our Strategy and Biz Ops team leads the coordination for the yearly company OKR process. It takes us one to two months from the first draft to getting to finalized yearly company OKRs."— Lenny Rachitsky
"The annual plans are generally structured as a six-pager that captures the overall state of the product, goals, measurable success indicators over the coming fiscal year, and a set of customer scenarios that we focus on in relation to the big boulders."— Lenny Rachitsky
Implement a Tiered Resolution Approach
Detail specific projects and prioritization for the immediate quarter to maintain operational rigor. For future quarters, use high-level bullet points to leave room for strategic flexibility as new information emerges.
Featured guest perspectives
"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."— Lenny Rachitsky
"Themes once a year, which gets translated into a six-month plan, and then there are four six-week cycles inside each half."— Lenny Rachitsky
Adopt a Structured Planning Framework
Use the W or M framework to structure the back and forth between leadership and pods. This ensures top-down strategic alignment meets bottom-up tactical feasibility through multiple passes and feedback loops.
Featured guest perspectives
"The annual process works along a “W” shape, similar to the framework Lenny suggested here. It starts at the top, with the Gong management team setting up top company priorities—usually three or four. Based on these priorities, product and engineering determine the capacity for the different products and product areas."— Lenny Rachitsky
Maintain Weekly Operational Momentum
Bridge the gap between quarterly goals and daily work by asking teams every Monday what they are doing this week to get closer to goals. Use lightweight rituals like two-week sprints or weekly focus practices to ensure execution.
Featured guest perspectives
"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..."— Christina Wodtke
"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."— Lenny Rachitsky
Adapt Cadence to Organizational Maturity
Evolve your planning horizons from fast, two-week sprints in the pre-product-market fit stage to quarterly roadmaps as the team grows. Shield high-performing teams from unnecessary process friction while maintaining overall standards.
Featured guest perspectives
"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."— Eeke de Milliano
Get this guide as an AI skill for Claude Code
Install This Skill
Add this skill to Claude Code, Cursor, or any AI coding assistant that supports Agent Skills.
Quick Install (Recommended)
Install this skill directly using npx:
npx skills add RefoundAI/lenny-skills --skill planning-cadenceOr install all 76 skills:
npx skills add RefoundAI/lenny-skillsManual Installation
Download the skill
Download Skill (.zip)Add to your project
Create a folder in your project root and add the skill file:
.claude/skills/planning-cadence/SKILL.mdStart using it
Claude will automatically detect and use the skill when relevant. You can also invoke it directly:
Help me with planning cadence optimizationOr receive these install instructions in your inbox:
Guest Perspectives
Deep dive into what 5 podcast guests shared about planning cadence optimization.
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..."
- Ask every Monday: 'What am I doing this week to get closer to our goals?'
- Raise your head above the noise of daily operations to ensure current tasks align with mission and strategy.
- Utilize temporal landmarks like Mondays or the start of a quarter to reset attention and commitment.
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."
- Identify high performers and creative thinkers who do not need formal process to do their best work and shield them from unnecessary friction.
- Introduce formal structures only when the risk of organizational variance outweighs the cost of reduced individual autonomy.
- Acknowledge that scaling a company requires more process to ensure a baseline standard across a larger, more diverse workforce.
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."
- Cap the development cycle for any individual feature at a maximum of six weeks to ensure delivery.
- Assign exactly one programmer and one designer to each project to minimize communication overhead and meetings.
- Avoid 'whale' customers that require custom features and massive support infrastructures which distract from a single code base.
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."
- Adopt a rolling 12-month roadmap that is updated every six months to balance long-term vision with short-term confidence.
- Establish a nested metric structure across pillars and areas to ensure every team's success is tied to the broader product strategy.
- Organize teams around durable problem spaces and target customers rather than static feature sets to ensure roadmaps remain outcome-focused.
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."
- Prioritize securing stakeholder alignment on a real product strategy months before formal planning cycles begin.
- Bend or break rules around mandatory templates if they do not add actual value to your decision-making.
- Collapse planning timelines from weeks to days by focusing on strategic pillars rather than ritualized artifacts.
Make your product team AI-native
These skills work best as a system. Get a free 8-email course: map how your team works today, wire agents into real workflows, and make it stick. From the team that does this for a living.
Related Skills
Other Planning & Prioritization skills you might find useful.
Roadmap Prioritization
Prioritizing 'lovability' over mere viability ensures that early product versions generate the organ...
View Skill → →Goal Setting and OKRs
Measuring success through absolute volume rather than conversion percentages prevents teams from art...
View Skill → →High Stakes Decision Making
You can effectively shorten long-term feedback loops by identifying and measuring intermediate signa...
View Skill → →Evaluating Trade-Offs
High-velocity teams avoid the binary choice of building or buying by using SaaS for core functionali...
View Skill → →