The Founder's Guide to Quarterly Planning: How to Run a Two-Day Cycle That Aligns the Company, Kills Zombie Projects, and Ships What Actually Matters
Most startups plan in one of two broken ways. Either they run a chaotic all-hands where the CEO announces the next quarter's priorities on a Friday, or they build a bloated OKR process that takes three weeks, produces a spreadsheet no one opens, and ends with the same work getting done that would have been done anyway.
Neither works. The first produces surprise and misalignment. The second produces theater.
There is a better way: a two-day quarterly planning cycle that forces honest tradeoffs, kills zombie projects, and ends with every function knowing exactly what they own for the next 90 days. This guide is how to run it.
Monthly is too short. Real work in a startup takes 6–12 weeks to ship and see signal from. Monthly plans devolve into task lists.
Annual is too long. The market moves faster than your plan can. Any annual plan is a lie by month four.
Quarterly is the natural rhythm of startup work: long enough to ship something meaningful, short enough to reset without shame.
Planning fails when it starts cold. Two weeks out, distribute three artifacts:
1. Last quarter''s scorecard. What did we commit to. What did we ship. What did we miss. Written honestly, not defensively. 2. Function memos. Each function lead writes a 2-page memo: current state, top 3 problems, proposed priorities for next quarter, resources needed. Memo, not slides. 3. The customer and market update. What has changed in the market, in the competitive set, in customer behavior. This is the CEO''s memo.
Everyone reads all three before day one. No one presents them in the room.
The mistake most planning off-sites make is jumping straight to "what should we do." That produces a wish list. The right first move is diagnosis: what is actually true about the business right now.
Morning (3 hours): Metric review. Not a dashboard walk. A structured conversation: what surprised us, what did we predict correctly, what do we still not understand.
Afternoon (3 hours): The problem tree. On a whiteboard, write the top 5 problems the business faces. Under each, write the underlying causes. Under each cause, write what would need to be true to fix it.
By end of day one, the room agrees on the problems. Not the solutions. The problems.
Day two is where most teams fail. They arrive with too many ideas and no forcing function to cut them.
Morning (3 hours): Each function proposes 3 priorities. The full leadership team stress-tests them: is this the highest-leverage work, does it depend on another team, what does it cost, what does it displace.
Midday (1 hour): The kill list. Every project currently in flight that is not on the priority list gets an explicit decision: continue, kill, pause, transfer. Zombie projects — the ones no one loves but no one has killed — die here. This is the single most valuable hour of the two days.
Afternoon (3 hours): Commitments. Each function walks out with 3–5 priorities, each with an owner, a measurable outcome, a due date, and a named dependency list.
If it does not fit on one page per function, you have too many priorities.
Weekly: Each function lead posts a 5-bullet update against the priorities. No status meeting.
Monthly: 90-minute leadership review. Red/yellow/green on each priority. Reallocate if needed.
Mid-quarter: Explicit checkpoint. Kill or double down on any priority that is off track.
End-of-quarter: The scorecard for the next planning cycle writes itself.
1. Memos, not decks. Slides hide bad thinking. Memos expose it. 2. Kill before you add. Every new priority displaces something. Name what. 3. Three per function, max. If you have five priorities, you have zero. 4. Named owners. "The team" is not an owner. A person is. 5. Measurable outcomes. "Improve onboarding" is not an outcome. "40% activation in 7 days" is.
The CEO monologue. Founder arrives with the plan already written. Everyone else disengages.
The performance review dressed as planning. Blame instead of diagnosis.
The perfect document. Three weeks polishing OKRs while the quarter starts without a plan.
The forgotten plan. No weekly rhythm, no mid-quarter checkpoint. The plan is written, filed, and never referenced again.
Six weeks into the quarter, any employee can answer three questions in 30 seconds: what are the company''s top priorities, what are my function''s top priorities, and how does my work this week ladder to them. If they can, the plan is working. If they can''t, no amount of documentation will save it.
Quarterly planning is not a spreadsheet exercise. It is the leadership team''s single most important act of clarity. Two days, done well, buys you 90 days of focus. That is the trade.
