A quarter fits in one afternoon, if you stop planning nine things
Most quarterly plans are a list of hopes with a date at the bottom. Here is the three hour version that ends with fewer things on it, and a reason to believe each one.
The UnaTask team, Building UnaTask. Mar 8, 2027. 6 min read.
It is the first Monday of the quarter. There is a document called Q2 plan, it has nine headings, and every one of them is something you genuinely want. A new pricing page. The onboarding rewrite. The partner program. Two hires. A tidier invoicing process. Everyone agreed on it in a meeting that ran long, and it felt good, because a list of good ideas always feels good.
Thirteen weeks later, two of the nine are done, three are half done, and four were never started. Nobody was lazy. The plan simply never asked the one question a plan exists to ask: does this fit?
What a list of nine actually costs
A quarter plan that does not fit is worse than no plan at all, because it does two quiet kinds of damage. The first is that it spreads the team thin. With nine priorities, everything moves a little and nothing moves enough to ship, so at the end you have nine things at forty percent, which is worth less than three things at a hundred.
The second is that it trains everyone to ignore the plan. When the list is obviously impossible by week four, people stop reading it and go back to working on whatever is loudest. The plan becomes a document you mention in the review and nowhere else.
And the gap is not small. In a well known 1994 study, students guessed they would finish their thesis in 33.9 days. It took 55.5 on average, later than even their own worst case guess. A quarter is that same guess, made thirteen times over and about several things at once.
The turn: plan the hours, not the ideas
The fix is to plan a quarter the way you would plan a week: start from the time you really have, and only then decide what goes in it. It sounds obvious. Almost nobody does it, because counting hours is less fun than writing headings.
A quarter plan is not a list of what you want. It is a decision about what you will not do, written early enough to matter.
Give it one afternoon, about three hours, with the calendar for the next thirteen weeks open. Here is how the afternoon goes.
How the afternoon works
First hour: count the real weeks. Thirteen weeks on paper is rarely thirteen in practice. Take out the holidays, the conference, the week the whole team is at the offsite, and one more week for the things that always happen and never get planned. Most teams land on about eleven. Then take the hours each person can really plan in a week, after meetings and after the room you keep for surprises. If you did the weekly version of this, you already know the number. Twenty is common. Eleven weeks at twenty hours is 220 hours per person.
Now the uncomfortable part. Not all of that belongs to the big things. The normal work, the support, the small fixes, the invoices, will take its share whatever you write down. Promise sixty percent to the quarter and let the rest absorb the ordinary. That is roughly 130 hours per person for the things that are supposed to change the business.
Second hour: three outcomes, written as finished sentences. Not projects, outcomes. "Work on pricing" is a project. "By 30 June, the new pricing is live and the old plans are retired" is an outcome. The sentence form matters because it tells you when you are done, and it exposes the vague ones immediately. If you cannot finish the sentence, the thing is not ready to be a priority yet.
Then put a rough size on each, in hours, and add them up. This is the moment the plan tells the truth. If three outcomes need 300 hours and you have 130, you do not have a scheduling problem. You have two outcomes too many, or one outcome too big. Cut until it fits, and write the cut ones on a separate list called not this quarter. That list is the most valuable page you will write all afternoon, because it is the one that lets people say no in week six without an argument.
Third hour: lay them on a timeline, staggered. Three outcomes started on the same Monday all finish late on the same Friday. Stagger them instead: one starts now, one starts when the first is past its hardest part, one finishes in the last month. Give each a checkpoint roughly every four weeks, something you could show someone. Then book only the first two weeks as real blocks on the calendar. The rest stays as dates on the timeline, because a plan that books thirteen weeks of blocks on day one is a plan you will rebuild by week three.
- Count the real weeks, and the hours in each. About 220 per person is typical, 130 of them for the big things.
- Three outcomes, each a sentence with a date in it.
- Size and cut until the total fits, and keep the not this quarter list.
- Stagger them on a timeline, a checkpoint every four weeks.
- Book the first two weeks only. The rest stays a date until it gets close.
The same Monday, thirteen weeks later
Run the quarter again. The document has three sentences on it and a short list of things that are explicitly not happening. In week five somebody proposes a partner program, and instead of a debate, you point at the list. It is already there, with a note: next quarter. In week eight one outcome is behind, and you can see it, because its checkpoint came and went, and you have five weeks rather than five days to decide what to do about it.
At the review, three things shipped. That is fewer than nine. It is also three more than usually ship, and everyone knows exactly why the other six did not.
The bigger idea
A week, a day and a quarter all fail the same way: they are built for the time you wish you had rather than the time you do. The unit changes, the arithmetic does not. Count the hours first, fill them second, and put the leftovers on a list with a name, so saying no becomes something the plan does for you.
The quarter is decided in an afternoon and lived one week at a time. This is the one page we use for the week. Free, no email. Get the weekly plan sheet