The Work That Shouldn't Exist
Work doesn't get killed because it's useless. It survives because nobody's ever forced to justify why it's still there.
That's not laziness. It's just how organizations actually work.
Ask most owners what their team spends time on, and they'll describe the job title. Ask what their team actually did yesterday, and you get a different answer: a status update nobody acted on, a report that got forwarded and never opened, a review step that exists because it always has.
None of this gets decided. It accumulates. Someone adds a check-in during a rough quarter, and the rough quarter ends, and the check-in doesn't. A process gets built around a person who's since left, and three reorganizations later nobody remembers it was built around anyone at all.
Asana's Anatomy of Work Index put an actual number on it: the average U.S. knowledge worker loses 308 hours a year, nearly eight full work weeks, to duplicated effort and work that's already gone stale. Bloomberg's reporting adds unnecessary meetings on top of that, at roughly $25,000 per employee, per year, in salary spent on nothing. Run a ten-person team and that's close to a quarter million dollars a year, and nobody bought it on purpose. It just kept happening.
I once took over professional services at an enterprise storage company with zero visibility into what my own department was already producing. Seven months in, an IT reorg surfaced four monthly performance reports that had been going out to regional VPs the entire time. I'd never run one of them. Not a single VP ever asked where they went.
Issue 1 was about sorting what's actually on your plate. Issue 2 pointed straight at this one before it happened: the work that shouldn't exist at all. Neither of the first two issues works if the plate itself is full of things nobody decided to keep. This is where that gets fixed. Not delegated, not documented. Removed.
This week, one small move. Complete on its own, no follow-up required.
First Move
One small move. Complete on its own.
Pick one recurring task, report, or check-in your team runs on autopilot. Find out, directly, who consumes it and what they do with it. If the honest answer takes more than one sentence to explain, that's already a warning sign.
Cancel it for one cycle. Don't announce it as permanent. Just skip it once and see who asks where it went.
Below this line is what subscribers get once the paywall goes live at Issue 5: the deeper exercise and a four-prompt pack. Find the orphans, find the duplicates, price the waste, replace the meetings. For now, through Issue 4, it's yours free, no catch.
Field Application
The exercise. Every issue ends with one of these.
01. List It
List every recurring task, meeting, and report your team runs on a fixed schedule.
02. Name the Consumer
For each one, name the specific person who consumes the output and what decision or action it drives.
03. Flag It
Anywhere you can't name a consumer, or the consumer just forwards it without acting on it, mark it for removal.
04. Cut It
Cut everything marked in the next two weeks. Not "revisit next planning cycle." This cycle.
AI Edge
You can audit your own calendar. You can't easily audit everyone else's, and that's usually where the real waste hides, three layers below anything you personally attend. Pull your team's recurring task list or meeting schedule. Then paste these four prompts into ChatGPT, Claude, or whatever you're using, in order, in the same chat. Each one builds on the last.
Prompt 1. Find the orphans.
"Here is our list of recurring tasks, meetings, and reports: [paste list from above]. For each item, identify who consumes the output, what action or decision it drives, and whether that justification still holds today versus when the item was created. Flag anything where the stated purpose and the actual current use have diverged, or where no clear consumer exists."
Prompt 2. Find the duplicates.
"Using the same list, find items that overlap. Group any tasks, reports, or meetings that produce the same output for the same audience, or that another team already produces. For each group, tell me which one to keep and why, and which ones can go with no loss. If two items look similar but you don't have enough to be sure, ask me before you group them."
Prompt 3. Price the waste.
"For every item flagged so far, estimate the yearly cost. Ask me how often it runs, how many people touch it, and how long each run takes. Use $[hourly rate] as the loaded hourly cost. Rank the flagged items from most expensive to least. Give me the top five to cut first, and for each one, the sentence I'd use if someone asks where it went."
Prompt 4. Replace the meetings.
"Take every recurring meeting on the list. For each one, tell me what actually happens in it: a decision gets made, information gets passed along, or people just show up. If it's a decision, keep the meeting. If it's information, draft the written update that replaces it, under 150 words. If nobody can name what it produces, mark it for removal."
Issues 1 through 4 are free. That stays true.
Starting with Issue 5, every issue splits at the line you crossed above. The narrative and the First Move stay open to everyone. The step-by-step exercise, the prompt pack, and a new tool every month go to paid subscribers, $47 a month. The first 50 paid subscribers pay $27 a month, for as long as they stay.
Join at any point and the paid half of every issue from 5 on opens up. Nothing to catch up on, nothing to unlock one at a time.
If the first three gave you something worth doing, the next ones give you the harder version. Or skip it. The free half still lands every Monday.
That's Issue 3. Every Monday, one problem, one week to act on it.
Work with Eliv8
If any of this sounded like your business, Ground State is the fix. It's a fixed-fee diagnostic that finds where the structure is leaking and puts the answer in writing. See how it works.