How to Run a Quarter Like You Mean It

Two planning horizons get almost all the attention, and each is missing the thing the other has.

The annual plan has direction. It knows where you're trying to end up. It also has no urgency whatsoever, because in January, December is a rumor. Nothing about a twelve-month goal makes any particular Tuesday different.

The daily list has urgency and nothing else. Everything on it feels pressing, which is the problem: it can't tell you whether today mattered, only whether it was busy. String three hundred of those together and you can work hard all year without moving anything you'd have named in January.

Ninety days is where both resolve.

Why the quarter is the unit

Short enough that the end is always visible. From week one you can see the finish, which is the thing an annual goal never gives you.

Long enough to move something real. A month can produce activity, but most outcomes worth having don't respond inside four weeks. Ninety days will move a number you can actually score.

And frequent enough to correct four times a year. Miss a quarter and you've lost a quarter, not a year, and you get an honest look at why while the details are still fresh.

There's also a practical argument. Urgency and sustained effort both seem to peak somewhere around ten to twelve weeks. Beyond that a push stops being a push and turns into a condition.

The reframe is small and does a lot of work: stop asking what you'll do this year, and start asking what each of the four cycles is about. A quarter has a launch, an execution period, and a close. A month just ends. That's The 90-Day Window.

Set it up before day one

The most common failure isn't a bad quarter. It's a quarter that never got started properly, and by the time anyone notices, three weeks are gone and urgency has quietly made all the decisions.

The setup happens before the quarter begins. Decide what this cycle is about, cut the list to what will actually fit, and know what you're not doing. Two weeks vanish otherwise, and they vanish invisibly, because the first weeks of a quarter feel productive no matter what's in them.

Then the middle is for execution and the last week is for the close. Skip the close and every following quarter is worse, because you've thrown away the only data you had.

The close is an hour and four questions: what got hit, what didn't, what the scores say about how well the targets were calibrated, and what carries forward. It gets skipped because by week thirteen you're tired of the quarter and the next one is more interesting. The cost arrives later. Without a close, the following quarter's targets get set from memory and optimism, which is how a planning practice drifts from honest to decorative over the course of a year.

Write it down so it can be scored

A quarter with a theme and no numbers is a feeling. This is where the second piece comes in.

Andy Grove built the practice at Intel and John Doerr carried it outward: separate where you're going from how you'll know you're getting there.

The objective is the destination, in language you'd actually say out loud. Three to five of them at most, or focus collapses and you're back to a to-do list with ambitions.

The key results are the evidence, and they have to be measurable. "Increase revenue" is not one. "Increase MRR from $40k to $60k" is. The test is blunt: if you can't tell whether you hit it, it isn't a key result. Attach three to five per objective.

An objective without key results is a slogan. Key results without an objective are a dashboard pointed at nothing. You need both. That's OKRs.

Score against 70 percent, not 100

The scoring convention is the part that looks wrong and isn't.

Set targets ambitious enough that landing around 70 percent means the plan was honest and the execution was real. Hit 100 percent every quarter and you're not succeeding, you're sandbagging. Drop below 30 and something structural is broken, which is also worth knowing.

That band changes what the number is for. A score is not a grade on you. It's a reading on whether the plan was calibrated, and you only get that reading if the target was set somewhere you might miss.

What you have in December

Run four complete cycles, each one launched deliberately, executed, and closed, and each close seeds the next launch. The question "what did you build this year?" gets answered with four documents instead of a feeling.

That's the real difference. Not that you got more done, though you probably did. It's that you know what happened, and you can say why.

If the current quarter is already underway, don't restart it. Close it properly at the end, and put an hour on the calendar the week before the next one starts. That hour is the whole system.