The Real Test of Trust Happens When You're Not There
Every leader I ever met said they “trust their team.”
I said it too. And I meant it. Then I would take a week off and I’d be checking email from the airport, the hotel, or the camp ground. Not because anything was on fire. Because I wanted to know. I’d tell myself I was just staying in touch so it would be an easier reentry on Monday. If I am honest, I really wanted to make sure things weren’t dropping while I was gone.
That gap between what I said and what I did took me a long time to notice, and longer to admit. My team wasn’t unreliable. I checked in anyway, every trip, for years, and never once asked what it was actually costing me.
Trust gets tossed around loosely, like it’s a feeling. Something you extend to people, like credit. In practice it’s closer to a framework or infrastructure. It’s the set of things you put in place ahead of time that enable work to continue without you in the room. If those things don’t exist, no amount of saying “I trust my team” changes what happens when you go quiet for two weeks.
Saying It and Building It Are Not the Same Thing
Here’s the uncomfortable truth. If the work stalls when you’re gone, that is not a people problem. That’s a design problem, and you own the design.
I spent years believing the opposite. When something waited for me, I felt more important than I actually was. I read it as a signal the team needed more coaching or more experience or more time to grow. Sometimes that was true. More often the team was perfectly capable of making the call but had learned, from watching me, that calls get made when I’m available.
People are good at reading what actually gets rewarded. If every decision that goes around you comes back for a second look, they stop going around you. You didn’t say that out loud. You didn’t have to.
The Tells
The behaviors that undermine trust rarely look like distrust. In fact, they usually look and feel like helpfulness. That’s what makes them hard to catch in yourself.
You stay on the invite. The recurring meeting you no longer need to attend, but you keep the seat because you like knowing. Your presence changes the meeting. People pitch to you instead of discussing, negotiating and deciding with each other.
You ask to be looped in. A reasonable request that quietly converts a decision into a proposal. Once you’re looped in, you’re the approver, whether or not anyone (including you) intended that.
You answer too fast. Someone brings you a question they could have worked through. You solve it in ninety seconds because solving it is easy and you’re good at it. It feels generous. It actually teaches people that bringing you questions is faster than answering them.
You reopen settled things. This is the expensive one. Come back from a week away, ask why a decision went the way it did, and you’ve told everyone that decisions made in your absence are provisional.
I did all four. Not constantly, and not with bad intent, mostly unknowingly. Unfortunately, I did these often enough that my team learned the pattern before I did.
Trust Is Something You Install Before You Leave
The work of being able to disappear is done well ahead of the act of disappearing. Four things I have found to matter more than the rest.
Write down who decides what. Not implied, not understood, written. Which decision rights belong to the team, which ones need a conversation with you, and which ones genuinely need to wait. Most teams operate on an unwritten version of this that everyone interprets slightly differently. Putting it on paper takes less than an hour and removes an enormous amount of hesitation.
Establish escalation criteria instead of escalation instincts. “Call me if it’s important” is not a criterion. Important is a judgment call, and the person making it is guessing at your threshold. Give them the actual line. Any spend over $X. Any change to a committed delivery date. Anything with legal or safety exposure. Anything that a customer would notice. Everything else, you’ll hear about when you’re back.
Build context, not instructions. Instructions cover the situations you anticipated. Context covers the ones you didn’t. If your team understands why the roadmap is sequenced the way it is, what the sponsor actually cares about, and where the political sensitivities sit, they can handle a situation you never briefed them on. If all they have is a task list, the first surprise sends them looking for you.
A name, not a committee. Someone is holding the wheel while you’re out. Say who. Say it to the team and say it to your peers and stakeholders, because half the pressure to break glass and call you comes from outside your org, not inside it. A stakeholder who knows exactly who to go to will go to them. A stakeholder who doesn’t will go to you.
None of this is complicated. It’s just work that never feels urgent, which is exactly why it doesn’t get done until something forces it.
The part that takes real discipline is practicing it while you’re still there. Establish the go to for product decisions as the product manager. Get the analyst used to working through research and escalations. Empower the developer to make code decisions and define architecture. It’s not taking anything away from you. It’s building their muscle so they know what to do, which makes it automatic when you’re away.
Coming Back Is the Audit
A few years ago I was managing a cross functional team that had been together for about four months. I went on vacation in December for two weeks with several deliverables and milestones due while I was away. I was worried about them. So I checked email each day and joined a couple of “important” meetings.
I came back on Monday to fewer than 50 emails waiting for me. At the time I read that as a good sign.
It wasn’t. My inbox was light because I had never actually left. My team escalated early and waited on decisions because I was right there to ask. I hadn’t taken a break, and I hadn’t given them one either. Every email I sent while I was supposed to be offline told them the same thing: I didn’t trust this to run without me.
The other thing I lost is the one I regret more. The pile waiting for you when you come back is the most useful information you will ever get about your operating model, and I had thrown mine away before it could form.
Look at what’s sitting there. Not the volume, the type. Decisions that waited for you point straight at a gap in decision rights. Questions that could have been answered internally point at a context gap. Escalations that weren’t real escalations point at criteria that were too vague. Silence on something that should have escalated points at criteria nobody believed.
That’s a free diagnostic, and most of us waste it. We come back, dig out, and never ask what the pile was telling us.
The better habit is to spend thirty minutes with your internal team leaders in the first week back. What did you have to decide? What factors led you to your decision? What did you almost call me about, and what stopped you? What information did you wish you had? You will learn more from those questions than from any offsite exercise about team maturity.
The Part Nobody Warns You About
At some point you will come back and find a real decision was made, correctly, using good judgment, but it is not the decision you would have made.
This is the moment. Everything you’ve built up to here gets tested in about four seconds, and your face gives away the answer before your mouth does.
If the outcome was good and the reasoning was sound, the decision stands. Even when yours would have been better. Especially then. The cost of overturning a defensible call is not the cost of that one call. It’s every future decision that now routes back through you, because the team just learned that your absence is temporary and your judgment is permanent.
You can still teach. There’s a version of the conversation that sounds like “walk me through how you got there,” and ends with you sharing a consideration they didn’t have. That’s coaching, and it strengthens the next call they make. There’s another version that sounds like “here’s what I would have done,” and ends with the decision quietly reversed. That’s a reversal wearing a coaching costume, and everyone in the room can tell the difference.
Sit with the discomfort. It passes faster than the damage does.
Real Trust
A team that only performs when you’re watching is not a high-performing team. It’s a well-managed one, which is a different and much smaller thing.
The leaders I’ve learned the most from were unremarkable in the room and impossible to replace outside of it. Their teams made good calls on Tuesday whether or not the leader was there on Tuesday. That doesn’t happen because those leaders were more trusting by nature. It happens because they did the unglamorous work of writing down who decides what, and then held the line when it got tested.
Trust isn’t something you feel about your team. It’s something you build, and its proven when you’re gone.
Have you ever come back from time away and found the pile in your inbox was telling you something? Connect with me on LinkedIn or Substack to continue the conversation.