Planning as Hiding
His stakeholder map had forty-seven names on it. Colour-coded. Cross-referenced with reporting lines, influence scores, and likely objections. He'd been building it for three weeks.
He hadn't spoken to any of them.
"I need to have the perfect plan before I reach out." He worked in pharma — an industry where thoroughness isn't just valued, it's regulated. Where every protocol gets reviewed four times and nobody questions why. The perfect environment for a pattern like his to hide in plain sight.
I didn't ask him about the stakeholder map. I asked him what would happen if he called the first person on the list tomorrow, before the map was done.
His jaw tightened. "That's not how I work."
It's not how he works. That's true. And the question is whether "how I work" is a method or a fortress.
Planning feels like progress. It uses the same muscles — the analysis, the pattern recognition, the systems thinking that got him promoted. His manager sees the late nights and thinks committed. His peers see the comprehensive deck and think thorough.
What nobody sees, including him: the plan is never finished. Yet finishing the plan means acting on it. And acting means being seen. And being seen before he's certain means risking the one thing he can't risk.
Being wrong.
In our third session he described his weekend. He'd spent Saturday mapping scenarios for a meeting that was two weeks away. I reflected the logic back to him: you have to have a plan, you have to be on top of things, because it's safe to be on top of things. It's simply safe.
He nodded, fast. The way people nod when they want you to move on.
Pharma gives this pattern a perfect host. Every delay can be justified. Every additional review is "prudent." The industry selects for people who mistake caution for competence — and then promotes them into roles where the terrain has shifted from protocol to politics, from problems you can solve to situations you can only navigate.
His forty-seven-name stakeholder map was a regulatory submission for a phone call.
He needed to notice what the planning was doing for him — safety, control, the illusion that if the preparation is thorough enough, the outcome is guaranteed. And underneath all of that, so far underneath he'd never looked: the belief that being wrong wouldn't just be a mistake. It would be exposure.
We sat with that longer than he wanted. He kept trying to turn the insight into an action item. That was the pattern too — even the self-awareness became something to plan around.
He made the first call the following week. The stakeholder map still had forty-seven names on it. He started with one.
The person pushed back on something he hadn't anticipated. He didn't have an answer. He said he'd come back to them.
He survived.
Strategy and stalling use the same muscles. The difference is the relationship to uncertainty. One accepts it will be wrong and moves anyway. The other perfects the map so it never has to touch the territory.
...