The financial year exists for reporting. It is a good convention for comparing periods and a poor one for planning human effort, and most people never separate the two.
So targets get divided by four, the big push lands in whichever quarter the board expects it, and if it goes badly the conclusion is that you did not execute well enough.
An annual plan that accounts for your own variation is not softer. It is more accurate, and accuracy is what makes plans hold.
Start with the honest audit
Before you plan next year, look at the last two.
Mark, month by month: when did you start things that worked? When did things fall over? When were you ill, and when did you take a decision you later regretted?
You are looking for repetition, not a single bad month. If two consecutive Novembers were the point where everything got difficult, that is worth building around. If one November was bad because of a specific event, it is not a pattern.
Be sceptical with yourself here. Two years is a small sample and it is easy to see a shape that is not there. Where the data is thin, hold it loosely.
Assign work to conditions, not months to targets
Once you have a rough map, the planning move is not to work less in the harder periods. It is to put a different kind of work there.
Broadly, work sorts into three kinds:
Outward work — launches, pitching, hiring, conferences, anything requiring you to be visible and persuasive. Expensive if the conditions are wrong.
Building work — systems, product, documentation, process, the things that make next year cheaper. Largely condition-independent, which makes it the natural default for lower periods.
Deciding work — strategy, restructures, ending things. Best placed where you have clarity rather than momentum, which is not always the same period as your high-energy months.
Most bad years are the result of putting outward work in a month that could not carry it, and then reading the poor result as evidence about the plan or about yourself.
Protect the peaks
The more common error is not overworking the low periods. It is wasting the high ones.
A period when things move easily is a genuinely scarce asset. Filling it with admin, or with a delayed project that could have run at any time, is expensive in a way that never shows up in any report.
When you identify a strong period, decide what it is for before it arrives, and defend it. That is the single highest-return move in this whole exercise.
Tell someone
An energy-aware plan that lives only in your head will not survive the first pressure from outside.
You do not have to explain the reasoning. "I want the launch in September rather than June, and I want Q1 for the platform rebuild" is a complete sentence for a board. You are not asking permission to be tired. You are proposing a sequence, and a sequence with a rationale beats one that came from dividing by four.
The limits, honestly
This will not make a bad quarter good. It will not tell you whether a decision is right. It does not override the market, the runway or the customer.
What it does is stop you spending your best months on maintenance and your hardest months on things that needed you at full strength. That is a smaller claim than most planning advice makes, and it is one I can actually stand behind.