The quarter stays. The waiting goes.
A goal should take as long as the outcome takes. Almost nobody runs it that way.
Here is a question I have started asking leadership teams, and the pause afterwards is usually the interesting part.
Why is that goal three months long?
Not “why that goal”. Why three months. And the honest answer, once we get past the first one, is almost always the same: because that is how long a quarter is.
The bit nobody argues with
Nobody would design it this way on purpose.
If you sat down to size a piece of work, you would look at the outcome you wanted, form a view about what it would take, and size it accordingly. Some things would be five weeks. Some would be five months. You would not reach for the finance calendar.
And yet the finance calendar is what most companies use, for the most important work they do.
Not because anyone decided it was right. Because the quarter was already there, doing a useful job for reporting, and it quietly became the container for everything else too.
What it costs, in four ways you will recognise
Goals get padded. Ninety days available, ninety days used. Not deliberately, just naturally.
Dead goals get dragged. Everyone in the room knows by week six. The goal stays open until week thirteen, because that is when goals close here.
Teams rest when they finish early. A goal lands in week eight and the next one starts after planning. Nobody would ever choose to leave good people pointed at nothing for a month. Waiting for the calendar does it anyway, and it does it quietly.
And goals get killed by the date rather than the evidence. This is the one people forget, and it is the most expensive. The work was going fine. It needed five months. It got three, so it failed, and everyone drew the wrong conclusion about the idea.
The part I want to be careful about
The obvious move here would be to attack the quarter, and it would be wrong.
The quarterly rhythm earns its place. A shared clock means everyone reviews at the same time, which is the only moment when trades are cheap and a genuine swap of resource between teams is possible. It means reporting lands together. It means the company can see itself.
Take that away and you do not get speed, you get a company where nobody knows what anyone else is doing.
And there is a real reason people reach for a quarter, or a trimester, or something longer still. It is long enough to attempt something meaningful, and meaningful is the point. I am not arguing against that. Value Sequencing exists precisely so meaningful work gets the room it needs.
The argument is about sizing. Results, evidence, the effect of a new tool, the pace at which a team actually learns: these are all hard to size in advance, and getting harder. Which means the answer is not a longer fixed period instead of a shorter one. It is planning that can flex as the evidence arrives, and right-time a goal rather than pre-commit to a length nobody could have known.
So keep it. The quarter is a good clock and a bad gate.
What changes
Two things, and they are small.
Goals end when they are done. Either the outcome was reached, or stopping was the right call and the reasons got written down. Both are proper endings. Running out of quarter is not one.
When a goal ends, the next one starts. Not after a ceremony. The team has the capacity, the next most valuable thing is waiting, so they pick it up.
That is it. The rhythm of attention stays exactly where it was. The length of the work stops being decided by a date.
The arithmetic, because it is the honest argument
I am wary of promising percentages here, so let me give you the reasoning instead and let you do your own sums.
A quarter holds a fixed pool of hours for the work that changes the company. If a team finishes in five weeks and waits three, you have paid for eight and bought five. Do that twice a year, across several teams, and the number gets uncomfortable.
There is no cleverness in this. It is just that idle capacity is invisible, so nobody adds it up.
And one thing I would rather say than not
We have not run a controlled experiment proving that this beats a well-run quarterly system. I doubt anyone has. What we have is ten years of watching the four failures above, in more than a hundred organisations, and a method designed against them.
So we publish the confidence behind it, and what would prove us wrong. If you want to see that, it is on the method page. I would rather show you our workings than sell you certainty.
The question worth sitting with
Look at your current goals. For each one, ask why it is that long.
If the answer is the outcome, good. If the answer is the calendar, you have found something.
Goals at the speed of the work, not the calendar.
This is part of how we work. The method page carries the canonical definition, the two good endings, and the confidence behind it.
Read the method →
A UK-based strategy and OKR consultant and two-time SaaS founder with a venture-backed exit, Matt turns strategy into execution for teams scaling from tens to thousands. He co-founded ZOKRI in 2018, having previously co-founded Linkdex, a venture-backed enterprise SaaS platform he led to a trade sale. He writes the methodology behind these notes.