The job that stops when one person calls in sick

The growth plan gets approved on Monday. On Tuesday, your setup lead tells you he retires in March, and line 3's changeover steps leave with him.

You've probably lived some version of that. A quote waits because one estimator is out. Second shift runs slow because the person who knows the old press works days.

I call that the enabling layer: the thing everything else sits on, and you don't notice it until it breaks. I learned to look for it at Naval Nuclear Power School and kept looking through 30 years in plants. Find what everything else depends on. Fix that.

In a plant, that's the know-how in your strongest people's heads. If it lives in three people's memory, more equipment or another shift won't help. It just adds weight to the same people.

What to do this week

Pick one critical job. Have your most experienced operator walk it while someone records the steps and the "watch for this" moments on a phone. Put it where the floor already works, with one owner and a visible revision date. Then make one rule: every time someone finds a better way, the document changes that week.

One job a month, and in a year you've removed twelve single points of failure.

That's the habit MaxKnowledge, a Knowledge and Recursive Improvement Platform, builds inside the Microsoft 365 your team already uses. But you don't need us to start. You need one job, one operator and a phone.

Which job in your plant would stop if one person called in sick tomorrow?