You Don’t Need to Be in the Room

I was on a prospect call this week while the team worked directly with a customer in parallel. They had pulled me into the prep earlier. By the time it mattered, they had what they needed. They ran it. It went well.

That’s not the interesting part.

The Test Nobody Designs For

Most people in charge test autonomy by choosing to step back. They skip a meeting. They stop responding to a thread. They watch what happens.

That’s a useful exercise. It’s also a controlled one. You’re still watching. You’re still available. The system knows you’re there.

The real test is different. The real test is when the business forces you to be somewhere else and the system doesn’t wait for you to come back.

Not because you chose to let go. Because the work didn’t give you the option.

That changes the data entirely. Controlled experiments tell you whether the team can operate without you. Uncontrolled moments tell you whether the system was designed to.

Presence Is Not Contribution

Most people in charge confuse these two things for a long time. Being in the room feels like adding value. Sometimes it is. Often it’s just proximity disguised as leverage.

The shift worth paying attention to: when does your team start pulling you into the thinking instead of the execution?

That’s a structural change, not a behavioral one. It means clarity exists about where your input shapes outcomes and where your presence just adds comfort. When that line gets drawn well, the team doesn’t need you in the room. They need you before the room.

Then they move.

The Tradeoff Nobody Talks About

There’s real leverage in being upstream of execution. There’s also a cost.

When you’re not in the room, you don’t control how things land. You don’t adjust in real time. You don’t know how it went until it’s over.

That discomfort doesn’t go away. It shouldn’t. The moment it feels comfortable, you’ve probably stopped paying attention to whether the system still holds.

The question worth asking after every one of these moments: did it work because the system is sound, or because this particular situation was forgiving?

That distinction matters. One scales. The other just got lucky.

The Harder Standard

In January, I wrote about auditing every place the system still depended on me. Decisions that paused. Approvals that existed for comfort. Wins that couldn’t repeat without personal intervention. Then I wrote about redesigning around that dependency.

This week was one data point. Not a conclusion. The redesign held under real conditions for the first time. The business needed me somewhere else and the system didn’t flinch.

When something eventually breaks, the question a leader asks isn’t “why wasn’t I there?”

It’s “what in the system made my presence necessary?”

That’s a harder standard. It also scales.