the_bus_factor
misfits.kaihacks.ai
khai misfits · a staging

The Bus Factor.

Open the misfit → ← Misfits
Misfits
00 · the misfit synopsis

Synopsis.

Name

The Bus Factor. A team that hums, because whenever anyone is stuck they know exactly who to ask ... and the whole of what the team knows lives in that one person's head, with no copy anywhere, one bus away from gone.

Arc

The bend is this: every day the team gets faster, and every day it gets more fragile. It runs on two lines that rise and fall together, in opposite directions. One line is the dependence: the more the team leans on the one who knows, the faster it moves, because asking the expert always beats reading the documentation that was never written. The other line is the redundancy, and it falls as the dependence rises, because every question answered directly is a question not turned into a page anyone else could read: the fast path is the path that does not share, so each use of the knowledge deepens its home in a single head instead of spreading it. Nobody hoards. The expert is being helpful, answering is quicker than teaching, documenting is thankless and never urgent, and being the person everyone asks is rewarded. So the knowledge concentrates a little more with every interaction, the team runs a little faster and stands a little closer to the edge, until the day the one head leaves, and takes the system with it. Write it down once, where anyone can read it, and the bus has nothing to take: the concentration is the story.

Stakes

Whether the knowledge ever lives anywhere but one head. Every plot moves it the same direction: not toward the page, toward the person. The production cannot make the fast path share, because the fast path is precisely the one that does not. It can only show that no one hoarded, that every question was answered in good faith and every answer deepened the trap, and that the one move that would have saved the team, write it down where anyone can read it, was the one move that was never quick, never urgent, and never anyone's job.

Estate

khai-misfits: the house that holds this production and answers for the whole run.

01 · plots editorial

Plots.

Fast Path A critical system rests on one person's tacit knowledge. Questions route to them because it is fastest, and writing it down goes on the backlog. The Keystone answers, the Asker asks. Closes when the fast path is set and the documentation is deferred without end.

Backlog Item Cue: the team ships on the expert. Each answer deepens the concentration, the expert becomes indispensable and is rewarded for it, and the named backup is never given the time to become real. Closes when the team is fastest and most fragile, dependence at its peak and redundancy at zero.

Single Point Cue: a new hire cannot onboard from documentation that does not exist, so they learn by asking the expert, deepening it again. The risk owner sees the single point of failure and bets the expert stays, because they are here and delivering. Closes when the risk is on the register, accepted, and growing.

Empty Desk Cue: the one head leaves, by bus or notice or burnout, and the knowledge leaves with it. The successor digs through the undocumented system to rebuild a partial, wrong copy. Closes when the bus factor is named ... or the next single point is already forming.

02 · plot editorial

Backlog Item.

Cue

The sprint, where delivery is the measure and the clock is always running. The team ships on the expert, fast, and on the backlog the ticket to write it all down sinks a little lower each planning.

Tension

Every call is the right call this sprint. Shipping beats documenting when there is a deadline, and there is always a deadline, and the backup is always needed on delivery too. But the sum of every reasonable this-sprint is a team at its fastest and its most fragile, the expert now the only one who can, the backup real only on paper, and the redundancy quietly at zero.

03 · plot editorial

Empty Desk.

Cue

The empty desk, the Monday after the one head is gone. A notice worked, or a better offer, or a burnout, or the bus itself: the chair is empty, and everything it held is not there.

Stage

The Excavator tables Dig It Out: reconstruct the knowledge from the code and the scraps, and the concentration is read at last, all of it that ran into one head and none that ran out. The bus has taken what it always could: a partial, wrong copy is rebuilt at a cost that dwarfs the writing-down never done.

Tension

Nobody hoarded, and nobody was unlucky. Every fast answer was generous, every deferral was reasonable, every accepted risk was sound arithmetic. The reckoning is not a betrayal or an accident, it is the fast path arriving where it always led: the knowledge was used constantly and copied never, so the day its one holder left, it left. Write it down once would have cost a week ... or the desk is refilled, the new expert starts answering, and the next single point begins to form.

04 · plot editorial

Fast Path.

Cue

The keyboard, where the system was built and is best understood. A critical thing rests on one person's unwritten know-how. Through the queue the questions are already starting to arrive, because everyone knows exactly who to ask.

Tension

Nobody is hoarding. Answering directly is generous and quick, asking the person who knows is sensible, and writing it all down first would be absurdly slow. But the quick way is the way that leaves no copy, so the very helpfulness of the exchange is what keeps the knowledge in one head, and the fast path is set before anyone notices it is also the path that does not share.

05 · plot editorial

Single Point.

Cue

The onboarding, a new hire at a fresh desk with nothing to read. The documentation that would bring them up to speed does not exist, so the one way in is to ask the expert, and the risk of that is plainly on the register.

Tension

The arithmetic is sound every time. A newcomer must learn from someone, and the someone is the expert, and paying real hours now to prevent a possible loss later never wins against this quarter's delivery. So the risk is seen, rated, and rationally accepted, mitigated on paper and never in fact, and the single point of failure sits on the register, acknowledged, growing, one sane deferral at a time.

07 · pitch editorial

The Go-To.

Tenor

Fast, capable, unblocked. Whenever anyone is stuck, they know exactly who to ask, and the answer comes back in minutes. The voice of a team that never waits long, spoken by people who each, sensibly, ask the one who already knows.

Undertow

Under the speed, a single copy. Each quick answer solves the problem and skips the writing down, so the knowledge deepens in one head and spreads to none. The team never slows: it only leans a little harder on the one person, and stands a little nearer the day they are gone.

Nerve

The feeling of a team that always knows who to ask, moving fast because it never has to look anything up, resting its whole weight on a chair that could be empty on Monday.

Echo

After the run: a system no one left can explain, a wiki page that was always next sprint, and a week when the fastest team in the building could not answer its own questions.

09 · persona editorial

The Asker.

Projection

Pragmatic. Unblocked. Gets on with it. No time lost hunting through pages that do not exist. One message, one answer, back to work.

Action

Sends every question straight to the expert. It is the route that works, so it is the route taken. Fast in, fast out, moving again.

Shadow

Taking the quick answer is sensible, and it leaves no copy. Each ask deepens the dependence it relies on... a good team member doing the efficient thing, again, onto the single point. Nothing malicious, just the shortest line between blocked and shipping.

Tell

Says "I'll just ask them, they'll know," and they do. And no one else learns it.

10 · persona editorial

The Bettor.

Projection

Prudent. Numerate. Manages the register line by line. Sees the single point of failure clearly, names it, logs it. Nothing hidden, everything counted.

Action

Reads the single point of failure, names a paper backup. Weighs the cost of fixing now against the odds of failing later. Accepts the risk, one more quarter.

Shadow

The arithmetic is genuinely sound: a certain cost now against a possible cost later. So the rational owner waits, and rational waiting is how a seen risk is carried... growing, quarter by quarter, until the quarter it is too late. No recklessness here, only a wager that pays out until it does not.

Tell

Says "it's on the register, we're managing it." And managing means watching it grow.

11 · persona editorial

The Excavator.

Projection

Plain. Arrived after the one who knew was gone. No handover waiting, no page to open. Just a running system and a shovel.

Action

Digs through the undocumented system, layer by layer. Rebuilds what was only ever spoken, from traces and guesses. Reconstructs the map by walking the ground.

Shadow

Not a hero, just the one who came next. It rebuilds a partial, wrong copy at a cost that dwarfs the writing-down never done... and proves by the labour that one page would have saved it. This is the reckoning arriving as excavation, where foresight would have cost almost nothing.

Tell

Says "there's nothing written down anywhere." And there is not.

12 · persona editorial

The Keystone.

Projection

Capable. Generous. Always there when you need it. Ask anything, any hour, and the answer comes back clean. Nothing waits on a queue when it is the queue.

Action

Answers every question directly, on the spot. Teaching is slower than telling, so it tells. The help is real, and it is gladly given.

Shadow

The generosity is the fast path, and the fast path is the trap. Every quick answer keeps the knowledge in one head... the more it gives, the more it is the only place to ask. It could not write it all down in a year, and it is never given a week.

Tell

Says "just ask me, it's quicker," and it always is. And nothing is ever written.

13 · persona editorial

The Leaner.

Projection

Focused. Delivery-driven. Hits the dates. The board moves, sprint over sprint, clean. Whatever ships this week, ships this week.

Action

Pulls delivery every sprint, and lets the documentation wait. There is work that ships and work that does not, and shipping wins. The docs card slides to the next column, always.

Shadow

Shipping beats documenting when there is a deadline, and there is always a deadline. So the reasonable this-sprint choice gets made forever... the one task that would break the trap deferred, sprint after sprint, by a manager doing exactly the job. No villain here, only a backlog that never surfaces the thing that matters most.

Tell

Says "docs next sprint, we need to ship," and ships. Next sprint, says it again.

14 · persona editorial

The Newcomer.

Projection

Keen. Ready to learn. Looking for something to read. First week, open to everything, notebook out. Wants the map before the territory.

Action

Finds nothing to read, and learns the only way open. Asks the expert, because the expert is the documentation. Onboards by conversation, one question at a time.

Shadow

Onboarding by asking is the sole route, and it deepens the concentration that left nothing to read. A new person, blameless, adding again to the one head... because the org gave them no other door. The newest arrival becomes the newest dependency, before they even choose to.

Tell

Says "where are the docs?" and is pointed at a person. Not a page.

15 · persona editorial

The Understudy.

Projection

Willing. Named on the chart as the backup. Present in the plan, the box that says: covered. Ready, on paper.

Action

Stands as the backup, where the org chart says to stand. Never given the hours to actually learn the thing. The label holds; the knowledge does not.

Shadow

This seat could be real redundancy, and it knows the redundancy is fiction. The time to shadow always loses to delivery, so it stays a label on an empty box... and it cannot fix that from where it sits. Sensible people filled the box, and the box is still empty.

Tell

Says "I'm the backup, but honestly I couldn't run it." And no one hears the second half.

17 · place editorial

The Backlog.

Shown

The list of good intentions. The ticket titled "write the runbook," aging quietly.

Holds

The doc ticket, endorsed and unpulled. Every nod it got, none of the doing.

Offers

The look of a plan to fix it. A line item that answers the audit.

Withheld

The sprint it would need to actually happen. The priority that would pull it above the next fire.

18 · place editorial

The Empty Desk.

Shown

The Monday after the one head left. A monitor dark, a login no one holds.

Holds

An undocumented system and a shovel. A live service and no one who wrote it.

Offers

A partial copy, rebuilt at cost. Weeks of reading logs to guess intent.

Withheld

Everything that was only ever spoken. The reasons behind the code, gone with the voice.

19 · place editorial

The Keyboard.

Shown

Where the system was built and is best understood. The keys worn smooth by the one who typed them all.

Holds

The tacit knowledge, in hands and habits. The map that lives behind the eyes, never drawn.

Offers

A system that runs, in one person's care. Speed no committee could match.

Withheld

Any copy of the unwritten half. The half that leaves when the chair does.

20 · place editorial

The Onboarding.

Shown

A new hire at a fresh desk. A welcome, a laptop, a list of names to ask.

Holds

The single point of failure, plainly visible. Every road on the map running through one office.

Offers

A way in, by asking. An expert who will answer, once more.

Withheld

A page to read instead of a person to deplete. The written system that would let the newcomer walk alone.

21 · place editorial

The Queue.

Shown

The stream of questions to the expert. Every thread ending at the same name.

Holds

The fast path, an answer in minutes. A backlog of interruptions worn as proof of worth.

Offers

Quick unblocking. The team moves, because one head does not sleep.

Withheld

A trail anyone else could follow. The answer spoken, then gone from the air.

22 · place editorial

The Sprint.

Shown

Delivery measured against the clock. Points burned down, velocity climbing.

Holds

The deferral, docs below every ship. The backup untrained, one more cycle out.

Offers

Dates hit. A board of green, a demo that lands.

Withheld

The hours to write it down or to train the backup. The slack that would spread the load.

24 · piece editorial

The Backlog Item.

Place

On the backlog, near the bottom, its priority a permanent someday. The ticket everyone approves of and no one pulls: document the system, write the runbook, capture the tribal knowledge, always this quarter's intention and last quarter's too.

Load bearing

Without it the not-writing would be a visible choice and someone might make the other one. With it the not-writing is disguised as a plan: the Backlog Item is how an organisation agrees the knowledge should be shared and ensures it never is, because a task that everyone endorses and nothing prioritises is a task that lives forever in the state of about-to-happen. It never loses the argument, it simply never wins the sprint, and there is always a fire that outranks it, so the copy that would have saved the team is perpetually one iteration away.

Apparent

A plan to fix it. It looks like the problem is handled: it is on the board, it is acknowledged, it will get done. Being on the board reads as progress. It is the opposite: it is the alibi that lets the fast path continue guilt-free, because the sharing is, officially, coming.

Yearbook

Endorsed by everyone, pulled by no one, deprioritised each sprint by the leaner. It is the deferral made visible: the one act that would break the concentration, written down and ranked below every delivery, so the knowledge stays in the head and the plan to free it stays on the list, and both are still there on the day the head walks out.

25 · piece editorial

The Bus.

Place

The gap between what the team runs on and what it can survive losing. On one side, a system operating perfectly, fast and unblocked. On the other, a single chair, and everything the system needs to keep working sitting inside the person in it. The Bus is the standing distance between the two, and the certainty that one day it closes.

Load bearing

Without it the play is a run of sensible fast answers and one unlucky resignation. With it those are one object: a team whose whole knowledge lived in a single uncopied head, held whole by nobody once that head is gone, because the seat that carried the tacit half was the only seat that had it, and no page, no backup, no second knower was ever actually made. It does not require a bus. A notice, a better offer, a burnout, a retirement: any exit empties the chair, and the knowledge does not resign, it simply is not there the next morning, and was never anywhere else.

Apparent

An ordinary departure. From the outside one person left a job, which happens constantly and recovers. The trap is invisible until the moment it is total: nothing looks fragile while the expert is answering, and everything is unmaintainable the day they are not.

Yearbook

The team built it in good faith: the fast path taken, the backlog item deferred, the indispensable rewarded, the paper backup never made real. The excavator was the first to sit at the empty desk and try to read a system that was only ever spoken, and rebuilt a partial, wrong copy at a cost that dwarfed the writing-down never done. Nobody had a name for the risk while it was answering every question ... until the morning it could not.

26 · piece editorial

The Concentration.

Place

Across every interaction, in one direction. Each answer given, each fire fought, each fix applied by the one who knows, all of it deepening the knowledge in the same single head instead of spreading it.

Load bearing

Without it the play is one clever person and a bit of key-person risk. With it it is a current: the Concentration is why the two lines diverge rather than drift, because the very act of using the knowledge, taking the fast path, is what deepens it, so reliance does not merely coexist with fragility, it manufactures it. Every question routed to the expert makes the expert a little more the only one, so the team's growing skill at getting answers is the same motion as its growing inability to survive without the answerer. It runs one way, because a direct answer adds to the head and subtracts from no one, and there is no interaction that spreads the knowledge as a by-product the way asking concentrates it.

Apparent

A team getting better. It looks like expertise deepening, a go-to person becoming ever more capable, the team ever quicker. All true. The same graph, read the other way, is the redundancy going to zero.

Yearbook

Driven by every ask, and reversed by nothing, until the empty desk. It runs the dependence up while the redundancy falls, the fast path feeding the tacit knowledge back into the one head it came from, the two lines drawing apart the whole way, until the distance between what the team relies on and what it could survive losing is the whole system.

27 · piece editorial

The Fast Path.

Place

Through the queue, a message to the expert and an answer in minutes. The route every stuck person takes because it works: not the search, not the doc, not the dig, just ask the head that holds it and be unblocked.

Load bearing

Without it the team would be forced to the slow ways that leave a trail: the write-up, the shared debugging, the doc that outlives the moment. With it the team takes the quick way every time, and the quick way is the trap, because the Fast Path resolves the problem and distributes nothing: a direct answer is a transfer from one head to one head, gone when the second forgets, while the slow ways would have made a copy anyone could read. It is not that the team chooses concentration over sharing. It chooses fast over slow, and fast happens to be the one that does not share.

Apparent

Efficiency. It looks like a well-oiled team removing blockers quickly, exactly what a good team does. Speed is a virtue. This speed is bought by never leaving anything behind.

Yearbook

Taken by the asker, and offered gladly by the one asked. It is the engine of the concentration: every trip down the Fast Path is a lesson given and not recorded, so the knowledge is used constantly and copied never, and the more the team relies on it the deeper it sinks into the single head it came from.

28 · piece editorial

The Indispensable.

Place

Wherever the org shows it values the expert: the raise, the retention call, the please do not leave. The standing the Keystone earns precisely by being the single point, valued in exact proportion to how much would break without them.

Load bearing

Without it the expert has every reason to share the load and lighten it. With it the expert has a quiet reason not to, because the Indispensable is the incentive pointing the wrong way: an organisation rewards the person it cannot lose, so being irreplaceable pays, and the surest route to irreplaceable is to remain the only one who knows. It need not be cynical. The expert may long to offload it and still feel, correctly, that their standing rests on being the one asked, so the system that would most help the team is the system that would most reduce the expert, and no one has to choose that reduction on purpose for it never to happen.

Apparent

Recognition of value. It looks like an organisation rightly prizing its best people, keeping its stars happy. Valuing expertise is good. Valuing it as a single point, and paying most for what is least shared, quietly funds the fragility.

Yearbook

Conferred on the keystone, and felt by the understudy as a door that will not open. It is the incentive twin of the fast path: one makes not-sharing quick, the other makes it pay, so the concentration is pushed by convenience and pulled by reward, and the expert stays the only shelf in the library because both the day and the ladder ask them to.

29 · piece editorial

The Paper Backup.

Place

On the org chart and the risk register, a second name beside the system. The nominated backup, the also-familiar, the in-case: a redundancy that exists in the box and nowhere in anyone's actual knowledge.

Load bearing

Without it the single point is nakedly single and someone might act on the alarm. With it the alarm is silenced without being answered, because the Paper Backup lets the organisation believe it is covered while it is not: a name is written where a second knower should be, and the writing is mistaken for the knowing. The backup was never given the hours to shadow, the tickets to struggle through, the failures that make expertise, because those hours always lost to delivery, so the redundancy is a label on an empty box, and it does its worst work by making the risk look handled.

Apparent

Coverage. It looks like the responsible thing, a bus-factor mitigation in place, a second pair of hands ready. Naming a backup sounds like having one. The gap between the name and the knowledge is the whole exposure, hidden behind a filled-in cell.

Yearbook

Worn by the understudy, who is the backup on paper and knows they could not actually take the wheel. It is the fiction that makes the single point of failure survivable to look at: with a backup named, the risk owner can accept the risk, so the label that was meant to reduce the exposure is what lets everyone stop worrying about it.

30 · piece editorial

The Single Point of Failure.

Place

On the onboarding and the risk register both, where the dependence is plainly visible and calmly accepted. The known fact that if this one person is unavailable, the system cannot be changed, fixed, or explained by anyone else.

Load bearing

Without it the concentration is a habit and not yet a hazard. With it the habit has a name and a place on a list, and is accepted anyway, because the Single Point of Failure is a risk everyone can see and no one is moved to pay to remove: mitigating it costs real time now, the failure it guards against is only possible and only later, and the expert is here today and delivering. So it is logged, rated, given a paper backup, and left, a known exposure carried in the open, growing, because the cost of closing it is certain and the cost of leaving it is merely probable.

Apparent

A managed risk. It looks handled: identified, assessed, on the register with an owner and a mitigation. Being on the register reads as being controlled. It is being watched, which is not the same, and what is watched here only ever gets larger.

Yearbook

Accepted by the bettor, who weighs a certain cost against a possible one and rationally waits. It is the risk that the empty desk collects: seen for years, mitigated on paper, never actually reduced, because every quarter the same sane arithmetic says not yet, until the quarter it says too late.

31 · piece editorial

The Tacit Knowledge.

Place

At the keyboard, in the hands and the habits of the one who built it. The why behind the config, the gotcha that is not in any comment, the reason it is done this odd way and must be: the working knowledge that never made it to a page.

Load bearing

Without it the system could be run from a manual and anyone could hold it. With it the system can be run only by the person who carries the unwritten half, because the Tacit Knowledge is the part of knowing that does not survive being written: we know more than we can tell, and what cannot be told stays where it was learned, in one head. It is not withheld, it is simply not extractable at the speed anyone has, so it accretes in the builder as a by-product of building, and every fix adds a little more that only they now hold.

Apparent

Expertise. It looks like deep skill, hard-won mastery, the mark of someone who really understands the system. It is all of that. It is also a single uncopied volume, and the library has one shelf.

Yearbook

Carried by the keystone, who could not write it all down in a year and is never given a week. It is the root of the play: the fast path forms because asking this head is the only way to reach what only this head holds, and so the knowledge that resists writing is the knowledge that most needs it, and least gets it.

33 · position editorial

Delivery Manager.

Has

The deadlines, dated and public. The sprint, planned around who can move fastest.

Orders

Ship. Route the hard work to the one who knows: it lands soonest there. Fill the board and burn it down.

Loses

The documentation, deferred every planning. Writing it down is always slower this sprint than asking, so it never wins the slot. The velocity that ships is the velocity that hides the risk.

Drives

Toward delivery, sprint over sprint. On the back of the one who knows. Each on-time ship makes the next one lean harder on the same head.

34 · position editorial

Keeper.

Has

The whole system, load-bearing and live. And the unwritten half of it, the part that lives nowhere but here.

Orders

Keep it running. Help whoever asks, fast, because asking beats the page that was never written. Say yes to the next question.

Loses

The time to ever write it down, spent answering. Every direct answer is a page not made: the knowledge deepens its home in one head. Redundancy falls exactly as reliance rises.

Drives

Toward a working system and a helped team. By staying the only one who can. Each help renews the trap it means to relieve.

35 · position editorial

New Hire.

Has

Fresh energy, and every question still allowed. No way in but asking, because there is no page to read.

Orders

Get up to speed. Learn the system, meet the people, start contributing. Find the answers wherever they live.

Loses

The self-serve route, because nothing is written. Ramp-up runs entirely through the one who knows, one interruption at a time. The only door open is the door that does not scale.

Drives

Toward learning, the one path left. Which routes another stream of questions into the single head. Getting up to speed deepens the very trap that slowed it.

36 · position editorial

Nominal Backup.

Has

The title of second, on the org chart, in the plan. And none of the knowledge, because none of it was ever handed over.

Orders

Be the backup. Be ready to step in the day the one who knows is gone. Stand behind the seat you cannot yet fill.

Loses

The hours to become one, always to delivery. Shadowing loses to shipping in every planning: the backup is real only on paper. The seat that could be redundancy is never resourced to be.

Drives

Toward real redundancy, wanted by all and funded by none. From a seat never given the time to build it. The title stays; the coverage never arrives.

37 · position editorial

Risk Owner.

Has

The register, with the concentration logged on it in red. The choice to spend now or wait, quarter after quarter.

Orders

Manage the risk. Weigh the cost of acting against the odds of the day it lands. Keep the register current and let the numbers decide.

Loses

Nothing this quarter, which is why the risk is never closed. The bet pays every quarter it does not fail, so waiting always looks cheapest. The loss is deferred until it arrives all at once.

Drives

Toward a sound bet, that the expert stays. Renewed each quarter it holds, until the quarter it does not. Every renewal makes the eventual loss larger.

38 · position editorial

Successor.

Has

An empty desk, where the one who knew used to sit. An undocumented system, running, that no one can now explain.

Orders

Keep it alive. Learn it from the outside, by reading the code that has no notes. Rebuild what left with the person.

Loses

Nothing it was given: it inherited a gap. The knowledge was never written, so nothing was there to hand down. The bill for years of unwritten answers comes due here, all at once.

Drives

Toward rebuilding the knowledge from scratch. At a cost the writing-down would have spared many times over. The fast path arrives, at last, as the slowest one.

39 · position editorial

Team Member.

Has

A blocker, right now, on the critical path. And a person to ask, who always knows.

Orders

Get unblocked. Keep moving. Take the quick answer: it is right there, and the page is not.

Loses

The chance to learn it durably, traded for the quick answer. The answer clears the blocker and leaves no trace anyone else could read. The path that unblocks is the path that does not share.

Drives

Toward flow, ticket after ticket. Down the fast route, the one that never spreads. Every clean unblock feeds the single head.

41 · process editorial

Deferral.

Initiated by

A deadline against a doc ticket. A ship date that will not move.

Direction

Writing pushed to next sprint. The capture slides right, again and again.

Lever

Delivery against capture, always a fire first. Something urgent burns, the page can wait.

Echo

The sharing task perpetually about to happen. A promise renewed each planning, never kept.

42 · process editorial

Departure.

Initiated by

A notice, an offer, a burnout, a bus. Any reason a chair goes empty.

Direction

The one head out the door. The knowledge walking with the person.

Lever

Any exit against no copy, the chair empties and the knowledge with it. No backup means the loss is total.

Echo

A system no one left can explain. A machine still running, its logic now a rumor.

43 · process editorial

Excavation.

Initiated by

An empty desk and a live system. A team told to keep it running blind.

Direction

Knowledge dug from code and scraps. Meaning reconstructed from commits and old chat.

Lever

Reconstruction against the gap, rebuild what was spoken. Every guess a slow dig through what was never written.

Echo

A partial, wrong copy at a cost the writing-down would have spared. Months spent recovering an hour never taken.

44 · process editorial

Indispensability.

Initiated by

An expert asked for everything. The one name on every escalation.

Direction

Value concentrating on the single source. Worth measured by how badly they are needed.

Lever

Reward against sharing, paid to be irreplaceable. Raises follow the ones who cannot be spared.

Echo

An incentive pointing away from the page. Why write it down when the not-writing pays.

45 · process editorial

Reliance.

Initiated by

A team that always knows who to ask. A habit of leaning, never learning.

Direction

Weight onto the one who knows. Load gathering on a single back.

Lever

Convenience against redundancy, lean and do not spread. Easier to ask than to own it.

Echo

A team faster and nearer the edge. Quick today, fragile the moment that back is gone.

46 · process editorial

Routing.

Initiated by

A blocker and a known expert. A stuck engineer who knows exactly whom to ping.

Direction

The question to the one head. Every path bending toward the same desk.

Lever

Speed against sharing, ask beats read. The fast answer wins, the slow page waits.

Echo

A lesson given and never recorded. Solved again, from scratch, next week.

48 · plan editorial

Ask the Expert.

Direction

Take the quick route to the one who knows. Blocked now, unblocked now. The shortest path runs through the same person every time.

Orders

(The Asker joins the line and puts the question to the keeper.)

Implementation

(The Queue; the Routing process; a clause of friction: the fast answer never leaves a trace.)

Targets

  • [ ] the blocker is cleared
  • [ ] by the fastest path
  • [ ] no copy is left behind
  • [ ] the dependence deepens by one more ask

49 · plan editorial

Bet They Stay.

Direction

Accept the key-person risk for another quarter. The exposure is real, the fix is expensive, and the bet is that nobody leaves yet.

Orders

(The Bettor logs the single point of failure, names a paper backup, and defers the mitigation.)

Implementation

(The Backlog; the Reliance process; a clause of friction: a certain cost now always loses to a risk that has not landed yet.)

Targets

  • [ ] the single point is logged
  • [ ] a paper backup is named
  • [ ] the certain cost is deferred
  • [ ] a seen risk is carried, growing, until too late

50 · plan editorial

Cover on Paper.

Direction

Stand as the named second. The chart says covered. The hours to actually learn it never come.

Orders

(The Understudy accepts the label, asks for shadowing time, and is told next quarter.)

Implementation

(The Sprint; the Indispensability process; a clause of friction: a name on the chart costs nothing, the shadowing costs sprint capacity no one will spend.)

Targets

  • [ ] a backup is named on the chart
  • [ ] never given the hours to shadow
  • [ ] the redundancy is a label
  • [ ] the risk looks handled and is not

51 · plan editorial

Dig It Out.

Direction

Reconstruct the knowledge from scraps. The head is gone, the desk is empty, and the system must be read back out of the code.

Orders

(The Excavator reads commits, chases fragments, and rebuilds the map that was never written.)

Implementation

(The Empty Desk; the Excavation process; a clause of friction: every answer must be inferred, and some inferences are wrong.)

Targets

  • [ ] the empty desk is inherited
  • [ ] the system is excavated from code and fragments
  • [ ] a partial, wrong copy is rebuilt
  • [ ] at a cost that dwarfs the writing-down never done

52 · plan editorial

Just Ask Me.

Direction

Resolve every question directly. Fast. The answer lives in one head, so route it through the mouth, not the page.

Orders

(The Keystone answers on sight. No ticket, no write-up, just the reply.)

Implementation

(The Keyboard; the Routing process; a clause of friction: writing it down is always slower than saying it.)

Targets

  • [ ] the question is answered in person
  • [ ] faster than any doc could be
  • [ ] the tacit knowledge stays where it was learned
  • [ ] helping quickly keeps it in one head

53 · plan editorial

Onboard by Asking.

Direction

Learn the only way open. The wiki is empty, the readme is stale, so the questions go to the person who holds it all.

Orders

(The Newcomer searches for docs, finds none, and turns to the expert instead.)

Implementation

(The Onboarding; the Reliance process; a clause of friction: asking works, so nothing pushes anyone to write.)

Targets

  • [ ] no docs are found
  • [ ] the expert is asked instead
  • [ ] the newcomer gets up to speed
  • [ ] each question adds again to the one head

54 · plan editorial

Ship It.

Direction

Hit delivery. Defer the writing. The date is real, the doc is not, and only one of them slips.

Orders

(The Leaner closes the sprint and pushes the documentation ticket to the next one.)

Implementation

(The Sprint; the Deferral process; a clause of friction: there is always a nearer deadline than the one to write things down.)

Targets

  • [ ] the sprint ships
  • [ ] the doc ticket sinks
  • [ ] there is always a deadline
  • [ ] the one task that would share is deferred without end

55 · reference warrant

Line Of Work.

Staging the bus factor as a systemic system: a team that runs faster the more it leans on one person's knowledge, and more fragile by the same motion, because the fast way to use the knowledge is the way that does not share it. The play models the documented mechanics, tacit knowledge that resists being written down, the concentration of a project's understanding into one or two heads, the under-provision of documentation as thankless and never urgent, and the key-person risk accepted because it is certain to cost now and only possible to cost later, as the load-bearing vectors of the structure, not as a tale of a hoarder. The governing finding of the source literature is the play's governing law: knowledge routes to whoever already holds it, because that is fastest, so each use deepens its concentration instead of distributing it, and dependence and fragility rise together, one direction, until the holder is gone.

56 · reference warrant

Origin.

The phenomenon in practice, and the research spine beneath it.

Source Key Work / Event Scope
Polanyi "The Tacit Dimension" (1966) Tacit knowledge: "we know more than we can tell", so a large part of expertise resists being written down and stays in the person who holds it. The Tacit Knowledge.
Nonaka & Takeuchi "The Knowledge-Creating Company" (1995) Tacit versus explicit knowledge and the cost of converting one to the other: why capturing what an expert knows is slow, effortful, and easily deferred.
Brooks "The Mythical Man-Month" (1975) Conceptual integrity held in a few minds, and the failure of knowledge to transfer by adding people: understanding does not copy the way headcount does.
Davenport & Prusak "Working Knowledge: How Organizations Manage What They Know" (1998) Internal knowledge markets and why sharing is under-provided: documenting is unrewarded, being the source is valued, and "knowledge is power". The Indispensable.
Avelino, Hora & Valente "A Novel Approach for Estimating Truck Factors", ICPC (2016); Cosentino et al., "Assessing the Bus Factor of Git Repositories", SANER (2015) Empirical measurement of the truck / bus factor: most projects concentrate their knowledge in one or two contributors. The Concentration, measured.
Practitioner "bus factor" / "truck factor"; key-person risk in risk management The naming: how many people would have to be hit by a bus before the work cannot continue, and the register on which that risk is logged and accepted.
57 · reference warrant

Restrictions.

What the house refuses to model, and how it credits what it stages.

  • No villains: the elements are reduced to load-bearing vectors. The play refuses to cast the expert as a hoarder, because the source finding is precisely that no one need hoard: answering directly is generous and fast, documenting is thankless and never urgent, and leaning on the one who knows is what a sensible team does. The misfit is that the helpful, fast move is the one that does not share.
  • No hero: the play refuses to resolve the misfit into foresight closing the risk in time. The reckoning is the departure and a successor excavating an undocumented system, because writing it down was never quick, never urgent, and never anyone's job, not a conscientious act arriving to prevent the loss.
  • Credit, not claim: the research above is other people's work, packaged and attributed here, never claimed as the house's. The staging is the house's; the findings are theirs.
58 · reference warrant

Encoding.

Source to constraint, per element.

  • The Tacit Knowledge: carries tacit knowledge (Polanyi; Nonaka & Takeuchi), the know-how that resists codification and stays in the head that learned it.
  • The Fast Path: carries the routing to the fastest resolver, the direct answer that resolves the problem and distributes nothing.
  • The Backlog Item: carries the under-provision of documentation, the capture endorsed by all and prioritised by none.
  • The Indispensable: carries the knowledge market (Davenport & Prusak), the reward for being the single source that points against sharing.
  • The Paper Backup: carries the fictional redundancy, a key-person-risk mitigation that exists as a name and not as knowledge.
  • The Single Point of Failure: carries key-person risk, the exposure seen, logged, and accepted because it costs now and only possibly later.
  • The Concentration: carries the truck-factor dynamic (Avelino et al.; Cosentino et al.), a project's understanding sinking into one or two heads, deepened by every use.
  • The Bus: carries the phenomenon whole (Brooks; the bus-factor folklore), the day the one head leaves and the system with it, held whole by nobody after.

updated: 2026-07-01

59 · download artifact

Download Misfit.

Download the_bus_factor.zip
size
65.8 kB
sha256
71189997895e24de21e7f7bf57d748322e3a9ac041f449665cfdf82bfbf70f21

Includes the misfit configuration and all staged elements.

Enter the Stage