90-day plans that survive the quarter

What is a 90-day plan?

A 90-day plan is a one-page list of what someone commits to deliver this quarter, written so that anyone can check progress against it. A year is too long to hold people to, and a week is too short to change anything meaningful. Ninety days is long enough to finish real work and short enough that nobody can put it off until later. The glossary entry gives the one-line definition.

Each line in a good plan has an outcome, a way of telling whether it happened, a date and a single owner. That is most of the discipline. The format matters far less than whether the plan is looked at again after the first week.

How is a 90-day plan different from OKRs?

A 90-day plan is a simpler cousin of OKRs. OKRs, short for objectives and key results, came out of Intel and were popularised by Google. They pair an ambitious objective with a few measurable key results, and are often set at company, team and individual level so the layers line up.

For most small service firms, the 90-day plan is the better starting point. OKRs work well when you have several layers of management to align, and they add overhead when you do not. You can move to OKRs later without starting again, because each plan line already has an outcome and a measure.

Why do most quarterly plans fail by week six?

Most quarterly plans fail quietly, not dramatically. They are written with energy at the start of the quarter, filed, and found again in week twelve. The usual causes are:

• No review date. Nobody looks at the plan until it is too late to recover.
• Shared ownership. A line owned by “sales and delivery” is owned by nobody.
• Too many lines. Twelve priorities means none of them is a priority.
• Vague outcomes. “Improve client communication” cannot be checked, so it cannot fail, so nobody works on it.
• The plan lives somewhere nobody visits. A document in a shared drive competes with a full inbox and loses.

Each of these has a simple fix, and most of the fixes are about rhythm and ownership rather than better writing.

What goes in a 90-day plan?

A 90-day plan needs five columns and no more than five rows. Use this template as a starting point:

Write outcomes as things that will be true, not activities. “Run three workshops” is an activity. “Three clients have signed off the new onboarding” is an outcome. Add a line at the bottom for what you are deliberately not doing this quarter. It stops the plan from being quietly added to.

How often should you review a 90-day plan?

Review a 90-day plan weekly for status, monthly for direction and at the end of the quarter for lessons. Each review has a different job.

• Weekly check-in. The owner updates the status of each line and names anything blocking it. Keep it short and stick to changes since last week.
• Monthly review. With a manager, look at the lines marked at risk or off track. Decide whether to add help, change the approach, or drop the line and say so.
• Quarter-end review. Mark each line as done, partly done or missed. Write one sentence on why for anything missed, then draft next quarter’s plan.

The weekly check-in is what keeps the plan alive. Without it, the monthly review becomes a surprise and the quarter-end review becomes a post-mortem.

Who should own each line?

Every line should have one named owner, who is accountable for the outcome even if other people do the work. Two names on a line invites each to assume the other has it. If a line genuinely needs two teams, split it into two lines with one owner each, or name one owner and list the others as contributors.

The owner is not always the most senior person. It should be whoever is closest to the work and able to say, each week, whether it is on track. A manager’s job is to review the plan and remove blockers, not to own every line on it. The same principle applies to customer relationships, where an account owner answers for one client.

A worked example: an operations lead’s quarter

This example is illustrative, with invented figures. Take a 30-person agency whose operations lead writes a 90-day plan in early October.

Her first draft has nine lines. At the first monthly review, the managing director asks which three would matter most if nothing else got done. She keeps four, including “every won deal has a billing plan within five working days”, and moves the rest to a “not this quarter” list.

By week four, the billing line is marked at risk: two deals worth £38,000 between them have no billing plan, because the handover form is optional. She makes it mandatory in week five. By week eight, the weekly check shows no exceptions. At quarter end, three lines are done and one is partly done, with one sentence explaining why. Her next plan starts from that sentence.

The plan did not succeed because it was well written. It succeeded because a problem found in week four could still be fixed in week five.

Where OpsUPLOOP fits, and where it doesn’t

OpsUPLOOP keeps objectives and 90-day plans alongside the work they are about. Each line has a named owner and a status, check-ins are dated so you can see a trend, and plans keep their versions. A plan is visible to the person it is for, its author and the managers above them, rather than to the whole firm. The OpsUPLOOP Delivery page shows how ownership works across sales, customers and billing.

OpsUPLOOP is not an HR system. It does not handle appraisals, pay, holidays or contracts, and it will not write a good plan for you. If you need full OKR software with company-wide cascading and scoring, a dedicated OKR tool will suit you better.