TL;DR
Lean operations, as I run it, is not a process toolbox or a cost cut. It is the discipline of removing the structural cost of a process so the saving persists, and putting the freed time on work worth doing.
What “lean operations” means
As I use the term, lean operations is diagnosing where a process spends human time it should not, re-engineering the mechanical layer so the cost drops to its structural minimum**, and freeing the time for the work worth doing.
That is the method behind the systems that scale work. A process’s cost is usually built into how it runs, and the model says to change how it runs rather than accept the cost as permanent.
Why it matters
A process’s cost is usually structural: a step that should not exist, a loop that never closes, a hand-off no one owns. Trim what the operation produces and the cost falls once, then returns, because nothing about how the work runs has changed.
Lowering a cost is short-lived if the process that produced it stays. Lowering the structural cost is the saving that persists.
That distinction separates this model from a vague “efficiency” compliment and from plain cost-cutting. It is also the first thing I look for in an operation: not where the money goes, but which part of the process makes the work expensive in the first place.
What it looks like in practice
Two builds from the same founder-era operation show the mechanism, and I keep each to the mechanism itself, not the full engagement. I built the first alone; on the second I worked with the team that handled the inbox.
- The first was a fortnightly newsletter whose production took five half-days and came down to half a day once I removed the integration step that forced a manual desktop-publishing pass on every issue. The fix was not to write faster or publish less often. The full report is its own piece.
- The second was a customer-service inbox drawing 80% of one role’s time. Rather than strain the inbox harder, I closed a feedback loop that routed client complaints back into website improvement, so the site removed the root cause of the emails over time. Cleaner filtering and a categorized contact form helped; the volume came down to 30% of that role’s time while the sites absorbed up to 1.3 million monthly unique visitors.
What it is commonly confused with
Three terms sit close enough to be mistaken for this one, and the differences are what carry the definition.
- The factory-floor vocabulary of lean manufacturing (kaizen, kanban, muda, and Andon) is a toolbox for a production line, not a method for any process. I apply an owner-level principle wherever work spends human time it should not, in plain operating terms, with no factory vocabulary attached.
- Plain budget-cutting trims output: it lowers cost once and the quality falls with it. Lean operations removes the structural cost of the process, so the saving holds and the output and its quality stay intact. What gets cut is the reason the work was expensive, never the work itself.
- “Efficiency” as a vague compliment names nothing verifiable. This model names its mechanism: automate what is automatable, re-engineer the mechanical layer, and free the human time. It is evidenced by named outcomes rather than an adjective.
Where to go next
The model is one discipline, and these are the pieces where it does the work:
- The editorial-priority algorithm, built and adapted across two businesses.
- The AI-era engagements, where the same instinct shows on both sides of the shift.
- The mechanism deep-dive, for how the scoring actually decides.
- The decision system re-aimed at a second business and then into a product.
The about page is where the operator behind the model sits.
If you are running a process you suspect is carrying structural cost, let’s talk about where the cost actually lives.