The 90-day plan an owner-operator will actually follow

Most small business plans are written once, in January or in a quiet week, and never opened again. That isn't a discipline failure. It's a design failure: the document was built to be comprehensive rather than usable, and a comprehensive document has no obvious next action in it on a Tuesday morning.

A 90-day plan is a different object. It's short, it names 3 things, it has a date against each of them, and it gets looked at every week. It's the practical end of working on the business instead of in it, and it's the mechanism that stops the good intentions from a planning session evaporating by the third week of the quarter.

Why the 12-month plan doesn't survive contact

3 things kill an annual plan.

The horizon is too long to feel real. Nothing on a 12-month plan is urgent in March, so nothing on it happens in March. By the time it becomes urgent, the situation has changed and the plan is out of date rather than behind.

It has too much on it. An annual plan typically carries 8 to 15 initiatives, because writing a plan feels productive and adding an item feels free. An owner-operator with 4 hours a week of genuine planning capacity cannot run 12 initiatives. They can run 2, and possibly 3.

Nothing checks it. The plan lives in a document and the week lives in a job board and an inbox. Without a fixed review, the plan is competing for attention against work that shouts, and work that shouts always wins.

90 days fixes the first problem, a hard limit of 3 fixes the second, and a weekly review fixes the third. All 3 are needed. A 90-day plan with 11 items on it fails exactly the way the annual one did.

What actually goes on it

3 objectives. Not 5, and not "3 plus a few small ones".

Choose them by asking what would still be true at the end of the quarter that isn't true now. Then apply a filter: pick the objective that removes a constraint, not the one that's easiest to describe. A quarter spent tidying the website while the constraint is the owner's own capacity produces a nicer website and the same business.

Each objective needs 4 lines and nothing more:

1. The objective. In plain words, in 1 sentence.
2. How you'll know it's done. A test you could apply on the last day of the quarter and get a clear yes or no.
3. The first 3 actions. Small enough to start this week, each with a person and a date.
4. What it will cost. Hours, money or both. An objective with no cost written against it is a wish.

If you can't name the test in line 2, you haven't got an objective yet, you've got a topic. "Improve the quoting" is a topic. "Every quote goes out within 24 hours of the site visit, and I can show that from the job log" is an objective.

Writing an objective you can actually check

The difference between a plan that runs and a plan that stalls usually comes down to whether the objective is checkable.

A checkable objective names a state, not an activity. "Do more marketing" is an activity and it's never finished. "The 3 processes on the list are written, and somebody other than me has run each of them once" is a state, and on 30 June it's either true or it isn't.

Where you can, attach a number you already collect. A plan that requires a new measurement system to be built before it can be tracked will stall on the measurement system. If you're not sure which figures those are, the numbers worth knowing off the top of your head is a reasonable starting list, and most owners already have 3 or 4 of them without realising.

A 90-day plan will often carry an objective with a dollar figure or a staffing decision inside it. Coaching is a good place to think through the operational side of that. The parts that need an accountant or a lawyer belong with them, and a plan is a good way to work out which parts those are before you're standing in front of a deadline.

The weekly review is the plan

The document is not the plan. The 20 minutes a week you spend on it is the plan, and if that appointment doesn't exist, nothing else here matters.

Put it in the calendar as a recurring block: same day, same time, ideally at the start of the week rather than the end of it. Then run it the same way every time.

• Read the 3 objectives out loud. It takes 30 seconds and it's the only thing keeping them present.
• Go through last week's actions. Done, not done, or moved. Say which, without explaining.
• Name why anything slipped. In 1 sentence. Not to punish it, but because the reason is the actual information: no time, blocked by someone else, or you didn't want to.
• Set 3 actions for the coming week. Each with a date.

The awkward part is the second step, and it's the part doing the work. Reading back a commitment you didn't keep, out loud, is uncomfortable in a way that reading a plan silently never is. Owners who run this with somebody else, whether that's a business partner, a peer or a coach, generally find it survives longer than doing it alone.

An illustration, with round numbers

Here's a plan for a made-up Adelaide services business, purely as an illustration. It isn't a real business, the numbers are round, and it isn't a projection of what any plan produces.

Objective 1: quoting stops being a night-time job. Done when every quote in the log went out within 24 hours of the site visit for 4 consecutive weeks. First actions: build the standard quote template by Friday, list the 6 most common jobs with prices, move the site visit slot to mornings. Cost: about 6 hours in week 1, then less.

Objective 2: 3 processes written and handed over. Done when the scheduling, ordering and invoice preparation processes are written and each has been run once by someone else without a question coming back. First actions: record yourself doing the scheduling run, write it up, hand it to the office admin on the 15th. Cost: roughly 2 hours a process.

Objective 3: 1 new source of work opened. Done when 3 enquiries have arrived from a route that isn't the existing referral network. First actions: list 10 businesses that serve the same customer earlier in the job, contact 5 of them, book 2 conversations. Cost: 1 hour a week.

3 objectives, 9 first actions, all of it on 1 page. The point of the illustration isn't the content. It's the shape.

What to do when you miss

You'll miss. Every quarter carries a fortnight where something breaks and the plan gets nothing.

The recoverable version is to name it in the weekly review, move the date once, and carry on. The unrecoverable version is to skip the review because there's nothing good to report, which is how quarters get quietly abandoned in week 5.

If an objective has moved 3 weeks running, it isn't behind. It's not being done, and the honest move is to take it off the plan or halve it. A plan carrying an item nobody intends to start teaches you to ignore the whole document.

Where every quarter stalls in the same place, the plan probably isn't the problem. Persistent stalling usually points at capacity, and there are only so many ways an audit of your own week can tell you the same thing.

Where the quarter's 3 objectives come from

The most useful source is a diagnosis rather than a wish list. Working out what usually causes a revenue plateau in a business like yours tends to produce a shorter and more useful list of candidate objectives than a blank page does, because it points at the constraint instead of at the symptom.

Beyond that, the tools on this site cover the ground a first plan usually needs: what an owner hour is worth, what coaching costs before you go looking, and whether a coach is the right kind of help at all. None of them writes the plan. They just narrow what belongs on it.

Be clear-eyed about the limits, though. A 90-day plan is a scheduling device. It doesn't make a decision better, it doesn't create hours you don't have, and it can't tell you whether the 3 things you picked were the right 3.

What it does is make the postponement visible. Most owners already know what needs doing. The plan's only real job is to stop the quarter passing without any of it happening, and that's a modest claim which happens to be true.