I Published Two Articles One Week and Sixty Three the Next. That Is Not a System.

I pulled my own numbers this morning.

I did not like them.

Here is exactly what my archive did over the last eight weeks. Not an estimate. A straight count out of the database that runs this site.

Two in one week.

Sixty three two weeks later.

Then fourteen. Then twenty three.

Read that again.

That is not a publishing system. That is a mood with a database attached.

Everybody has a version of this chart

You may not run a website. You still have this chart.

The week you called eleven leads and the three weeks you called nobody. The month you posted every day and the month you went dark. The quarter you invoiced on time and the quarter you did not send a single one until you needed the money.

Most people never look at it. They just remember the good week and tell themselves that is the pace.

It is not the pace. The average is the pace. And the average includes the week you did two.

Why the spikes are a warning, not a win

I know exactly what caused my July spike. I got the automation working. Once it worked, I ran it hard, because I could.

And then real life showed up, which it always does, and the number fell off a cliff.

Here is the part that took me a long time to accept.

A spike is not proof the system works. A spike is proof the operator was available.

The only thing a spike proves is that on that particular week nothing broke, nobody got sick, no filing came due, and I had the hours. Take any one of those away and you get the week where the number is two.

If your output collapses the moment your week gets hard, you did not build a system. You built a habit that depends on your calendar staying clean. Your calendar is never going to stay clean.

I have written about this from the other direction, about how anything that only runs when you personally run it is a job you gave yourself. This chart is what that looks like in numbers.

The fix is smaller than you want it to be

Everybody wants the fix to be a tool.

The fix is a floor.

Pick the number you can hit on your worst week of the year. Not your best. Not your average. Your worst. The week the truck breaks down and somebody is in the hospital and you did not sleep.

Whatever you can still do that week, that is your real number.

Mine is three a day, automated, publishing whether I am at a keyboard or in a delivery room. That number is not impressive. It does not need to be impressive. It needs to be true on the worst Tuesday of the year.

Then you build everything on top of that floor. Extra capacity goes into the good weeks as a bonus, not as the plan.

Three things to check this week

One. Count your actual output for the last eight weeks. Not how it felt. Count it.

Two. Find your worst week and circle it. That is your real capacity, not the good one.

Three. Ask what would have to be automated, delegated, or scheduled in advance for the worst week to still hit the floor.

That third question is the whole job. Everything else is decoration.

I stopped trying to have more good weeks. I started trying to make the bad weeks boring.

If you want this built for you

This is the work I do. I take a business that runs on somebody remembering to do it and turn it into something that runs whether they remember or not.