AI did not end the data literacy crisis. It changed it. As machines move from providing information to interpreting it and recommending what to do, the scarce skill is becoming judgment: knowing what to trust, what to question, and what decisions are still ours to make.
Evidence does not make decisions. People interpret it, weigh it, challenge it, and make judgments. A courtroom reveals what leaders can learn about evidence, expertise, confidence, and data-informed decision-making.
Feeling sure doesn't mean you're right. Learn five simple ways to question what feels true, spot what might be influencing you, and make better decisions about what to believe.
When a decision fails, leaders point to the model. The analysis had already removed the judgment that would have caught the mistake, long before the call was made. This is how analytics stops being a tool you use and becomes one you hide behind.
The model didn't fail you. It replaced the judgment that would have caught the mistake.
The familiar critique of analytics is that models sometimes give wrong answers and leaders should treat them carefully. The deeper problem runs underneath. Analytics also quietly removes the slow work that builds the judgment to recognize a wrong answer in the first place, then absorbs the blame when judgment fails. The visible alibi after a bad call is only possible because a less visible substitution happened years earlier.
Most consequential calls today come with analytical cover. The pain is not that the cover is wrong now and then. It is that leaders can defend a decision in the room and still not own it, and they have stopped doing the work that would let them know when the model is missing something. The current state is fluent agreement with the dashboard. The better state is using the analysis to sharpen your thinking, carrying it into the moment as one voice, and owning the call when it goes sideways.
Anyone whose decisions ride on analytical inputs in high-stakes moments. Operators making calls under time pressure. Executives presenting bets to a board. Analysts and decision scientists watching their work get used as cover. Boards and change leaders responsible for the systems that decide where accountability lands when a call fails.
A working distinction between the kind of decision an analytical tool was built for and the kind it cannot carry. A way to recognize the substitution while it is happening, not years later. Language for the asymmetry where credit routes up to the person and blame routes sideways to the tool. And a clearer sense of what the slow developmental work actually produces, so you can tell when efficiency is removing waste and when it is removing the formation that makes ownership possible.
The executive stood in front of the board explaining why the initiative had failed. A forecast that once looked solid no longer matched reality. The market had moved, assumptions had broken down, and the expected outcome never arrived.
Then came the sentence that ended the real conversation. "The model recommended it." The room stopped examining the decision and started examining the model. But that was not where the story began. By the time decision-makers point to a model after a bad decision, they have often spent years relying on it to answer questions they used to have to answer themselves.
Most people notice the move that happens after the decision. The model becomes part of the explanation, and responsibility starts to drift. The scary part is that few people notice what made that move possible.
It's called the Alibi Effect: when analysis becomes a substitute for judgment on the way in and a shield from accountability on the way out.
Understanding how that happens requires distinguishing between two very different kinds of decisions.
Most data tools are built for one kind of decision and asked to do another.
The first kind of decision is prep-grade. Conditions are stable, the question is well-defined, and you have time. In sports, that is a general manager building a draft board who has weeks to prepare. In business, that is a CFO modeling next year's pricing over the span of months. In both those situations, the work rewards patience and rigor.
The second kind of decision is in-game. Conditions shift while you are deciding and the question keeps changing shape. In sports, that is a coach calling a timeout with forty seconds left who does not have time to consult a chart. In business, that is a CEO responding to a competitor's surprise announcement. They cannot wait for the model to refresh.
Analytics in both business and sports were built mostly for the first kind of decision. The trouble starts when leaders pull prep-grade tools into in-game moments, and then point at those tools when the call goes wrong.
This ends the free preview.
Create a free account to get full access. No payment required.
Sign up for free
AI did not end the data literacy crisis. It changed it. As machines move from providing information to interpreting it and recommending what to do, the scarce skill is becoming judgment: knowing what to trust, what to question, and what decisions are still ours to make.
Evidence does not make decisions. People interpret it, weigh it, challenge it, and make judgments. A courtroom reveals what leaders can learn about evidence, expertise, confidence, and data-informed decision-making.
Feeling sure doesn't mean you're right. Learn five simple ways to question what feels true, spot what might be influencing you, and make better decisions about what to believe.
We teach data literacy as a ladder: data at the bottom, wisdom at the top, climb step by step. But the rungs are not where the work happens. The judgment lives in the gaps between them, and that is exactly where AI now carries us straight past.
