There is a grim but necessary question every team needs to ask: What happens to the business if our best employee gets hit by a bus? We call this the "Bus Factor." If the number is 1, you are running a fragile system.
In tech, we often confuse being "indispensable" with being "valuable." We think that if we are the only person who knows how a critical system works, our job is secure.
But being indispensable is actually a trap. Here is how to break out of it.
1. For the Engineer 🛠️
The Trap: The Illusion of Job Security. You built the legacy billing service. You are the only one who knows how to debug it when it goes down at 2 AM. You feel secure because the company "needs" you.
The Reality: If you are the only person who can maintain the billing service, you can never leave the billing service. You cannot be put on the exciting new greenfield project, and more importantly, you cannot be promoted. You have made yourself too essential to move.
The Fix: Make Yourself Replaceable. To move up, you have to fire yourself from your current role.
The "Vacation Test": Take a two-week vacation. If the team panics, you have failed to share knowledge.
Document the Magic: Write down the undocumented "lore" in your head. Turn your complex debugging processes into a runbook that a junior engineer can follow.
Mentor your Replacement: Start actively pairing with a teammate on the system you own.
2. For the Manager 📈
The Trap: The "Hero" Dependency. When a tight deadline approaches, it is incredibly tempting to assign the hardest ticket to the person who has done it a hundred times. It is fast. It gets the sprint across the finish line.
The Reality: Every time you rely on the "Hero", you are creating a Single Point of Failure (SPOF). You are rewarding knowledge hoarding and stunting the growth of the rest of your team. If your hero burns out or takes a new job, your capacity drops to zero.
The Fix: Mandate Redundancy. High-performance teams optimize for resilience, not just speed.
The "Shadowing" Sprint: Next sprint, assign the critical ticket to a different engineer, and have your "Hero" act only as a consultant or reviewer. It will take longer this week, but it will save you next month.
Reward the Teachers: Change your 1:1 conversations. Stop praising people just for shipping code, and start praising them for unblocking others and improving team documentation.
The Insight 🧠
Redundancy is not inefficiency; it is resilience.
A "Brute Force" system relies on a single load-bearing pillar. If it cracks, the roof caves in. A "Resonant" system distributes the weight.
Your homework for this week: Identify one task, system, or process where your team has a Bus Factor of 1. Schedule a 30-minute pair programming or shadowing session this week to spread that knowledge to one other person.
See you next week,
Serhii Klymenko
Creator of The Resonant Manager
P.S. Managing your calendar is hard. Managing your meetings is harder. I'm building Sibyl to act as your AI Co-Pilot during meetings – it transcribes, extracts action items, and tracks your impact so you don't have to scramble to remember what you did at the end of the quarter. [Join the Waitlist Here]
Powered by GetSibyl.com - The AI Copilot for ICs, Managers, and AEs.