Most quarterly plans are written by optimists and executed by people who are already full. The plan lists eleven initiatives, the team nods, and then normal work resumes and consumes every available hour. Twelve weeks later, two of the eleven happened, both of them the ones that had a deadline attached from outside. That is not a discipline problem. It is a planning method that never accounted for the work that was already there.
Why quarterly plans do not survive week two
A plan that ignores existing commitments is a wish list. In most small organizations, the recurring work, the client obligations, the events, and the admin already consume seventy to eighty percent of the available hours before anyone plans anything new. The remaining twenty percent is the entire capacity for change, and quarterly plans routinely allocate three times that.
The second failure is that everything on the list is genuinely worth doing. That is exactly what makes prioritization hard and exactly why it cannot be avoided. Choosing between good and bad is easy. Choosing between eight good things, knowing you can fund two, is the actual job.
The third failure is that nothing is ever removed. New initiatives are added on top of the existing operating load year after year, and the accumulated weight is the real reason everything feels urgent.
Start by counting what is already spoken for
Before choosing a single priority, work out how many hours you actually have. This is unglamorous and it is the step that makes the difference between a plan and a hope.
- Take the raw hours. People, times weeks in the quarter, times realistic working hours. Then remove leave, holidays, and known absences. Start with a real number rather than a theoretical one.
- Subtract the operating load. Recurring delivery, client work, the weekly event, support, admin, meetings. If nobody knows this number, estimate it high. Every organization that measures it discovers it was larger than they thought.
- Subtract a disruption allowance. Fifteen to twenty percent for the things that always happen and are never planned: an emergency, a departure, a system failure, a client crisis. A quarter with no allowance is a quarter that fails on the first surprise.
- What remains is your change budget. That number, usually much smaller than expected, is what you have to spend on anything new. It is the constraint that makes the priority conversation honest.
Teams that do this for the first time typically find they have a fraction of the capacity they were planning against. That discovery is uncomfortable and it is the most useful output of the exercise.
Three priorities, no more
Three is not arbitrary. It is roughly the number of significant changes a small team can hold in mind alongside their operating work. Five becomes a list; eight becomes decoration.
- Each priority gets an owner, not a committee. One name. Shared ownership is where quarterly initiatives go to stall quietly.
- Each priority gets an hours estimate. Compared against the change budget. If the three add up to more than you have, you have two priorities, not three.
- Each priority gets a done statement. A sentence that describes what will be true at the end. “Improve onboarding” is not a done statement. “Every new client is set up within two business days using a documented checklist” is.
- Each priority gets a first step scheduled in week one. Initiatives that have not started by week three almost never finish, because the quarter fills in behind them.
- Everything else is explicitly named as not this quarter. Written down and visible. The parked list is what stops good ideas from being re-litigated every week.
A quarterly plan without a list of what you are not doing is not a plan. It is an inventory of everything anyone mentioned.
Decide what to stop
This is the step almost everyone skips, and it is the one that makes room. If the change budget is genuinely full, the only way to add something is to remove something. Look at these categories specifically.
| Candidate | Question to ask | Typical outcome |
|---|---|---|
| A recurring meeting | What decision does it make? | Halve the frequency |
| A report nobody references | Who read the last one? | Stop producing it |
| A low-attendance program | Would we start it today? | Retire or merge |
| A manual process | Why is a person doing this? | Automate or template it |
| A tool with one user | What breaks if it goes? | Consolidate |
Removing one weekly meeting that involves six people returns roughly seventy hours across a quarter. That is often larger than the entire change budget you were fighting over, and it is available immediately.
Handle urgency without abandoning the plan
Urgent things will arrive. The plan does not fail because of them, it fails because there is no agreed way to absorb them, so each one silently displaces planned work and nobody notices until the quarter is over.
- Make displacement explicit. When something urgent is accepted, name what it pushes out. Both facts go on the record. This turns an invisible drift into a visible decision.
- Use the disruption allowance first. That is what it is for. Only when it is exhausted does new work start displacing priorities.
- Distinguish urgent from loud. The genuine test is what happens if it waits two weeks. If the answer is nothing much, it is loud rather than urgent.
- Batch the small stuff. Small urgent requests do more damage through interruption than through hours. A weekly slot for them protects the rest of the week.
- Review displacements monthly. If the same source keeps displacing planned work, that is a structural problem to fix rather than a run of bad luck.
The rhythm that keeps it alive
A plan reviewed once at the end of the quarter is a document. A plan touched weekly is a system. Keep the cadence light enough that it survives a busy month.
- Weekly, 15 minutes. For each priority: on track, at risk, or blocked, and what happens this week. Nothing else. This is a status check, not a working session.
- Monthly, 45 minutes. Hours spent versus estimated, displacements accepted, and an honest call on whether all three priorities are still achievable. Cutting one in month two is a good decision, not a failure.
- End of quarter, 90 minutes. What finished, what did not, and why. Then plan the next quarter using the actual capacity numbers you just learned rather than the optimistic ones you started with.
- Carry forward deliberately. Unfinished priorities either become a priority again with a revised estimate, or they get parked. Rolling them forward automatically is how a plan quietly becomes a backlog.
The estimates get better every cycle, and that improvement is the real return. After a year of this, a team knows its actual change budget within a reasonable margin, which makes every subsequent plan more honest than the last.
Key takeaways
- Count the hours already spoken for before choosing priorities. The change budget is usually far smaller than expected.
- Three priorities, each with one owner, an hours estimate, a done statement, and a first step in week one.
- Write down what you are not doing this quarter. The parked list stops good ideas from being re-argued weekly.
- Make room by stopping something. One recurring six-person meeting is about seventy hours a quarter.
- When urgent work arrives, name what it displaces, and review displacements monthly for patterns.
Common questions
What if leadership hands us more than three priorities?
Present the capacity arithmetic rather than arguing about importance. Show the hours available, the operating load, and what each initiative would cost. The conversation shifts from whether things matter, where you will lose, to what gets funded, where the numbers do the work. Ask which three should be funded first and what happens to the rest.
How long should quarterly planning take?
Half a day for a small team, including the capacity count. If it takes longer, it has usually turned into a strategy discussion, which is a separate and less frequent conversation. Quarterly planning is about allocation, not direction.
Is a quarter the right length?
For most organizations, yes. It is long enough to finish something meaningful and short enough to correct. Highly seasonal organizations sometimes do better planning around their seasons instead, for example an academic year or a program cycle. The method is unchanged; only the boundaries move.
What if we do not know our operating load?
Estimate it high for the first quarter and measure roughly as you go. A simple weekly note of where time actually went, kept for one quarter, gives you a workable number. Waiting for precise data before planning is a common way to never start.
How does this work for volunteer-run organizations?
The same arithmetic applies with smaller and less reliable numbers. Estimate volunteer capacity conservatively, since availability fluctuates more than staff time, and put a larger disruption allowance in. One priority per quarter is often the honest answer for a volunteer team, and one finished priority beats three abandoned ones.
