Four Months Left

Tomorrow is September first. You have four months left in the year, and about seventeen usable weeks once you take out the holidays and the fortnight in December when nobody answers email.

Seventeen weeks. That's the whole runway.

I bring this up every year around now and it lands differently than it does in January, because in January the year is theoretical and by September it's evidence. You know what your capacity actually is. You've watched yourself fail to do things for eight months. That's not a criticism, that's data, and it's better data than any planning session produces.

So let's use it rather than doing the thing everyone does in September, which is to write a fresh list of ambitious things and feel briefly excellent about it.

Get your January list. Whatever form it took, a doc, a whiteboard photo, a note in your phone. If you never wrote one down, use the version in your head, it's close enough.

Now sort it into three piles, and be brutal, because the whole exercise fails if you're generous with yourself.

Done. Things that shipped. Usually shorter than expected and usually includes two things you'd forgotten you did, which is worth noticing.

Not started. Not "in progress." Not "partially scoped." Nothing has happened. This pile is almost always the biggest and it's the one people lie to themselves about hardest, because "I've been thinking about it" feels like progress and isn't.

Genuinely in motion. Real work has happened in the last thirty days. Thirty days, not "recently."

Now the number that matters. Count the not started pile. Look at how long it's been sitting there. Eight months.

Here's the thing that should reframe your September: something that has survived eight months of not happening is not going to happen because you got serious in the fourth quarter. It didn't fail from lack of effort. It failed because every week for thirty five weeks, something else was more important. That's not weakness. That's a revealed preference, repeated thirty five times, and it's telling you something true.

The mistake is treating it as a discipline problem. It's an information problem, and the information is: this thing is less important to you than you claimed in January.

Before you pick anything, it helps to know why the not started pile got that big, because the same forces are about to eat your September plan if you don't name them.

Lie one: "this will take a week." Almost nothing takes a week. The building takes a week. The deciding takes three, and the deciding is invisible in the estimate because it doesn't feel like work. It feels like procrastination, which is why people don't budget for it and then feel bad when it happens.

Fix: whatever your estimate is, ask what has to be decided before the work can start, and who has to agree. Add that time explicitly. The estimate gets uglier and considerably more accurate.

Lie two: "I'll do it when things calm down." Things do not calm down. There has never been a quarter in the history of small business where things calmed down. This phrase is how a task gets deferred indefinitely while feeling like it's been scheduled.

Fix: if something only happens in a calm week, it doesn't happen. Either it goes in the plan with time protected for it, or it comes off the list. No third option.

Lie three: "it's basically done." The last twenty percent is half the work, and it's the half made entirely of unglamorous tasks: the settings page, the error message, the email nobody wants to write, the conversation with the one client who'll be annoyed. That's why things sit at ninety percent for months.

Fix: for anything currently "nearly finished," write out the remaining tasks in full. The list is always longer than the feeling. Then either finish it in September or kill it, because a thing sitting at ninety percent is costing you attention every week and returning nothing.

Run your list through those three and it usually shortens itself before you've made a single hard decision.

Seventeen weeks sounds like a lot until you price things honestly.

A genuinely new offer, from conception to first sale, is eight to twelve weeks for most small businesses. Not the building. The building is two weeks. It's the deciding, the positioning, the pricing wobble, the rewrite, and the six weeks of nobody buying it while you work out the message.

A meaningful system rebuild, the kind where a workflow actually changes and stays changed, is four to six weeks including the fortnight where everyone quietly does it the old way anyway.

A hire, from writing the description to the person being useful, is ten to sixteen weeks.

A content or audience push takes a full quarter to show anything, and if you start in October you're reading the results in January.

Which means, realistically, you have room for one large thing and two small ones. That's it. That's the whole budget.

Most people go into September with six. Then they do four of them badly, finish none, and arrive at January having converted seventeen weeks into a feeling of being busy.

One large. Two small. Write those three down and cross out everything else, and I mean actually cross it out rather than moving it to a someday list where it goes to feel guilty.

Here's the one I use, and it's the only planning question I've found that reliably produces a different answer than the obvious one.

Which of these, if it were finished, would make the others easier or unnecessary?

Not which is most valuable. Not which is most urgent. Which one changes the shape of the rest.

Most lists have one item like this and it's almost never the one at the top. The top item is usually the loudest problem, and loud problems are usually symptoms.

An example from my own list this year. I had "fix the onboarding sequence," "write better case studies," and "raise prices" all sitting there. The obvious pick was pricing, because it's the fastest revenue and everyone tells you to raise prices.

But the case studies were the one that changed the shape. With three real ones, the pricing conversation stops being a negotiation and becomes a comparison. The onboarding sequence writes itself out of the same material. Pricing first would have been a fight I'd have half won. Case studies first made the fight unnecessary.

That's the pattern. Look for the item that's load bearing for the others, and accept that it's usually less exciting and takes longer to pay off.

Second question, and this one's for the small things: what would you be embarrassed to still be doing manually in January?

Not the biggest time sink. The one that's embarrassing. That word does something useful, because embarrassment is a decent proxy for tasks that are both obviously automatable and quietly expensive, and you've been carrying it around because it never got loud enough to fix.

Everybody's got two. Mine last year was manually copying invoice numbers between two systems, a thing Make solved in an afternoon, forty minutes a week, for eleven months, because it never crossed the threshold of annoying enough. Twenty six hours to save a two hour build.

Once you've got your one large and two small, the sequencing matters more than the planning did.

September is for the large thing, alone. Not alongside. Alone. The first four weeks of anything substantial are where it either gets traction or quietly becomes the thing that's on next year's list. Protect them. If you can only defend one month of focus this year, make it this one.

October is for the two small things, which should be automation or process work you can finish rather than start. Finishing matters here for reasons that aren't about the tasks. You need at least one thing this quarter that visibly ends, or the whole four months feels like wading.

November is for whatever the large thing turned out to actually need, because it will not be what you thought in September. Leave the month genuinely open. This is the discipline most plans lack and the reason most plans fail: no slack, so the first surprise eats the rest of the quarter.

December is for closing and deciding. Not new work. Close what's open, write down what happened, and do the honest version of this exercise for next year while the evidence is fresh rather than in January when the memory has softened into a story.

A four month plan needs one mechanism or it becomes a document. Just one, and it takes about ten minutes a week.

Every Friday, three questions on the same page.

Did the large thing move this week? Yes or no. Not "sort of." If the answer is no three weeks running, the plan is fiction and you need to either protect the time properly or admit the thing isn't the priority you said it was. Both are fine. Pretending is not.

What tried to get added to the list? Something always does. Write it down and put it on the January list rather than this one. The purpose isn't to reject good ideas, it's to make the addition visible, because the way four month plans actually die is by accretion. Nobody decides to abandon them. Six small urgent things just quietly take the space.

What can come off? Ask it every week even when the answer is nothing. Once a month or so the answer isn't nothing, and catching that early is worth more than the other two questions combined.

Ten minutes, Friday afternoon, same page every week so you can see the pattern across months. That's the entire management overhead. Anything more elaborate becomes a thing you maintain instead of a thing that helps.

The businesses I watch land the fourth quarter well almost all have some version of this. Not a system, a habit. The plan is the easy part and everybody makes one. The weekly ten minutes is what separates the plan from the paperwork.

The temptation right now, with four months on the clock, is to go faster. Longer days, more parallel work, catch up on the year.

That's how the fourth quarter goes wrong. Not from doing too little. From doing six things at forty percent and shipping none of them, then carrying all six into January where they become next year's not started pile, and the cycle runs again with new dates on it.

The businesses I watch finish the year well don't do more in the fourth quarter. They do less, on purpose, and the less is chosen deliberately rather than by whatever was loudest in the second week of September.

So the actual assignment for this morning is subtraction. Take the January list. Kill everything that has survived eight months of not happening, and be honest that killing it is just formalising a decision you already made every week since February. Pick the one thing that makes the others easier. Pick two things you'd be embarrassed to still be doing by hand.

That's the whole plan. It fits on an index card. Seventeen weeks is enough for it and not enough for anything more.

Then go do something on a Sunday that isn't this. The plan will still be there tomorrow, and September's a better month for it than August anyway.

Jordan

The AI Newsroom is written by Jordan Hale. This issue contains affiliate links to tools I actually use. If you sign up through them I may earn a commission at no extra cost to you.