The 90-day plan: a quarterly planning framework for growing businesses

A 90-day plan is a quarterly planning framework that turns the annual strategy into three to five priorities, each with one owner, a measurable definition of done and a weekly check-in. Ninety days is long enough to deliver something that changes the company and short enough that the plan is still true at the end of it. The method has five parts: a planning meeting, a short list of priorities, workstreams with owners, a weekly rhythm, and a review that feeds the next quarter.

Why plan in quarters

A year is too long to manage against. By month four the assumptions behind an annual plan have shifted, and the plan quietly stops being consulted. A month is too short to deliver anything that changes the business. Ninety days sits between the two: long enough for a real project to land, short enough that people still remember what they committed to. It also gives four natural moments a year to stop, look at what changed and reset.

This is not a niche idea. Google's re:Work guide to OKRs describes Google setting annual and quarterly OKRs and holding company-wide meetings every quarter to share and grade them. EOS, a framework widely used by founder-led companies, builds its execution around 90-day priorities. The quarter is simply the shortest period in which strategy and execution fit in the same conversation.

The quarterly planning meeting

The plan is made in one session with the full leadership team, away from the daily flow. One full day or two half days is enough. Longer sessions tend to produce longer lists, not better ones.

Inputs

• The annual priorities and the one-page strategy, so the quarter connects to something bigger.
• The scorecard: current KPIs and how they moved over the last quarter.
• Last quarter's review: what was delivered, what slipped and why.
• The issues list: problems raised during the quarter and parked for planning.
• Capacity: known constraints such as hiring, holidays, launches or large client deliveries.

Agenda

Outputs

• Three to five company priorities, each with one owner and a measurable definition of done.
• A first draft of workstreams and milestones, finalised by the owners in week one.
• The KPIs to watch closely this quarter.
• A short list of what was explicitly not chosen, so it stops being reopened.
• A one-page note to the whole company explaining the priorities and why.

Choosing three to five priorities

This is where most quarterly plans fail. The candidate list is usually fifteen items long and every item has a sponsor in the room. Google's re:Work guide recommends three to five objectives, warning that more can over-extend teams and diffuse effort. In a growing company the warning applies even more, because the same few people own most of the work.

1. It moves an annual priority. If it does not connect to the year, it needs an exceptional reason.
2. It needs cross-team effort or leadership attention. Work a single team can deliver in its normal flow does not belong on the company plan.
3. Done fits in one sentence a stranger would understand. “Improve onboarding” fails. “Every new client live within ten working days” passes.
4. Someone in the room will own it. Not sponsor it. Own it.

Workstreams and owners

Each priority breaks into two to four workstreams. Each workstream has one owner, a definition of done and milestones at roughly weeks four, eight and twelve. The priority owner coordinates the workstreams and answers for the outcome; workstream owners answer for their part.

One name per line. A priority owned by two people is owned by nobody, and a workstream owned by a team gets done by whoever has spare time, which in a growing company is nobody. If roles are unclear, settle them before the quarter starts with an accountability and ownership matrix.

The weekly check-in

The plan lives or dies in the weekly leadership meeting. Each priority owner gives a one-line status: on track or off track. On-track items get no discussion. Off-track items go to the issues list and are either solved in the same meeting or given an owner and a date.

• Keep it to fifteen minutes inside the weekly leadership meeting.
• Status is binary. “Mostly on track” is off track.
• Report milestones, not activity: what was finished, not what was worked on.
• The owner reports, even when the news is bad. Especially then.

Andy Grove argued in High Output Management that a manager's output is the output of the organisation they lead and of the ones they influence. The weekly check-in is where that becomes practical: fifteen minutes in which the leadership team can see the whole plan and unblock it.

Mid-quarter correction

Around week six, take forty-five minutes to look at the plan as a whole. Each priority has three possible outcomes: keep it, reshape it or drop it. Dropping a priority because the situation changed is a decision, not a failure, as long as it is made openly and the freed capacity goes somewhere deliberate. What must not happen is the silent drop, where a priority stops being mentioned and is rediscovered at the end of the quarter.

The end-of-quarter review

The review closes one quarter and opens the next. Score each priority quickly and honestly. Many teams use done, partly done or not done. Teams using OKRs often grade on a scale from 0.0 to 1.0, and Google's guide places the sweet spot for ambitious OKRs at around 0.6 to 0.7, a reminder that a stretch goal fully achieved was probably not much of a stretch.

Then ask one question of every miss: was the priority wrong, or was the execution wrong? The answers are the first input to the next planning session. Our quarterly business review guide covers the full format.

A worked example: Marés Altas

Marés Altas is a fictional company, used here only to illustrate the method. It has 60 people and distributes fresh fish and seafood to restaurants across northern Portugal. Its annual priorities are to open a second region, protect margin and stop relying on the founder for every large account. The leadership team arrives at planning with eleven candidates and leaves with four.

At the week-six review, Galicia is off track: the warehouse partner is late. The team reshapes the priority instead of dropping it. The target moves to twelve restaurants, and the commercial director borrows one account manager from the key-account handover, which the founder agrees to slow by two accounts. The decision is written down and announced. At quarter end, three priorities are done and Galicia lands at eleven restaurants. The team scores it as partly done and carries it into the next quarter with a stated reason.

A 90-day plan template

The 90-day execution plan and the quarterly business planning template are ready to use. If you are deciding whether to write your priorities as OKRs, read OKRs vs KPIs first.

Common failure modes

• Too many priorities. Eight priorities is a to-do list. Cut to five, then ask whether four would do.
• Activities dressed as outcomes. “Run a hiring campaign” is an activity. “Three senior engineers start by week ten” is an outcome.
• No owner, or two. Shared ownership feels collaborative and behaves like abandonment.
• Planning without the scorecard. Priorities chosen without the numbers tend to address the loudest problem, not the most important one.
• No weekly rhythm. A plan reviewed only at quarter end is a wish list with a date on it.
• Silent drops. Priorities that vanish without a decision teach the team that the plan is optional.
• Business as usual on the plan. If it would have happened anyway, it does not need a priority slot.

Where to go from here

A 90-day plan is one part of a wider operating cadence. If you want to see where your current planning rhythm holds and where it breaks, an Operating Assessment is a short way to find out. When the gap is mainly in planning, our quarterly planning and OKRs work is the direct fit.