Tribal Knowledge: The $300K Problem Nobody Talks About

I watched a $4.2 million engineering hire fail because of something that never showed up in a single dashboard. We had recruited a senior architect away from Stripe. Brilliant engineer. Perfect cultural fit. She started on a Monday. By Friday, she had asked the same question to four different people and gotten four different answers about how our payment processing pipeline worked. By week six, she was spending more time in Slack archaeology than writing code. By month three, she gave her notice. "I can't be effective here," she told me. "The system makes sense to people who built it. I'm not one of them." The system she was describing had a name: tribal knowledge . What Tribal Knowledge Actually Is Tribal knowledge in software development is NOT "stuff we haven't documented yet." That framing makes it sound like a documentation problem with a documentation solution. It's deeper than that. Tribal knowledge is the gap between what your code does and why it does it that way . It's the ar