organizational conditions – A transformation doesn’t stall because leaders hire the wrong people—it stalls when organizations build the wrong operating conditions around those hires. The missing piece is how judgment moves through approvals, sign-offs, and performance incentives when amb
I’ve watched this moment happen more times than I can count. The call is made. It’s the right one—defensible, well-reasoned, and not the kind of decision the organization would call reckless. In fact. it’s the exact judgment the company says it wanted when it hired or promoted the person for that judgment in the first place.
Then the roadblock arrives. The people paid to say no start showing up—sometimes politely, sometimes with process language that sounds neutral. No one did anything wrong. The problem is that. in most organizations. saying no to something unfamiliar is the safer answer for whoever has to sign off. A “no” rarely follows anyone home. A “yes” that goes sideways does. So sign-offs multiply: legal review. then a name on an ExCom agenda nobody remembers adding. then a steering committee. then someone in an adjacent function who “needs to be in the loop.”.
Five weeks later, the call that should have taken an afternoon still isn’t made.
What’s striking is how quickly the judgment disappears without ever being explicitly removed. Nobody tells the person to stop using their judgment. Nothing gets that dramatic. The next ambiguous call simply gets run past three people first—just to be safe. The judgment doesn’t vanish. It goes underground.
That’s the shift making this moment feel like it’s “suddenly everywhere.” As AI absorbs more of the execution layer. the volume of unscripted calls organizations need someone—anyone—to make has gone up fast. at every level. The old version of judgment used to be mostly about knowing when to follow the rule and when to escalate an exception. That worked when exceptions were rare enough to run up the hierarchy one at a time.
It doesn’t work when ambiguity is the daily condition for people two and three levels below where escalation used to start. There isn’t enough hierarchy left to absorb the volume.
Years ago, I worked for a division president who got impatient with exactly this issue. He stopped trying to write a rule for every situation and started building the team around principles instead: judgment anchored to a few things everyone understood deeply. rather than a manual nobody could keep current. It looked unconventional at the time. It looks early now.
The gap isn’t about talent. It’s about capability—something specific. Organizational capability is the combined mindset. skillset. and operating conditions that determine whether an organization knows what to do next and can actually do it. Most leadership teams have already addressed one-third of that equation. They’ve hired the mindset, and often the skillset. What hasn’t changed is the operating conditions—the mechanics judgment calls have to move through.
The org chart says you’ve hired for judgment. But the conditions surrounding that hire were built for consistent execution and predictable outcomes, with risk contained through process. Governance bolted onto decisions after the fact will always treat an unscripted call as a deviation to be managed rather than the reason to have made a judgment hire at all. Instead of getting an organization that absorbs judgment. the result is a faster. more frustrated bottleneck—putting the best new hire directly in front of it.
One decision at a time, the pattern shows itself. The same mechanism that blocks an unfamiliar call also teaches people what “safe” looks like. When judgment is treated like an exception to be processed, the organization rewards people for slowing down—not for making the call.
So what does redesign actually require? Five places to start, none of them dramatic, all of them concrete.
First, redesign how you hire and promote for it. Many interview processes ask, “what would you do if,” which mainly tests what a candidate knows how to say. Ask instead for a specific time they worked through a decision with incomplete information. then keep asking what happened next until you can see how they actually think under pressure. Watch for a bias that’s easy to miss: a panel that selects for people who think like the panel will systematically screen out the judgment that doesn’t fit the existing pattern—often the judgment the organization needs most.
Second, trace one real judgment call through your actual organizational conditions. Not the one in the org chart. Pick a recent decision that ran against how things normally get approved. and follow it: how many sign-offs. how many days. how many people who don’t normally talk to each other had to agree. If that call took longer to close than your last technology spend took to approve. you have your answer about what your organization actually rewards moving quickly.
Third, name what doesn’t require escalation—and ask what isn’t being raised. Most organizations define only what does need to go up the chain. Everything below that line defaults to caution because nobody said otherwise. The deeper version of the question is sharper: what problem is someone not raising right now because they’re not sure it’s safe to?. That isn’t a culture question. It’s structural, shaped entirely by what happens to people who go first.
Fourth, protect the first defensible miss. The fastest way to teach a high-judgment hire to stop using judgment is to treat the first reasonable call that didn’t pan out the same as an error. People don’t learn the real rules from the job posting. They learn them from what happens after the first call that didn’t land. Watch that moment closely. It’s the one your best hires are watching too.
Fifth, change what the performance review actually scores. If reviews weight adherence to process over the quality of calls made under ambiguity. the organization is rewarding the opposite of what it claimed to hire for. Incentives that aren’t aligned to scaled. judgment-driven outcomes will always pull people back toward safer behavior. regardless of what leadership says it values.
The leaders who get this right aren’t doing something dramatic. They trace one decision at a time through their own organizational conditions and ask an uncomfortable question: if I hired this person for their judgment. would my organization actually let them use it?. Most leaders have never asked that question about their own company. The ones who have are usually surprised by the answer.
transformation organizational capability judgment hires AI execution governance escalation performance reviews sign-offs ExCom agenda technology spend approval