Most annual planning is a budgeting ritual that produces a document no one uses. Most quarterly planning is either too tactical — a task list, not a plan — or too abstract: a vision deck that names possibilities but makes no commitments.

The failure is almost always the same: planning is treated as a communication exercise, not a resource commitment process.

The right question for any planning cycle is not "what do we want to do?" It's "given what we know now, what are we committing to — with how much of what resources — and what are we explicitly not doing as a result?"

Everything else is aspiration.

The Right Way to Run a Planning Cycle

A planning cycle that produces real commitments has four phases:

Phase one: review the last cycle honestly. Before you plan forward, look at the last cycle's commitments and completion rate. If you committed to thirty things and completed fifteen, your planning baseline is fifteen, not thirty. Planning from aspiration rather than from historical capacity is the most common and most avoidable planning error.

Phase two: name your real capacity. Not headcount. Not FTE. Actual shipping capacity, accounting for meetings, admin, interviews, PTO, maintenance work, and planned interruptions. This number is usually lower than anyone wants it to be. That's fine. Better to plan to real capacity and over-deliver than plan to aspirational capacity and under-deliver every quarter.

Phase three: allocate to the three buckets. Any plan that works has to allocate across:

  • Hygiene: the work that keeps the lights on (maintenance, tech debt, customer escalations, compliance)
  • Execution: the work that delivers on existing commitments
  • Investment: the work that improves the system or builds new capability

Most teams under-allocate hygiene and then wonder why investment and execution keep slipping. The hygiene bucket is not optional — it just doesn't feel urgent until it becomes a crisis.

Phase four: write the not-doing list. Explicitly. What are you choosing not to do this cycle? Why? What would have to be true for that to change? This is the most discipline-inducing part of the planning process, because it forces real tradeoffs rather than pretending everything is equally possible.

A useful not-doing list is concrete: "we are not rebuilding onboarding this quarter; we are not adding the analytics export customers keep asking for; we are not starting the mobile redesign." Then name the tradeoff: those two engineers are going to the billing migration, because the current billing system is now the constraint on every enterprise deal. That is a plan. "We'll try to make progress on both" is not.

The Default Planning Horizon

Most teams are comfortable planning quarterly because that's the organizational default. But the right planning horizon is determined by the work.

If your critical path items run eight to twelve weeks, quarterly planning makes sense — you have one to two cycles per quarter to adjust. If your critical path items run three to four weeks, you need monthly planning. If they're measured in days, you need weekly.

The organizational calendar is not a good substitute for a honest assessment of your actual cycle times.

The teams that run best have a clear sense of their planning horizon and don't let the organizational calendar override what the work actually requires.

Planning is not a ritual. It's a resource commitment process. Run it like one.