You're perfecting something that should be deleted

Hey Warblers,

Something is eating your time.

Not the difficult stakeholder. Not the 4:30 Friday meeting nobody wanted.

Those are problems you can name. The real problem is the work you can't see anymore, because it's been there so long it's become invisible.

The weekly status report you've sent every Friday for two years. The approval process built for a vendor relationship that ended. The recurring sync your team inherited from the team before them.

You didn't build most of this. You inherited it. And because none of it was obviously wrong, you optimized it. Made it faster. Made it cleaner.

Here's what nobody tells you: the most dangerous thing you can do is get good at something that shouldn't exist.

Atlassian's latest research on workplace meetings found that 78% of knowledge workers say they attend so many meetings, it's hard to get their work done. Even worse: 62% of those meetings never stated a goal in the invite.

That's not a meeting problem. It's a sequencing problem. Organizations are relentlessly optimizing processes, making them shorter, adding AI summaries, building better agendas, without first asking whether the process should exist at all.

The best productivity tools in the world cannot fix a process that should have been deleted.

Toyota's production system, developed by engineer Taiichi Ohno starting in 1948, is one of the most replicated management frameworks in history. The core idea is deceptively simple:

Ohno called waste muda: any activity that consumes time or resources without adding value. His insight was that most organizations skip straight to optimization. They make broken things faster. They automate inefficient processes. They train people to execute tasks that should have been deleted entirely.

The sequencing error is the error. Fix that, and everything else becomes easier.

Here's the sequence. Skip ahead and you encode the problem permanently:

Most people start at Step 3.

They see something slow and they optimize it. They see something manual and they automate it. The lean manufacturing community has a name for this: over-processing. It's one of Ohno's seven categories of waste, and it's the most invisible one because it looks like productivity.

If you've ever built a better dashboard for a report nobody reads, you've done this.

Every recurring task, standing meeting, and scheduled deliverable you own should be traceable to a human being who made the original decision to require it. Not "the legal team." Not "leadership." A name.

When requirements belong to departments instead of people, they become permanent by default.

Here's what this looks like across functions:

Engineering: An infrastructure team runs weekly capacity reports every Monday. Step 1 reveals those reports were required by a VP who left eight months ago. The current VP has never read one.

Product: A PM runs a 14-day sprint review cycle before every launch, traced back to a compliance requirement in a client contract that expired. Nobody updated the process.

Marketing: Every campaign goes through three rounds of brand review. A creative director implemented this after a compliance incident in 2022. That incident was resolved with a different fix in 2023. The review cycle was never deleted.

None of these people are doing bad work. They're doing the right work in the wrong sequence.

Once you've found the owner and the original reason, the question is not "how do I make this better?"

The question is: what actually happens if this disappears tomorrow?

Run this test on everything you own. If it disappeared tomorrow, who would notice, and why? If the answer is "nobody important, for no defensible reason," that is your answer.

Ohno distinguished between two types of waste.

Most of what's eating your time is Type 2 wearing the costume of Type 1.

Shopify ran this at company scale in January 2023. They deleted all recurring meetings with more than two attendees and blocked Wednesdays as a no-meeting day. They didn't try to make bad meetings better. They deleted first, then rebuilt only what they actually needed back.

What made it through Steps 1 and 2 actually deserves your attention. Now strip it down. Remove approvals that don't change the outcome. Combine steps that happen in sequence for no reason. Cut the process to its minimum viable version before you try to make it faster.

Only after simplifying do you speed things up. Shorten the feedback loop. Reduce the time between request and delivery. Move a weekly report to biweekly. Compress a 5-day approval chain to 48 hours. You're not skipping steps anymore. You're compressing the ones that earned their place.

Toyota's philosophy was to first work a process thoroughly by hand, eliminate the waste, and only then build machinery around it. Automate the optimized version, not the original. Because if you automate a broken process, you've encoded the inefficiency permanently and made it harder to see.

Every AI workflow you've built on top of a process nobody questioned is potentially doing exactly that.

Block one hour this week. Open a blank document. List every recurring task, meeting, and deliverable you own. For each one:

Delete anything where you cannot confidently answer all three.

You will find three to five things you can eliminate immediately. That time does not go to the next item on the pile. It goes back to you.

After your 60-minute purge, paste what survived and what got cut. Use this prompt:

Pick one simplification and one new activity from the output. Ship both this week. The time you recovered doesn't stay free for long.

You are not behind because you are not working hard enough.

You are behind because 60% of your week is scaffolding around work that might not need to exist.

Delete before you optimize. The sequence is the strategy.

~ Warbler