This article argues that the real fragility in engineering teams isn’t the bus factor, it's the loss of decision context. Most systems depend on knowledge locked in a few heads, and when that disappears, teams pay for it in outages, rewrites, and slow recovery. The post proposes a simple operating model: capturing intent through decision logs, enforcing a technical "constitution" and using automation to reduce drift, so teams can scale without accumulating invisible risk.
I would love to hear from the community how are you handling tribal knowledge within your organisation
This article argues that the real fragility in engineering teams isn’t the bus factor, it's the loss of decision context. Most systems depend on knowledge locked in a few heads, and when that disappears, teams pay for it in outages, rewrites, and slow recovery. The post proposes a simple operating model: capturing intent through decision logs, enforcing a technical "constitution" and using automation to reduce drift, so teams can scale without accumulating invisible risk.
I would love to hear from the community how are you handling tribal knowledge within your organisation
Post link: https://brihatijain.com/blog/beyond_the_bus_factor