LEANTA · Field Notes
Notes from the floor,
not from a binder.
We publish the method. These are working notes on how Lean, self-improving operating systems actually get built — and how they keep running after the expert leaves. No hype, no fear-selling; a number only when we can stand behind it.
Why operational gains decay after the expert leaves
The single most common failure in operations improvement isn't getting the win — it's keeping it. Why gains erode, and the one structural change that stops the slide.
~5 min read →
AutomationThe four guards every automation needs
Verification, monitoring, fallback, and a cost cap — plus a human gate on anything irreversible. The checklist we run before a single automation touches a live business.
~6 min read →
ManufacturingWhat OEE actually measures (and why "85%" usually isn't)
Availability × Performance × Quality. Where the famous "world-class 85%" comes from, why a clean-looking line still scores in the sixties, and what the number is really telling you.
~6 min read →
PrincipleMeasure first: the number we won't promise
Why LEANTA refuses to quote a result it hasn't baselined — and why "what gets measured gets managed" is a warning, not a slogan, once you know who actually said it.
~5 min read →
New · LEANTA Dictionary
The operator’s dictionary
The terms behind these notes — OEE, SMED, micro-stops, automation bias — defined in plain language, each with an operator’s layer: first lever, common misreading, what good looks like. A new term lands every fortnight.
Want the method applied to your floor?
Reading is free. If a note here describes a problem you actually have, the next step is a short, plain conversation — no deck, no pressure.