A while ago I had dinner with the owner of an industrial parts company. His is the kind of company you have never heard of, but if it stopped, a whole industry somewhere in the world would have to halt its lines. A hidden champion. Several hundred million NT$ in revenue a year, steady profit. I asked him, almost in passing: "Mr. Wang, the line from taking an order to shipping it — if the veteran who runs it took a long leave tomorrow, could the company keep going?"
He smiled and didn't answer right away. After a few seconds he said: "Johnny, that's the exact thing that keeps me up at night."
I'm Johnny Yang. Seven years of back-to-back startups, and my team has done 252+ digital implementation projects across 32+ industries. This post isn't selling a course and isn't trying to scare you. I just want to lay out, clearly, the same time bomb I've seen again and again across those 252+ projects.
The conclusion first: no matter how high revenue is, if operations are locked in a few veterans' heads, succession is a time bomb
I'll put the most important point first. If you don't have time to read past this section, that's fine.
Taiwan has plenty of hidden champions with good-looking books and more orders than they can handle. But the company's real core operations — how quotations are priced, how materials get allocated, which customer you can't upset, who to call when a step goes wrong — are not in any system. They live in a few veterans' heads, a stack of paper, and a pile of Excel files only one person can read.
Day to day, this works. Because those few people are still here, and they still remember.
The problem is that succession and generational turnover will come. The second generation takes over, senior people retire, and suddenly you find out: how the company runs was never written down, never systematized. It was all in people's heads. Once those people leave, there's no handover, and the whole company is working blind.
Revenue can't cover this gap. You can earn several hundred million NT$ a year and still not fill the hole left when "the only person who knew how it works" walks out. That's what I mean by a time bomb. It's not a question of whether it goes off. It's waiting for its moment.
I. Why are hidden champions especially likely to step on this mine?
It's not that these owners are foolish. The opposite — they're formidable. But precisely because they're so good at making money, they're especially prone to growing this mine. Here are the reasons I've seen.
1. Making money comes first, digitization always comes later
The logic of a hidden champion is simple: win the order, ship the goods, collect the money. For decades that playbook kept winning. Who had time to stop and systematize anything? "We'll get to it when we have time" gets said for twenty years, and then there's never time.
2. Almost no real IT foundation
In many of these companies, the entire "IT department" is one very capable accountant plus an old server that's been running for years. It's not that they have no ERP. It's that nobody touched the system after it went live, so it became an empty shell used only to issue invoices. The real operations run by hand, outside the system.
3. Workflows that haven't changed in decades
"This is how we've always done it." I've heard that on site more times than I can count. The processes weren't designed. They accumulated over years, passed along by word of mouth, layer on layer. They work, but nobody can describe the whole picture, because it has never existed in any document.
4. Held together by veterans' unspoken understanding
This is the critical one. A company's real moat is often a few veterans who've been there twenty or thirty years. They know which supplier you can push, how to squeeze in a rush order, and what's behind a given quotation that can't be written on paper. This is tacit knowledge. It's valuable, but it exists only in people's heads, with no backup.
If the idea of Excel holding up an entire company sounds familiar, I wrote a more detailed piece on where Excel management hits its limit, so I won't repeat it here.
II. What does it look like when this bomb goes off?
I've taken this apart with clients many times. Here are a few scenes that really happen. Compare them with your own company.
Scenario one: someone leaves, and the handover fails. On the day the veteran retires, the handover is a stack of notebooks and a few Excel files handed to the successor, with "call me if you have questions." Once he's gone, the successor calls him three times a week. The company is effectively still being run by someone who has already retired. That isn't a handover. That's delaying the detonation.
Scenario two: the second generation can't make sense of it. The second generation is capable, educated overseas, knows digital. But the moment they walk in, they're stunned — none of their father's setup is systematized. It all runs on the veterans' "feel." If they try to change it, the veterans think they don't get it. If they don't, the company stays stuck in the previous generation's heads. The gap between generations usually isn't about mindset. It's that there is no shared, readable system they can both stand on and talk about.
Scenario three: key customer relationships break with one person. A few major customers have been handled by one veteran for twenty years. When that person retires, the customer's purchasing habits, sore spots, and personal ties all reset to zero. A competitor only needs to send in one diligent salesperson, and twenty years of relationship can be pried away in a year.
I've seen these three over and over in 252+ projects. They have one thing in common: everything valuable sits with people, and none of it sits with the company.
III. How to defuse it: systematize the tacit processes before the handover
The core idea fits in one sentence: while the key people are still here, still remember, and are still willing to talk, turn what's in their heads into a system.
Mind the timing — it has to be "while they're still here." If you wait until they've left to patch it, that isn't defusing a bomb. That's disaster recovery, and the cost and pain are ten times higher.
In practice, I usually walk clients through three steps:
- First, find the few lifeline processes that truly run on someone's memory. Not the whole company at once. Lock onto the critical steps that break if one person is gone. Quotation, scheduling, key customers, special processes — it's usually just those few.
- Dig out the tacit knowledge, write it down, and turn it into process. This step takes the most effort, because the veterans themselves can't explain it clearly — they work "by experience," not "by rules." It takes interviews, running the whole process alongside them, and asking every "why did you decide that" until you hit bottom. I wrote a separate post on what to actually ask and which layer to record: what to do when the company's know-how is in veteran employees' heads. It also covers what you don't need to record at all.
- Connect the process to a system so it no longer depends on specific people. Move the company's operating logic out of people's heads and into a system. People can change. The process stays.
If your company can't yet sort out step one — which processes count as core — start with the first step of digital transformation for SMEs, where I explain how to get started in plain language. If you want to go straight to selection criteria, I've put the succession angle into choosing an ERP for traditional manufacturers: check these 3 criteria first.
One more thing: this time bomb has an earlier warning sign — the owner can't take a vacation. When every decision, big or small, waits for the owner's nod, it's the same disease as veterans locking processes in their heads. The only difference is that the person holding the lock is the owner. I break that one down in Owner can't take a vacation? How to turn judgment into a system.
IV. The Brightstream approach: don't tear it down, keep the knowledge with API integration and cross-department co-creation
At this point, many owners voice their biggest fear: "Johnny, does this mean I have to replace everything that's been running for decades?"
No. And I'm strongly against doing that.
The way a hidden champion has worked for decades contains a lot of know-how that money can't buy. Tear it down and start over, and you cut away the company's most valuable asset along with it. Many implementation projects fail, and half of them die from exactly this arrogance of "knock it down and rebuild." I broke down several common ways they die in why ERP implementations fail.
Brightstream's approach is the opposite of "replace the system." Two core points.
1. Use APIs to connect existing systems instead of replacing them
Your current ERP, your inventory system, those Excel files, even the old server — as long as they still work and people are comfortable with them, we leave them in place. What we do is use APIs to connect these existing systems, so data flows between them automatically, and fill in the steps in between that depend on someone moving data by hand or remembering it.
In other words, we're not tearing the house down to rebuild. We're opening doors between the rooms and connecting the plumbing and wiring. The original things stay put, but the whole building starts working together. Side note: many people can't tell the difference between an inventory system and an ERP. I wrote inventory system vs. ERP: what's the difference, which pairs well with this.
2. Cross-department co-creation to draw out what's in the veterans' heads
The hardest part of systematizing tacit knowledge isn't the technology. It's how to dig out experience the veterans can't put into words. There's no shortcut. Our approach is cross-department co-creation, round by round:
- Interviews: not "what is your job," but running through it with them and asking the "why" behind every decision.
- Testing: turn the documented process into a prototype and have the people who actually use it try it out, instead of the owner signing off alone.
- Feedback: the people on the floor will always say "this part is wrong, actually we do it like this." That feedback is the gold.
- Refinement: revise, test again, revise again. After a few rounds, the tacit process that only lived in someone's head becomes an explicit process everyone can read and the system can carry.
This process has a hidden benefit: because everyone built it together, the veterans don't feel you're taking their job or dismissing decades of their contribution. They actually feel a sense of achievement — a lifetime of experience is finally being properly preserved. During a succession, that matters more to the internal mood than anything else.
For a fuller picture of how a system ties all this together, see the SME ERP implementation guide.
V. Quick comparison: "no system" vs. "with a system" before succession
| Situation | No system (runs on memory) | With a system (tacit knowledge preserved) |
|---|---|---|
| Veteran retires | Handover is a stack of notes plus endless follow-up calls; no real handover | Processes are in the system; work continues after they leave |
| Second generation takes over | Can't make sense of the father's setup; stuck between changing it and not | Standing on a readable system; can discuss and improve it |
| Key customers | Relationship tied to one person; customer leaves with them | Interaction history and unwritten details are in the system; a new person can take over |
| Firefighting when things go wrong | Only a few people know how to fix it | Process is traceable; several people can handle it |
| Company valuation | The moat is "people," and people are a variable | The moat is "system + process," which can be passed on |
VI. Busting the myth: "We've done it this way for decades with no problems"
This is the most comforting sentence, and the most dangerous one.
"Decades with no problems" is true. But it proves there were no problems in the past, not there will be no problems at succession. The risk structure of those two things is completely different.
There were no problems in the past because those few key people were always there. The stability of the whole setup was built, from start to finish, on the assumption that "these people won't leave." Succession, retirement, and generational turnover are exactly what breaks that assumption.
A blunter analogy: an old machine running thirty years without breaking down doesn't mean it won't break tomorrow. It only means you've never replaced the one veteran who knows how to fix it. When it's time to replace him, you discover nobody else in the company knows how it works — and at that moment, "decades with no problems" becomes "decades with no preparation."
I'm not asking you to reject the past. I'm asking you to save the past's success while there's still time.
VII. Ask this one question before you sign
Whoever you end up working with — Brightstream or someone else — before you sign, I suggest asking this question face to face:
"Are you going to replace our current systems, or connect what we have now and keep it?"
If the first thing they say is "this is too old, scrap it all and put in ours," be very careful. What they want to touch may well be your company's most valuable tacit asset from the past few decades, the one thing that should never be scrapped. People who actually understand succession in traditional manufacturing will first ask you "what can't be touched, and which people must be part of the co-creation" — not rush to tear everything down.
FAQ
Q: We only have a few dozen people. Do we need this kind of systematization too? Yes, and small companies need it more. Fewer people means fewer backups for each critical step. One veteran can be worth half the company, and when they leave, the impact is harder than at a large company. Systematization isn't a privilege of big companies. It's insurance every company that runs on a few people should have.
Q: What if the veterans won't cooperate because they're afraid of being replaced? This comes up in almost every project. The key is the approach. If it's "bring in a consultant to record his job and then replace him," of course he'll resist. But with co-creation, he becomes the "author" of the system, not "the person being copied," and his experience is formally preserved as a company asset. Most veterans actually take pride in that. Get the mood right, and cooperation isn't a problem.
Q: Is connecting via API without tearing things down really cheaper? In total cost and risk, usually much cheaper. With a full replacement, you pay not just for the system, but for the whole company relearning everything, the resistance, and the mistakes during the transition. Connecting existing systems via API keeps what people already know how to use and only fills in the broken links. Implementation is faster, the pain is smaller, and the original know-how is preserved.
Q: How long does it take? Will it stall halfway? It depends on how many core processes you're tackling, but I always recommend starting with the one or two most likely to break, not rolling out across the whole company at once. Defuse the most dangerous bomb first, see results, build internal confidence, then expand step by step. AI has also made many steps faster in recent years. If you're curious how far a system can go, see what AI combined with ERP can actually do.
If you finished this thinking "this is exactly our company," that's not a bad thing. It means you've seen this bomb earlier than most. Brightstream offers a free 30-minute diagnostic of your processes. Together we'll find the lifeline processes your company leans on memory for most, and work out which bomb to defuse first before succession. No sales pitch, no course. Just marking where the bombs are. If you want to talk, pick a 30-minute slot online. Reach me anytime. Johnny Yang.




