1.If your top senior engineer left tomorrow, how long would it take to figure out why core microservices were designed this way?

Weeks of pain reading old commits and guessing trade-offsSearching Slack threads hoping discussions weren’t deletedReading static Confluence docs that are 6 months outdatedMinutes: the original discussion, PR and decision record are linked and searchable

2.How much architecture knowledge lives purely in individual developers’ heads?

Over 70% (Extreme Tribal Knowledge)40% to 70% (Significant Key-Person Dependency)20% to 40% (Partial Documentation)Under 20% (most reasoning is written down and findable)

3.What happens when a new engineer asks "Why did we stop using Service X in Q2?"

Senior dev gets interrupted on Slack for 30 minutesThey spend 2 hours searching Jira & GitHub ticketsThey find the decision and its sources themselves in a few minutes

0 of 3 answered

Company knowledge death test.

More free tools

See where your team’s knowledge lives.