When great employees take a vacation, does critical insight take time off too?

The dreaded vacation. No, not yours. Theirs.

I’m talking about when your co-worker takes one. Not just any co-worker, but that one. The person with decades of experience, adored by customers, running their own parallel operating system, and carrying more tribal knowledge than could ever be transferred in the frantic afternoon before they disappear for two weeks.

You’ve got that person in your head already. Good. The one I think of fits that description perfectly. Let’s call him Chuck. That was his actual name.

Chuck was a machine.

Chaotic. Dangerous. Ill-tempered at times. Constantly stressed. And yet somehow one of the best salespeople I’ve ever worked with. Customers loved him. Internally, everyone relied on him. He managed an incredibly complex customer base with what felt like orchestrated precision. The problem wasn’t Chuck. The problem was how Chuck worked.

He didn’t trust the CRM. He didn’t care for modern desktops. Email was a necessary evil. His tools of choice were a dull pencil, stacks of Post-it notes, and handwriting that made a doctor’s prescription look like a professionally typeset document.

And thirty years of experience.

Watching Chuck work was impressive. Watching Chuck leave for vacation was terrifying.

“You Should Be OK. Everything’s on Cruise Control.”

Before he left, Chuck would always do his version of a handoff. He’d point to Post-it notes. He’d gesture toward piles of paper. He’d explain which order set lived where inside a Jenga-like tower of documents that looked ready to collapse at any moment.

He’d say, “Everything you need is right here.” It never was.

Without fail, the moment Chuck pulled out of the parking lot and said, “You should be OK, everything is on cruise control,” we realized he forgot to tell us what we were cruising into. Because that’s when it happened.

A customer needed special pricing clarified. Another wanted to know where a shipment was. Someone needed certs. Someone wanted to add material to an order already in process. Someone else called about packaging. Another about tolerances. Another about whether a shipment was supposed to be blind.

It was as if Chuck’s customers waited for him to leave before they needed anything.

And the truth was uncomfortable. Without Chuck, nobody actually knew the full story behind those accounts. We had fragments. We had guesses. We had notes. What we didn’t have was shared context.

Tribal Knowledge Feels Efficient. Until It Isn’t.

For a long time, Chuck’s way of working was tolerated. Even admired. After all, things usually got done. Orders shipped. Customers stayed loyal. Revenue came in. From the outside, it looked like a success but under the surface, the business was balancing on a single point of failure.

Tribal knowledge feels fast because it avoids friction. No documentation. No standardization. No need to explain decisions to a system. Everything lives in someone’s head. Until that head is on vacation. Then the cost shows up quickly.

We had “almosts.” Pricing mistakes that had to be honored. Return shipments due to incorrect packaging. Blind shipments that weren’t blind. Missed tolerances that nearly became scrap. Fires that needed to be put out quietly and expensively. None of this happened because Chuck was bad at his job. It happened because the company relied on him instead of relying on information that could be shared.

Eventually, after enough close calls, we forced the issue. Chuck had to start using the tools in front of him. Not because tools are magical, but because the business couldn’t keep absorbing risk every time he took time off.

Tribal knowledge was great until it worked against us.

The Real Lesson Isn’t About CRMs or Software

This story isn’t about forcing people to use systems they hate. It’s about something far more practical and far more important. It’s about capturing information in a way that survives people.

Small and mid-sized manufacturers live and die by experience. That experience is valuable. But when it isn’t translated into something others can access, understand, and act on, it becomes a liability. Ask yourself a simple question:

If your most experienced person disappeared for two weeks, could someone else step in without breaking promises, margins, or customer trust?

If the answer is no, the issue isn’t staffing. It’s knowledge transfer.

What Needs to Be Captured (And What Doesn’t)

Not everything needs to be documented. That’s where companies go wrong and people like Chuck revolt. What does need to be captured is decision-critical information.

• Why does this customer get special pricing?

• What tolerances are non-negotiable?

• Which certs are required every time?

• What assumptions are baked into recurring orders?

• What promises have been made that aren’t obvious on paper?

This information doesn’t belong in someone’s memory, handwriting, or desk drawer. It belongs in a shared, standardized format that others can interpret without translation. That doesn’t require enterprise software. It requires intention.

Standardization Isn’t About Control. It’s About Continuity.

Standardization gets a bad reputation because it’s often imposed poorly. But at its core, standardization is about making sure information means the same thing to everyone who touches it.

When information is standardized:

• Stand-ins don’t have to guess.

• Customers don’t feel the absence of a single person.

• Mistakes don’t multiply quietly.

• Vacations stop being operational threats.

• More importantly, the business becomes resilient instead of reactive.

Chuck didn’t need to stop being Chuck. The business needed to stop depending on him being everywhere, all the time.

The Anti-Consulting Message

Most manufacturers don’t need another system demo. They need someone to help them identify where tribal knowledge is silently holding the company hostage.

Where are the Chucks?

What decisions live only in people’s heads?

Which customers are one vacation away from chaos?

What information, if lost for two weeks, would immediately hurt revenue or reputation?

That’s the work that creates value. Not by ripping out processes, but by translating experience into shared understanding. By capturing what matters, standardizing it just enough, and ensuring the business can function when people step away.

Because vacations shouldn’t be operational risk events.

They should just be vacations.