ELS Perspectives — Article 3
Most lubrication programs don’t fail in year three. They fail on day one — before a single drop of oil ever moves. By the time the symptoms show up, the mistake is already years old.
I’ve watched plants launch brand-new lubrication programs with real budget, good intentions, and premium products, and I’ve watched a lot of those same programs quietly fall apart. Not because anyone stopped caring. Because of how they were built in the first place.
The failure was designed in. Here’s where it comes from.
It Started With a Product Instead of a Problem
The most common way a program is born is backwards. Somebody picks the lubricants first — often from whatever’s already on the shelf or whatever came recommended — and calls the resulting list a program. But a list of products is not a program. It’s an inventory.
A real program starts with the machines: the loads they carry, the environments they run in, the temperatures they reach, the speeds they turn. The lubricant is the last decision, not the first — the answer to a question about the equipment. When the product comes first, nobody ever asked the question, and every choice downstream inherits that gap.
A lubrication program built on a product list is a filing cabinet, not a program. The decisions were never made — they were purchased.
Nobody Was Given the Keys
Programs get launched as projects. Someone leads the rollout, everyone shows up for the kickoff, the binders get printed — and then the project ends, and the program is handed to nobody in particular. It becomes everyone’s job, which means it becomes no one’s.
A program without an owner starts decaying the day the rollout ends. There’s no one accountable for keeping the standard current, retraining after turnover, or adjusting when a line changes. It doesn’t fail loudly. It just slowly stops being followed, one shortcut at a time.
A program without an owner isn’t a program. It’s a memo everyone agreed with and no one runs.
It Was Built Around a Person, Not a System
Often the program works beautifully at first — because the person who built it is still standing right there. They know why every decision was made, so they keep it on track by hand. That looks like success. It’s actually the most fragile setup there is.
The moment that person moves to another plant or retires, the reasoning leaves with them, and everyone else is left executing steps they never understood. A program that depends on its architect was never really finished. It just hadn’t been tested yet.
Every program that depends on the person who built it has already scheduled its own failure — for the day that person leaves.
There Was No Standard, So Drift Started Immediately
If the program isn’t written down as a standard — same product, same quantity, same interval, same method, on every shift — then every technician fills the gaps with judgment. Good judgment, bad judgment, it doesn’t matter; it’s different judgment. Three shifts greasing the same bearing three different ways isn’t a program with a problem. It’s three programs pretending to be one.
Drift doesn’t wait for year two. It starts the first week, because nothing was ever pinned down to drift from.
The Setup Was Treated as the Finish Line
The deepest reason programs fail before they start is that they’re designed as a one-time installation. Set the routes, pick the products, train the crew, done. But a plant isn’t static. Loads change, product lines change, ambient conditions change, people change. A program with no mechanism to notice and adapt is aimed at the plant as it existed on launch day — a plant that stops existing almost immediately.
Most programs don’t fail because the plan was wrong. They fail because there was no plan to keep the plan alive.
What This Means for Anyone Starting One
None of these failures are about the products, and none of them are expensive to prevent. They’re about design. Start with the machines, not the catalog. Give the program a named owner before you give it a budget. Put the reasoning in the system, not in a person. Write the standard down. And build in the expectation that the program will change, because the plant will.
A lubrication program isn’t something you install. It’s something you start — and the ones that last are built, from the first day, to survive the second year.
Next in ELS Perspectives — How to Build a Lubrication Program That Survives Personnel Changes: what it takes to put the knowledge in the system so it doesn’t walk out the door with the person who has it.
Ready to move from reading about lubrication to applying it?
Lubrication Mastery is a structured 8-week program for maintenance and reliability professionals who want to build a reliability-led lubrication program — not just understand the theory. Opening later in 2026.
Danny Stephens is a Certified Lubrication Specialist, recognized by the Society of Tribologists and Lubrication Engineers (STLE), specializing in reliability-led lubrication programs across multi-site manufacturing operations. He is the founder of Environmental & Lubrication Solutions, Inc., an independent, manufacturer-neutral lubrication advisory firm based in Kerrville, Texas.
© 2026 Danny Stephens, CLS. All rights reserved.
#Lubrication #LubricationProgram #ReliabilityEngineering #MaintenanceExcellence #LubricationEngineering #AssetCare #Manufacturing #CMRP #ELSPerspectives