Distinctions
Is
| Identity (IS) | Explanation |
|---|---|
| Knowledge silo | Critical knowledge concentrated in one individual. |
| Bus factor of one | If the person disappears, the work stops. |
| Sole subject-matter expert | Only one person understands the system well enough to operate or modify it. |
| Gatekeeper of knowledge | Others must go through this person to access understanding or make decisions. |
| Fragile expertise | The organization depends on one individual’s cognition rather than shared capability. |
| Bottleneck expertise | Work queues behind the only person capable of resolving issues. |
| Tribal knowledge holder | Knowledge exists only in the person’s head rather than in artifacts or shared understanding. |
| Single maintainer dependency | A system maintained by only one capable person. |
| Operational dependency | Critical operational tasks require one specific person to perform them. |
Is Not
| Other (IS NOT) | Explanation |
|---|---|
| Subject-matter expertise | Someone can be highly knowledgeable without being the only one capable. |
| Domain leadership | Leaders may guide expertise but do not hold it exclusively. |
| Specialized roles | Specialists can exist within teams while knowledge remains shared. |
| Senior engineer / architect | Seniority does not imply exclusive knowledge ownership. |
| Mentorship | A mentor spreads knowledge rather than centralizing it. |
| Centers of excellence | Expertise concentrated in a team, not a single individual. |
| Temporary expertise gap | A momentary imbalance in knowledge that is actively being corrected. |
| Deep expertise | Depth of knowledge alone does not create dependency. |
| Accountability ownership | Being responsible for a system does not mean being the only person capable of working on it. |
| Design authority | Someone guiding decisions without being the sole implementer. |
Boundary
Single-Point Expertise exists when a system’s ability to function depends on the unique knowledge of one individual rather than shared capability within the system.
Systems
Relationships
| Relationship | Concept | Rationale |
|---|---|---|
| produces | Bus Ratio | Concentrated expertise reduces the number of people capable of sustaining system operation. |