Kill the Process Before You Optimize It
Most business processes exist to solve problems that no longer exist. Eliminate the process before you waste time optimizing it.
Key takeaways
- Question whether a process needs to exist before you spend a single hour optimizing it.
- Recognize that entrepreneurs are wired to seek problems, which means you will sometimes manufacture problems to solve.
- Trace every workflow back to the original problem it was built for. If that problem is gone, the workflow should go with it.
- Ask your actual customers what bothers them. Your assumptions about their problems are often wrong.
- Make it every team member's job to question whether their own work is necessary, including their role itself.
Timestamps
Show notes
What This Episode Is About
Paul Veth argues that the biggest drag on business performance is not a lack of optimization. It is processes that should never have existed in the first place. Before you refine a workflow, ask whether the workflow needs to exist at all.
The Utility Company That Could Not Cook
Paul called his energy provider to switch from gas to induction. The process: wait for the plumber to cut the gas, then wait for the power company to enable induction, possibly days or weeks apart. No cooking in between. Nobody at the company had questioned this sequence. Paul's fix: do not let the plumber in until the power is switched. The woman on the phone laughed. He was serious.
The Tesla Noise Reduction Division
In his book, Elon Musk describes a whole division working on what they believed was noise reduction. The fire safety team thought the noise team was handling a safety requirement. The noise team thought fire safety had signed off on the need. Nobody had. The solution was tested with and without the fix. It made no difference. The entire division was solving a problem that did not exist, at significant cost in time, money and engineering hours from the battery team.
Key Insights
- Entrepreneurs are wired to find problems. That instinct makes you look for problems even when there are none.
- Solving a non-existent problem creates a new one: you now have to maintain and optimize the solution.
- Most processes were built for a real problem. When that problem disappears, the process stays and becomes the problem.
- The simplest path to solving your customer's actual problem is eliminating everything between you and them that does not need to be there.
- Ask your customers what their real problems are. What you assume they struggle with and what they actually struggle with are often different things.
The Question to Ask Before Any Optimization
Paul's framework here is straightforward: identify the one thing your business exists to solve for the customer, then remove every step that does not directly serve that outcome. If a step cannot justify its existence against that single purpose, it should be cut. This connects directly to the Identity First principle behind everything Paul builds: start with what is essential, not what has accumulated.
Topics
Full transcript
View full transcript
Frequently asked questions
How do you know if a business process still needs to exist?
Trace it back to the original problem it was built to solve. If that problem no longer exists, or was never a real problem in the first place, the process has no reason to stay. Test it by removing it and seeing whether anything actually breaks for the customer.
Why do entrepreneurs keep building solutions to problems that are not there?
Entrepreneurs are wired to find problems. That instinct is useful, but it also means you will sometimes manufacture problems just to have something to solve. The fix is to validate the problem with real customers before you build anything around it.
What did Elon Musk find inside Tesla's noise reduction division?
The division was working on a solution that two teams had each assumed the other had requested. When they tested the car with and without the fix, there was no measurable difference. The entire team was eliminated because they had been solving a problem nobody actually had.
What is the simplest way to improve how your business serves customers?
Identify the single most important problem your customer needs solved, then eliminate every step between your business and that outcome that cannot directly justify its existence. Elimination beats optimization when the underlying process should not be there.
Should employees question whether their own role is necessary?
Yes. Paul's position is direct: it is your job to kill your own job if that job is not genuinely necessary. Businesses that reward people for defending unnecessary work accumulate waste. The better culture is one where removing friction is seen as a contribution, not a threat.
Related episodes
Get in touch
Want to learn more or collaborate? Feel free to reach out.
Get in touchDiscussion
The content makes a sharp claim: most processes exist to solve problems that no longer exist. What is a process in your business you kept running longer than you should have, and what made it hard to kill it before you tried to fix it?

