When the Data Said Yes

A few years ago I sat in a room where the engagement survey results were being presented to a senior team.

The numbers were fine. The survey showed 78% engagement, modest gains across dimensions, no red flags. The slide deck was well-designed. The recommendations were measured. The HR leader who presented it was competent.

I was watching three of the senior leaders in the room.

One of them had been a manager for fifteen years. She had walked the floor of three of these teams the week before. She had watched two people resign in the month leading up to the survey. She knew, from a kind of accumulated reading no model can reproduce, that something was wrong in the team that the data said was fine.

She did not say anything.

The conversation moved on. The survey was approved. Six weeks later, the team that had scored 78% had three more resignations and a small public crisis that took the legal team two months to clean up.

I keep thinking about the silence in that room.

She had the judgment. The data did not. And the room defaulted to the data.

This is what I have been calling The Human Code for years. The slow, quiet replacement of human judgment with process. Then with platforms. And now, with AI.

I want to name what is happening, because I do not think we are talking about it clearly.

What judgment actually is

Judgment is not decision-making. Decision-making is what most organizations train for. You list the options, you weigh the criteria, you choose. A model can do that as well as most humans now, and faster.

Judgment is what tells you the criteria are wrong.

It is the discomfort that arises when the analysis is correct but the answer feels wrong. The pull to ask a different question than the one being decided. The willingness to override what the system recommends because something inside you says the system is missing the relevant piece.

That something inside you is not magic. It is years of pattern recognition that was never written down. It is the way the team felt three weeks ago, the comment someone made in a hallway, the look on the head of operations' face during the last review. It is data the organization has, but not in any form the system can read.

The leader who has judgment does not always articulate why the answer is wrong. They know it is wrong. They are willing to be uncomfortable in the room until someone else also sees it.

That capability is rare. It is the thing organizations forget to protect.

Why AI accelerates the erosion

The erosion of judgment did not start with AI.

It started decades ago, with the steady move from manager-led decisions to process-led ones. Performance reviews moved from quarterly conversations to standardized forms. Promotions moved from a senior leader's call to a nine-box grid that nobody in the room could explain clearly. Terminations moved from a difficult judgment call to a checklist.

Every one of those shifts had an efficiency story. Every one of them was real. And every one of them slowly removed the muscle that made human judgment functional.

AI is not the cause of this erosion. It is the accelerant.

A model produces a recommendation that is technically correct, sourced from data that is well-organized, presented with the kind of confidence the room rewards. The leader with judgment may sense the recommendation is missing something. But by the time the model has spoken, the burden of proof has shifted. The leader now has to explain why their feeling overrides the data.

In most rooms, they do not bother. They go along.

This is how judgment dies. Not in one decision. In the small, daily practice of deferring to the system one too many times.

What it looks like to protect it

The leaders I have watched protect their judgment over time tend to do three things.

They stay in the room where the work happens. They walk the floor. They take the meetings they could have delegated. They watch the body language in the team that the system says is fine. They build the substrate that judgment runs on.

They speak the discomfort early. When the analysis says yes and something inside them says no, they say so. They do not have the right answer. They have the right unease. They are willing to hold that unease in the room long enough for the actual concern to surface.

They follow up on their overrides. The decisions where they trusted their judgment over the data, they revisit. Not to prove they were right. To learn when their read was actually accurate, and when they had simply been afraid of the system's answer. Over time this builds the trust in their own judgment that makes the next override possible.

These habits look unproductive on a Tuesday. They are the difference between a leader and a process operator.

The premium on the leader who still has it

When AI commoditizes the production of competent answers, the leader who can override a competent answer when their judgment requires it becomes the differentiator.

This is The Human Code.

It is not a framework about resisting AI. It is a framework about protecting the muscle that makes any technology useful in the hands of a leader.

The companies that will navigate the next decade well are the ones with leaders who still trust their own read of the room. Who can say "I know the data says yes. The answer is no. Here is what I am seeing that the system is not." And who are willing to take responsibility for the override when it lands.

That is the work that does not survive automation.

That is the work the next decade will pay for.

The Human Code is not a program. It is a practice. And judgment is the first capability worth protecting.

If there was a moment in your career where you trusted your judgment over the data and the override turned out to be the right call, I want to hear it. The override that lands well is the one most leaders learn from. The override that does not land well teaches just as much.

The person who comes to mind right now is who this was written for.

Send it to them.

Most of what comes next will live here. No newsletter cadence promises. No growth tactics. No five-bullet hacks. Just the slow work.