Software
That’s how you get into tech debt, stuck with entire infrastructure written in Cobol.
And even for purely UI changes, the UI totally impacts user adoption. Eg, a 90s style grey everything form is going to feel outdated to many users and they’ll associate that with the rest of the software being dated (regardless of whether or not it’s true). If your goal is adoption/sales, you often have to keep changing the UI even if it’s not broke with regards to functionality.
Preventive maintenance? As in, where you take your car in every year for an oil change so it doesn’t end up as one gigantic blob that gums up your entire engine or having your brake pads completely disintegrate, cleaning the lint out of a sewing machine, greasing your bike gears, …
Preventative maintenance for the win. Just bought a 90s DeaDoo, noticed it had the original grey fuel lines. I know that those lines are notorious for breaking down and plugging fuel filters, thus killing engines. However, this SeaDoo ran perfectly as-is. I was too paranoid to just run it like that so I took it apart and sure enough, the fuel filter was all plugged up - probably would have killed the engine if I hadn’t checked and just kept running it
An ounce of prevention is worth a pound of cure.
If you don’t schedule maintenance, your equipment will schedule it for you.
The external struggle in manufacturing:
“My machinery is having too much downtime. It needs comprehensive maintenance.”
Ok, I need 12 solid hours and I’ll give it back to you good as new.
“What?! 12 hours! That’s insanity, it’s already racked up 20 hours of downtime this month, I can’t spare 12 hours! Can’t you just do it next month?”
Repeat every month.
A stitch in time saves nine
