Nobody Reads It

There is a report sitting in your business right now that nobody reads.

Somebody builds it. Somebody sends it. It lands in an inbox, or a shared drive, or a channel, and then it does absolutely nothing. No decision comes out of it. No behavior changes because of it. It exists because two years ago somebody asked for it once, and asking for it once was enough to create a permanent obligation.

I want you to find that report this morning. And then I want you to find the other eleven.

Most operational waste doesn't look like waste. It looks like diligence. It looks like a team that documents things, that keeps stakeholders informed, that runs a tight ship. That's exactly why it survives. Nobody audits the stuff that makes them look responsible. You cut the obvious fat, the software you stopped using and the subscription you forgot about, and you leave the expensive stuff completely alone because the expensive stuff wears a suit.

The expensive stuff is the work product nobody consumes.

Here's the audit. It takes about ninety minutes and it will annoy you.

Open a blank document. List every recurring output your business produces. Not tasks. Outputs. Things that get made on a schedule and delivered to somebody. The weekly sales summary. The monthly client report. The project status email. The meeting notes. The dashboard somebody built in a fit of enthusiasm last spring. The onboarding packet. The internal newsletter. The compliance log. The deck that gets rebuilt every quarter with slightly different numbers.

Be greedy about it. If it happens more than twice and somebody made it on purpose, it goes on the list. Most businesses under thirty people land somewhere between eighteen and forty items. If you got fewer than fifteen you're not being honest yet, so go through your calendar and your sent folder and try again.

Now, next to each one, write the name of a specific human being who reads it. Not a department. Not "the team." Not "leadership." A person, with a first name, who you could call right now and who would be able to tell you what was in the last one.

This is where it falls apart. You'll get through maybe half the list before you start writing names you're not sure about. That uncertainty is the finding. That's the whole audit in one column.

For every item where you couldn't name a reader with confidence, do the ugly thing and check. If it's an email, pull the open rate. If it lives in a shared drive, check the view history. If it's a dashboard, most tools will tell you when it was last loaded and by whom. If it's a document, look at the version history and see whether anyone has opened it since it was created.

I've run this with a lot of operators now and the pattern holds with depressing consistency. Somewhere between a third and half of recurring outputs have no real audience. Not a small audience. No audience. The thing gets made, gets delivered, and gets ignored, week after week, by everyone including the person who originally requested it.

Understand what you're up against here, because the reason this waste survives is structural and it will fight you.

Nobody gets in trouble for producing something unnecessary. They get in trouble for stopping. The downside is asymmetric. If you keep making the useless report, the cost is a few hours a month buried in somebody's workload where nobody can see it. If you stop making it and one person notices, you had a lapse. You dropped something. So everyone keeps producing, forever, because the rational individual choice is to never stop anything.

There's also the requester problem. The person who asked for the report two years ago has completely forgotten they asked. They're not reading it. They'd be fine if it vanished. But nobody asks them, because asking feels like pushing back, and pushing back on a request from two years ago feels absurd. So the obligation just sits there, unowned, unloved, and fully funded.

And then there's the sunk cost of the build. Somebody spent three weeks setting up that dashboard. Killing it feels like admitting the three weeks were wasted. They were, but the three weeks are gone either way. The only question is whether you'd like to keep paying rent on them.

None of this is a people problem. It's a defaults problem. The default is continue. Your job this morning is to flip the default to stop, and make continuing the thing that requires a reason.

Once you've got the list and the reader column, everything sorts into four buckets. Go item by item and pick one.

Kill it. No reader, no decision, no downstream dependency. Stop producing it. Don't announce it with a memo, don't schedule a transition. Just stop, and put a note in your calendar for thirty days out. If nobody has asked in thirty days, it's dead and you were right. If someone asks in week two, you've learned something real about who actually needed it, and you can rebuild a much smaller version aimed at exactly that person. Most things you kill this way never come back. That's not a tragedy. That's the audit working.

Shrink it. There's one real reader and they use about fifteen percent of what you send. The monthly client report runs eleven pages and the client looks at the summary and one chart. Cut it to the summary and the chart. You'll be tempted to keep the rest "for completeness." Completeness is the enemy here. Nobody has ever complained that a report they don't read got shorter.

Automate it. Real reader, real use, but a human is assembling it by hand from three systems every week. This is the honest home for most of what survives the audit, and it's where the actual hours come back. Pulling numbers out of a CRM, formatting them, dropping them into a template, and sending them is exactly the shape of work that Make was built for. Trigger on a schedule, pull from the sources, format, deliver. Once it's built you stop thinking about it, and the report that used to eat two hours every Monday eats zero.

The same logic applies to the meeting notes nobody writes properly. If your recurring meetings generate action items that need to reach people who weren't in the room, a tool like Fathom will produce the summary and the action list without anyone taking notes at all. The output improves and the labor goes to zero, which is a rare combination.

Keep it as is. Some things survive intact. Real reader, real use, appropriate effort. Fine. Leave it alone. But make yourself say it out loud, because "keep it as is" should be a decision you make rather than a decision you inherit.

Want the whole thing done for you?

The AI Workflow Blueprint is the system I use to take a business from scattered manual outputs to a running set of automations, including the exact audit sheet, the four bucket decision rules, and the build patterns for the automations that actually survive contact with a real week. It's forty seven dollars. Reply with BLUEPRINT and I'll send it over.

Here's the failure mode I see most often, and I want to name it because it will happen to you if you're not watching for it.

People run the audit, feel great, kill six things, and then never look at the hours.

You didn't do this to have a tidier list. You did it to get time back. And time you get back without a plan doesn't stay got. It fills. Within about three weeks the space where the useless report used to live has been quietly colonized by something else, probably something equally useless, and you've netted nothing except the satisfaction of having run an audit.

So finish the job. Add up the hours. Be conservative and be specific. If you killed a weekly report that took ninety minutes, that's six hours a month. If you automated the client summary that ate a morning, that's four hours a month. Write the total down.

Then assign it before it disappears. Not to a category, to a thing. The four hours go to the sales follow up you've been meaning to systematize. The six hours go to the offer you keep saying you'll build. Put it on the calendar as a recurring block with a name on it, so that when the space opens up it already has an occupant.

If you genuinely have no idea where your hours are currently going, that's a separate problem and it's worth solving first. Running something like Rize for two weeks before you do this audit will give you an actual picture rather than the one you've assembled from memory, and the picture from memory is always wrong in the same direction. Everybody thinks they spend more time on strategy and less on assembly than they do.

Let me make it concrete, because "audit your outputs" is the kind of advice that sounds fine and gets ignored.

A twelve person agency I talked to ran this in July. Thirty one recurring outputs on the list. They could name a confident reader for fourteen of them. Seventeen were question marks.

Of those seventeen, nine had no reader at all. A weekly capacity report that the operations lead had built during a crunch two years earlier and kept sending after the crunch ended. A client health dashboard that nobody had loaded in five months. A Monday priorities email that three people had filtered into a folder they never opened. A monthly competitor summary that took a junior about four hours to assemble and that the founder admitted, when pressed, he had skimmed twice all year.

Six more had exactly one reader who used a fraction of the content. Those got cut down rather than cut out. The eleven page client report became two pages. The all hands deck went from twenty two slides to nine, and the meeting got shorter as a direct result, which nobody predicted but everybody appreciated.

Two were genuinely load bearing and just badly built. A human was pulling numbers from three systems by hand every Friday. That became an automation in an afternoon and now runs without anyone thinking about it.

Total recovered: a little over fifty hours a month across the team. Not from working harder, not from a new tool, not from a productivity system. From noticing that a third of what they produced was going nowhere and having the nerve to stop.

The founder's reaction is the part I remember. He wasn't surprised by any individual item. He was surprised by the total. That's the normal reaction, and it's the reason the audit works at all. Each piece of dead work is too small to notice on its own. You only ever see it in aggregate, and you only see the aggregate if you deliberately go looking.

One more thing and then go run it.

Do not turn this into a project. Do not build a committee. Do not create a tracking sheet for the tracking sheet. The entire value of this audit lives in it being cheap enough to actually finish this morning, and the fastest way to kill it is to make it important.

Ninety minutes. One list. One column for the reader. One decision per row. Kill, shrink, automate, or keep. Total the hours, assign them, and get on with your week.

Then put it on the calendar for ninety days out and do it again, because this stuff regrows. Every business is constantly manufacturing new obligations, and none of them come with an expiration date attached. The audit isn't a fix. It's maintenance. The businesses that stay fast aren't the ones that never accumulate junk, they're the ones that clear it on a schedule instead of waiting until the weight becomes obvious.

You're going to find something embarrassing today. Everybody does. Somebody has been building a thing for eighteen months that nobody has opened since the second week. When you find it, resist the urge to make it a whole conversation about accountability. It isn't a failure of anyone's judgment. It's just what happens when a system has an on switch and no off switch.

Add the off switch. That's the entire job.

Ready to build the machine instead of just clearing the clutter?

Clearing dead work gets you the hours. What you do with them is the actual business. Inside the AI Business Accelerator we take those recovered hours and put them into systems that compound, the follow up that runs itself, the content engine that doesn't need you, the client reporting that builds while you sleep. It's ninety seven dollars and it's for owners who want the whole thing wired together rather than another tool sitting in a tab. Reply with ACCELERATOR and we'll get to work.

Jordan

The AI Newsroom | Jordan Hale | ainewsroomdaily.com