The term software teams use for a risk nobody likes to name

Programmers have a grim little phrase for a problem they take seriously: the bus factor. It's the number of people who would have to be hit by a bus before a project stalls out completely — before the code can't be deployed, the server can't be restarted, and no one left standing knows why a particular decision was made the way it was. A healthy team spreads that risk around. A bus factor of five is comfortable. A bus factor of two is worth a meeting.

For most solo founders, the bus factor is one.

That isn't a moral failing. It's the natural state of a business built by a single person who has held every role, made every call, and carried the whole operation forward on the strength of knowing things no one ever wrote down. The trouble is that a bus factor of one isn't only a risk in the catastrophic sense. It's a quiet, daily fragility — and the thing it threatens most is not your passwords. It's everything the passwords don't unlock.

Why a password binder isn't the same as a plan

When founders finally sit down to think about handoff, the instinct is to gather credentials. Logins, recovery codes, the bank, the domain registrar, the payment processor. This is genuinely useful work, and it solves a real problem. But it solves the easy problem.

Knowledge comes in two kinds, and the distinction matters enormously here. Explicit knowledge is anything that can be written down and transferred cleanly: a password, an account number, a phone number for the accountant. It travels well. You can hand it to a stranger and they can use it.

Tacit knowledge is the other kind — and it's the part that actually runs your business.

What philosophers mean by "tacit knowledge"

The philosopher Michael Polanyi gave this idea its sharpest formulation in his 1966 book The Tacit Dimension, with a line that has been quoted ever since: "We know more than we can tell."

His favorite examples were physical. You know how to ride a bicycle, but you almost certainly can't explain the actual rule you're following to stay upright (it involves steering into the direction of a fall, in inverse proportion to the square of your speed — and knowing that fact would not help you ride). You can recognize a friend's face in a crowd of thousands, instantly, without being able to describe what you matched on. The knowing is real, it's reliable, and it lives below the level of words.

Your business is full of this. You know which vendor will quietly extend a deadline if you call instead of email. You know that one client's invoices have to be formatted a particular way or they bounce around accounts payable for a month. You know the real reason you switched fulfillment providers two years ago, which is different from the reason on record. You know which "urgent" requests can wait and which quiet ones cannot. None of this is in a document. Most of it has never been said out loud, because you've never had anyone to say it to.

That is what a bus factor of one really measures: not the accounts, but the judgment.

The move that matters: externalization

The management researchers Ikujiro Nonaka and Hirotaka Takeuchi spent years studying how knowledge actually moves through organizations, and in The Knowledge-Creating Company (1995) they mapped the conversions it goes through. One of those conversions is the whole game for a solo founder. They call it externalization: the deliberate act of turning tacit knowledge into explicit knowledge — putting the unspoken into words, models, and stories so that it can survive outside the head that holds it.

Externalization is hard precisely because the knowledge is tacit. You can't dump it the way you'd export a spreadsheet. It comes out sideways, through metaphor, narrative, and example. Nonaka noted that this is why it so often surfaces through explaining — the act of teaching forces you to articulate things you didn't know you knew. The implication for a one-person company is uncomfortable but clarifying: if you wait until you have a successor to explain things to, you've already missed the window. You have to externalize to no one — to the page, in advance.

How to actually get it out of your head

The good news is that externalization responds to a few concrete habits, none of which require a free month.

Capture the why, not just the what. A list of your vendors is explicit knowledge anyone could reconstruct from your bank statements. The note that says "we use this freight company because the cheaper one damaged a pallet and refused the claim — never go back" is tacit knowledge made explicit. The why is the part that disappears with you. Write decisions down at the moment you make them, in a running log, and you'll capture reasoning you'd never remember to reconstruct later.

Narrate, don't outline. Tacit knowledge resists bullet points. It comes out more honestly as a story or a walkthrough. Recording yourself talking through a routine task — screen-sharing while you actually do it, thinking out loud — captures the small judgments ("I always check this first because it's usually the problem") that a tidy step-list silently drops.

Name the relationships, not just the contacts. A phone number is explicit. "This is Maria; she's saved us twice; talk to her directly, not the support line" is the tacit map of who actually keeps your business running. Those human threads are invisible in any account export and impossible for a successor to rebuild from scratch.

Write down what only you would think to worry about. The renewal that auto-charges in January. The one piece of infrastructure that looks redundant but isn't. The thing that has never gone wrong only because you quietly prevent it every quarter. This is the purest tacit knowledge there is — risks that exist entirely as a vigilance in your own head.

You're not documenting a business. You're raising the bus factor.

It helps to reframe the whole exercise. You are not trying to produce a perfect operations manual; perfectionism is what stalls these projects for years. You are trying to move your bus factor from one to two. Every piece of tacit knowledge you externalize is one more thing that survives you — one more decision a successor can make correctly without you in the room.

Measured that way, the work is never wasted and never has to be finished in one sitting. A single afternoon spent writing down the five things you'd panic about if you were unreachable for a month does more for your business's resilience than a polished binder of passwords ever could. The passwords get someone in the door. The tacit knowledge tells them what to do once they're inside.

Where this fits

This is the harder half of estate planning for a one-person company, and it's the half most tools ignore — they're built to store the explicit and silent on the tacit. Heirloom was made for the whole picture: a single place to keep the vault and the context, the credentials and the why behind them, the beneficiaries and the decisions only you would have known to flag. It's the death-binder built for solo founders, where the account list and the knowledge that makes the accounts mean something live side by side.

If your business currently has a bus factor of one, the most valuable thing you can do this week is move it to two — and write down the part that lives only in your head. You can start that map at heirloom.lumenlabs.works, whenever you're ready to make sure you're not the only one who knows how any of it works.