I used to think trust was something you earned through a big moment.
A difficult project delivered on time. A decision that turned out to be right. A problem solved that nobody else had been able to solve.
I don't think that anymore.
I've worked in teams where trust felt high from the start, and teams where it felt low no matter what anyone did.
The difference, when I look back, was rarely capability. The teams that were trusted most weren't necessarily the most talented ones. They were the ones where you consistently knew what to expect.
They said they'd do something. They did it.
They said something was uncertain. It turned out to be uncertain.
They said they'd flag something early. They flagged it early.
None of those things are dramatic. But repeated over months, they accumulate into something that matters more than any single delivery.
The failure mode I've seen most often isn't dishonesty.
It's optimism.
Engineers who say yes when the honest answer is maybe. Leaders who commit to stakeholders before the team has had a chance to think the work through. Estimates that reflect how long something would take if nothing went wrong, rather than how long it actually tends to take.
I started noticing the gap when I changed how I asked about complexity. Instead of how many points is this, I'd ask: if you had to guarantee delivery, how many points would this be. The number was almost always higher. Not because engineers were being lazy with the first answer, but because the first question invited a best case, and the second one asked for an honest one.
Every missed date, on its own, is understandable.
But the pattern teaches people something. It teaches them not to rely on what they're told.
And once that lesson is learned, it's very hard to unlearn.
Trust isn't built through announcements.
It accumulates through small acts of consistency.
One of the most useful things an engineering leader can do is make the gap between what the team says and what happens as small as possible.
Not by being pessimistic. Not by sandbagging estimates.
By being honest about what's known and what isn't. By surfacing problems while they're still manageable. By treating stakeholders as adults who can handle a realistic picture.
It feels uncomfortable at first. Most teams have learned that bad news is unwelcome, and they've adapted accordingly.
But stakeholders don't actually want to be surprised. They want to be able to plan. And you can't plan around information you don't have.
The teams that earn the most trust over time aren't the ones that never have problems.
They're the ones whose problems feel like information rather than failures.
That distinction is the whole game.