The No-Go Zone
The president of a billion-dollar vendor introduced me to his long-term customers as the most important person to know in the company. He did this repeatedly. Over the course of that fiftieth anniversary event in Minnesota, he made sure everyone understood who I was and what I represented.
He wasn't wrong.
I could do things the head of sales couldn't do. Not because I outranked him — I didn't, not on paper. But because of what his involvement would have drawn: attention, visibility, the full weight of the formal relationship. I operated in the background. I got things set up. I moved things that needed moving. And then the head of sales could walk in and get them done. That arrangement worked precisely because it was quiet. The moment it became visible, it stopped working.
So when the president invited me to the box at the baseball game, I felt the contradiction. He had just spent two days telling everyone I was the most important person to know. Now I was sitting next to the person who actually had the budget, the signing authority, the ability to put a number on a contract. I don't even like baseball. But I felt obligated to honor what he'd said about me.
So I called it out. I asked him directly: am I supposed to be at this game?
He turned around and said: do you want to tell the head of sales he can't go?
That was the answer. He wasn't apologizing, and he wasn't taking back anything he'd said about me. He was telling me plainly where the line was — and who held what on each side of it.
That line is what I now call the No-Go Zone.
Not a rule. Not a policy. Not something written in an org chart. The No-Go Zone is the place where what an organization depends on quietly meets what it can acknowledge out loud. Everyone already knows where it is. You find out where yours is the moment something valuable is actually on the table.
Here is what made the difference for me: I knew what I cared about.
I cared about the fact that he recognized my ability to influence and get things done. That recognition was real. It had been demonstrated, publicly, repeatedly, over two days. The baseball game didn't touch it. The head of sales having the box seat didn't touch it. Those were his. I wasn't there for those.
Because I knew what I came for, I could read the situation accurately. I wasn't diminished by the constraint. I was informed by it. The No-Go Zone became visible, I understood it, and I could keep working — on the right things, in the right register, without mistaking the boundary for a verdict.
Most people hit a No-Go Zone and feel demoted. The title didn't match the room. The introduction didn't match the seat. Something that was said publicly didn't hold when the real decision arrived.
That feeling is data. But only if you know what you're measuring against.
Not all No-Go Zones are the same. Some are real — budget, regulation, authority structure. They belong where they are. Some are protected — nobody wants to touch them, the cost is political or relational, and moving them requires a different kind of conversation. And some are simply unexamined. They arrived without being checked. A workaround became a process. A preference became a policy. An assumption put on a blazer and started introducing itself as a constraint.
The work in any organization is to sort them. Not to eliminate the No-Go Zone. Sometimes it belongs there. But to distinguish between what's actually fixed and what has just never been questioned.
The most dangerous No-Go Zone isn't the one nobody names.
It's the one you mistake for something it isn't — because you never clarified what you actually came for.
What are you taking for granted that you haven't named yet?
Name it before the room makes you. Then sort it — Fixed, Protected, Unexamined — and move from a place you actually chose. That's the work I do with senior leaders in an Assumption-Ground Audit: surfacing the ground a direction is standing on while there's still room to question it.
That question is easier to ask before the baseball game than after.