World Model Readiness What leaves when one person does

Module · What leaves when one person does

The Team Knowledge Resilience Check

Every team has a person whose absence would hurt more than the org chart suggests: the one who knows why the workaround exists, which client cannot be pushed, how the fragile process actually holds together. That knowledge is invisible until it walks out the door. AI can help capture and surface it, but only if it was ever written down. This module checks the five things that decide whether your team survives a departure intact: whether you know your bus factor, whether you document judgment and not just steps, how long onboarding really takes, how many single points of failure you carry, and whether capturing knowledge is a habit or an afterthought.

Question 1 of 5 · Bus factor is known

Do you know which one person leaving would hurt your team most?

Bus factor is the number of people who would have to vanish before your team seizes up, and for most teams it is uncomfortably close to one. Knowing who that person is, and for which knowledge, is the first step. Not knowing means you will find out the hard way, on their last day.

Question 2 of 5 · Judgment is documented

Does your documentation capture judgment, or just the steps?

Most documentation records what to do, not why or when to deviate. The steps are the easy part; the value is in the judgment: when to break the process, which exception matters, what the numbers do not show. A team that documents only procedure keeps the manual and loses the expertise.

Question 3 of 5 · Onboarding is quick

How long before a new team member can work without constant help?

Onboarding time is a direct readout of how well your knowledge is captured. If it takes six months for someone to become self-sufficient, that is six months of knowledge locked in other people's heads. Fast onboarding is not about smart hires; it is about knowledge that is written down and findable.

Question 4 of 5 · Few single holders

How much of your team's critical knowledge sits with exactly one person?

A single holder is a single point of failure: one person who alone knows the system, the relationship, the fix. Every one of them is a risk you are carrying whether you priced it or not. Spreading that knowledge, through pairing, rotation, or documentation, is how you stop betting the team on one person's attendance.

Question 5 of 5 · Capture is a habit

Is capturing knowledge a routine, or something you do when someone quits?

Knowledge capture that only happens during an exit interview is knowledge capture that has already mostly failed. When capturing what you learn is a normal part of the work, resilience compounds quietly. When it is a panic triggered by a resignation letter, you get whatever the leaving person can dump in their last two weeks.

For the statistics · one click each

Three questions for the public picture

These do not affect your score. They feed the anonymised, aggregated statistics; groups under 8 respondents are never shown.

If your most knowledgeable person left tomorrow, how badly would your team hurt?

We would be crippled
Serious disruption
Manageable
We would be fine
We do not know

How much of your team's knowledge is actually documented?

Almost none
Steps but not judgment
Judgment partly captured
Most, kept current
We are not sure

How long until a new hire works without constant help?

Several months
A few weeks
Days to a week
Days, self-serve
We have not measured

Your context

Used to calibrate the report. Company size and sector remain in the anonymized dataset; your email does not.