Build the Skip Into It

Most automated systems have one thing they are physically incapable of doing.

Producing nothing.

You build a thing to make a report every morning, and it makes a report every morning. Even on the morning there is nothing to report. It will not sit the day out. It has no way to. So it does the only thing a system with a quota and no exit can do.

It pads.

What padding looks like

You have seen it. You probably never named it.

The weekly update where three of the five bullets are last week restated. The dashboard carrying a chart nobody has ever acted on. The status email that has said on track for four months running. The newsletter that goes out Tuesday because it goes out Tuesday, carrying four hundred words nobody needed.

None of that is laziness. It is usually the opposite. Somebody built a system, gave it a cadence, and never gave it permission to come back empty. So it fills the space, because filling the space is the only move available to it.

The cost is not the wasted words.

The cost is that once your system pads, nobody can tell the difference between a real signal and filler. A report that always says something ends up saying nothing.

The rule

Every recurring process I build gets three things written down before it runs a single time.

One. What counts as a real result.

Two. What it does when there is no real result.

Three. What it says when it takes option two.

That third one is the part everybody leaves out, and it is the part that makes the whole thing work.

A skip that happens silently is indistinguishable from a system that broke. You open your inbox, there is nothing there, and you have no idea whether that means all quiet or the job died at 3 a.m. three weeks ago.

A skip that says why is a status report.

There is an enormous difference between an empty inbox and an inbox that says checked every source, nothing new since Tuesday. Same zero. Completely different information.

I did not put that rule in because I am principled about it.

I put it in because those articles go out under my name without me reading every one first, and a system that pads is a system that will eventually publish something I have to walk back. The skip is the cheapest insurance I have ever bought.

Same rule, different room

This is not just a software problem. It shows up everywhere you have made an honest answer impossible.

Say your CRM has a required field for lead source. Salesperson picks up the phone, has a good call, goes to save the record, and does not actually know where the lead came from. The field will not let them save without one. So they pick whatever is at the top of the dropdown.

Six months later you have a pile of data telling you most of your business comes from the first item on an alphabetical list, and somebody is about to move a marketing budget based on it.

You did not get bad data because your people are careless.

You got bad data because you removed the honest answer from the form.

Add unknown to the dropdown. Add no update this week to the status template. Add nothing to report to the standup. Make the empty answer a legal answer and watch how fast everything else your people tell you gets more trustworthy.

How to add it to something you already run

Pick one recurring thing you produce. The weekly report is usually the best candidate because it is the one people have quietly stopped reading.

Write down what would make this week's edition worth sending. Be specific about it. New numbers. A decision. A change in direction. Something that needs a response from somebody.

Now write down what you send when none of that is true. One line is enough. Nothing moved this week, here is the one thing I am watching.

Send that line the next time it is true.

Nobody is going to be annoyed. Half of them will be relieved. And the next time you send a full one, they will actually read it, because they will know you only send it when there is something in it.

The bottom line

Cadence is not the product. The signal is the product.

If your system cannot skip, it is not reporting to you. It is performing for you.

Build the skip in. Make it say why. Everything else your system tells you gets more believable overnight.