The month nobody plans for

Somebody stops working on a plan they still believe in, and files it under willpower.

It is almost never willpower.

What a plan is actually made of

Think about what a plan hands you. Not just the order to work in. Every item on it ends, and an ending is a small receipt that the effort went somewhere. You close it, and you have something to hold up.

Those receipts are not spread evenly, and that is the whole story.

Early on they arrive constantly, because anything genuinely new can be finished. Install the thing. Build the small version. Read the chapter. Each one is a separate event with an edge you can feel.

Further in, the work stops being made of things that finish. It becomes a small set of skills quietly sharpening, and sharpening issues no receipt at all. You are not learning a new thing you could name; you are becoming less bad at something you already do, in a way that is invisible to you while it happens.

So the plan goes quiet. Nothing was wrong with how it was written. It has simply used up the one material it is built out of.

Why "try harder" lands on the wrong target

Here is the part that gets misdiagnosed, and the misdiagnosis is what costs people the thing they were building.

By that point you are still improving, visibly, to anybody watching. What you have lost is any way of telling. You cannot audit yourself while you are the one doing the work, and nobody can, at any level. That is a position, not a character flaw.

Which means what ran out is not commitment. It is evidence. And effort does not manufacture evidence, so working harder produces more of what you already had and none of what you are missing.

If the last few months have felt like slowly running out of reasons to believe it is going anywhere, that is the mechanism. It is not a verdict on you.

What to do about it, and when

Write yourself the receipt in advance, while writing it is still easy.

That is three lines, and it takes about twenty minutes:

One capability. Name something you will be able to do by a month you choose, that would beat you today. An action, not an understanding. "Read a stack trace and say where to start looking" is checkable. "Understand debugging" is not, and an uncheckable line is worse than a blank one, because it feels like an answer.

One check. Decide now how you will find out: one evening, no cost, and a yes or no at the end. The easiest check is almost always to try again the exact thing that beat you recently.

One date. Put it in the calendar. Not a reminder to study, a reminder to check. That date is the event the middle refuses to supply, and manufacturing it honestly is the entire trick.

A fourth line is worth writing, and it is the one people skip: what you will do if the answer is no. Decide that now, calmly, while nothing is at stake. On the day you will be tired, and a tired person reads a no as a verdict.

The page for writing those lines down, including the worked example and the room for the fourth one, is here.

Do it tonight, while it still feels unnecessary. That is not me hurrying you. The month that needs this is the month that cannot design its way out.