Every team has one. The person who knows how the billing job really works, or why the config has that strange flag, or what the client actually agreed to. When they are around, everything is fine. That is exactly the problem.
Engineers have a blunt name for it: the bus factor. How many people would have to be hit by a bus before the work stops. When the answer is one, you are running a risk that rarely shows up on any plan.
Why one is a dangerous number
A bus factor of one does not feel risky day to day. The one person is present, helpful, quick to answer. The system works. But it works because a single human is holding a piece of it in their head, and heads take vacations, get sick, change jobs, and log off at night.
The risk is not that the person is unreliable. It is that they are the only copy. A single point of failure made of a person looks like a strength right up until the moment it is not there.
The risk nobody names
Here is the part teams skip. The danger is not only the dramatic version, the resignation or the long illness. It is the ordinary, daily version. The one person is in a meeting, so a decision waits. They are asleep in another time zone, so a shipment slips. They are on holiday, so a whole area of work goes quiet for a week.
These small outages never get called risk. They get called waiting on the one person, or let's circle back. But added up across a year, the routine unavailability of your expert costs far more than the rare catastrophe everyone worries about. The bus almost never comes. The ordinary Tuesday always does.
Why it stays hidden
Single points of failure hide because they are efficient. The one person who knows is fast, so relying on them is the path of least resistance. Nobody writes the thing down because asking is quicker. Every shortcut is rational on its own. The risk builds anyway, one skipped handoff at a time, invisible until the person is out and the questions pile up with no one to answer them.
It also hides because the expert rarely feels like a risk. They feel like a hero. Praising the person who always has the answer is easy. Noticing that no one else can give it is harder, and less comfortable.
Lowering the number
You do not fix a bus factor of one by cloning the person. You fix it by getting what they know out of their head and into a place others can reach. Not a giant documentation effort. Just the working knowledge: what they decided, why, and where the details live. The goal is not to write everything down. It is to make sure the handful of answers only they can give are no longer trapped in one skull.
The test is simple. Pick your one person and imagine them out for two weeks. How many questions stall completely? Every one you can answer from something written down is a question that no longer depends on a single human being awake. Run the same test again next month, and the number should be lower, not higher.
Where StandIn fits
This is the gap StandIn is built for. Your one person writes a short brief at the end of the day, and while they are off, it answers from what they wrote, in their words, with a source under each answer. When something is not on record, it says so instead of guessing. It does not replace the expert. It just means the team is no longer one absence away from stuck.
When you're off, your StandIn is on.
It answers your teammates' questions from work you've already done, in your words, with a source under every answer.