When Past Team Failures Become Your Team's Problem

I want to tell you about a situation I'm currently navigating as a team lead. A senior technical leader came in with a reputation. Not a bad one on paper. He'd been around, worked with multiple teams, seen projects go sideways. On paper, experience. In practice, something else entirely. Before we'd shipped a single line of code together, before he'd sat in a single planning session with us, before he'd looked at our past projects or asked a single question about how we work, he had already decided what kind of team we were. We were a risk. A liability. Another team waiting to fail. And everything that followed came from that assumption. What It Actually Looks Like It doesn't always show up as open hostility. That would almost be easier to deal with. Instead it looks like this: We ran benchmark tests. We ran load tests. We brought results to the table, clean numbers, real data. They got acknowledged with a nod and then quietly set aside in favor of a gut feeling shaped by teams he'd wor