Forty-One Messages Nobody Read

For a little over a month, something I built sent me a short update every morning at a quarter to seven. What got done overnight, what was coming up, what needed a decision.

Forty-one of them in a row. I answered zero.

Not because they were bad. Most of them were fine. Some of them were genuinely useful. I just never read them, and when I finally went back and looked at why, the answer was embarrassing in how simple it was. Nobody had ever asked when I actually read anything.

I am not a morning reader

Once I bothered to look, the pattern was obvious. Half of everything I reply to lands between five in the evening and one in the morning. Between six and ten in the morning I barely touch my phone for anything that is not urgent. A message that arrives at 6:47 does not get read at 6:47. It gets buried under everything that comes in after it, and by the time I am actually sitting down to work, it is ten screens up and already stale.

So the update was doing its job perfectly. It was written well, it was on time, it was accurate. It was just showing up to an empty room.

Moving it was the whole fix

I did not rewrite it. I did not add a summary on top of it or a second reminder later in the day. I moved it to seven in the evening, cut it down to one short message, and stopped sending it at all on days when nothing happened.

That is the entire change. Same information, different hour, fewer words.

It sounds too small to matter. It is the opposite. The best update in the world is worth nothing if it arrives while the person is asleep, driving, or in the middle of something else. And a mediocre update that arrives the moment someone is ready to think about it gets read every time.

Volume was hiding the problem

The easy reaction to being ignored is to send more. Add a follow-up. Mark it important. Send a second version at noon in case the first one got missed.

I have done that, and it makes things worse. Every extra message teaches the reader that your messages are skippable, because most of them are. I wrote about a version of this in what I learned running four bots and zero employees: the few things that matter get lost in the steady drip of things that do not. More volume does not fix timing. It just makes the miss louder.

One message, at the right time, with something real in it. That beats five messages at the wrong time every single time.

This is not really about bots

I learned it from my own automation, but it applies to almost anything you send another person. The weekly update to a client. The report to a partner. The text to a friend asking for a favor.

Most of us decide when to send based on when we finished writing. That is our schedule, not theirs. The better question is when the other person is actually going to sit with it. Some people clear their inbox at six in the morning with coffee. Some people do it at eleven at night after the kids are down. If you do not know which one you are dealing with, you can usually find out by looking at when they reply to you.

It is the same idea as the Saturday morning test, turned around. That one is about noticing when you actually want to do the work. This one is about noticing when the people you work with actually want to hear about it.

What I check now

Before I set anything up to send on a schedule, I ask three plain questions.

When does this person actually read things? Not when they are awake. When they read.

Would they miss it if it did not come? If the honest answer is no on most days, it should only send on the days it has something to say.

Can I say it in the length of a text message? If not, the message is the headline and everything else lives somewhere they can open when they want it.

Forty-one messages taught me that. The forty-second one went out at seven at night, when I was actually there to read it.