Why the demand for "bold decision-makers" reveals an architectural failure, not a talent shortage.
The Quiet Disappearance of Practice Fields
There is something peculiar about the way large organizations talk about judgment. They want more of it. They say so in hiring briefs, leadership offsites, and annual reports. They describe the ideal future employee as someone capable of higher-order thinking — someone who can navigate ambiguity, challenge assumptions, and make consequential calls under uncertainty. And yet, when you look at how those same organizations actually operate, almost every system they have built over the past three decades has been designed to make judgment unnecessary.
This is not a contradiction born of hypocrisy. It is a design outcome. Standardization, process automation, approval hierarchies, compliance frameworks — each of these was introduced to reduce variance, minimize risk, and ensure consistency. They succeeded. And in succeeding, they quietly eliminated the conditions under which judgment was practiced, tested, and formed.
A mid-level manager in 2005 might have been asked to decide between two vendors based on incomplete data, negotiate a scope change with a difficult client, or determine whether a flagged transaction warranted escalation or dismissal. These were not heroic decisions. They were ordinary. But they required the exercise of judgment in a context where the outcome was uncertain and the criteria were not fully specified. The manager had to decide not only what to do, but what mattered.
That kind of environment — imperfect, slightly dangerous, full of low-stakes rehearsals for high-stakes thinking — has largely vanished. It was optimized away. The vendor decision now follows a procurement rubric. The scope change triggers a change control process. The flagged transaction is routed by an algorithm. Each improvement was rational in isolation. Together, they constitute something more significant: the removal of the developmental infrastructure for judgment itself.
When organizations now say they need people with "chutzpah" — with the audacity to think independently and make hard calls — they are describing a capacity that their own structures have systematically prevented from developing. The demand is real. But it is not a talent problem. It is an architectural one.
What AI Actually Displaced
The conventional narrative around AI and work focuses on task replacement: which jobs will be automated, which skills will become obsolete, which roles will survive. This framing, while intuitive, misses the more consequential shift. AI has not primarily replaced tasks. It has replaced the texture of decision-making environments.
Consider what a knowledge worker experienced before the current generation of AI tools. Gathering information was slow, often requiring consultation with colleagues, manual research, or waiting for data to be compiled. This friction was inefficient. It was also formative. The slowness of information gathering created space for interpretation. The incompleteness of data required assumptions. The need to consult others demanded the articulation of reasoning — explaining not just what you wanted to know, but why it mattered and what you intended to do with it.
AI has compressed this entire process. Information arrives instantly, pre-synthesized, often with recommendations attached. The cognitive work of framing a question, tolerating ambiguity, and constructing a provisional interpretation has been substantially reduced. What remains is a cleaner, faster, more efficient workflow — and a worker who has fewer occasions to practice the very skills the organization claims to need.
This is not an argument against AI adoption. It is an observation about a secondary effect that most implementation strategies ignore. When you accelerate the information layer, you do not merely speed up decisions. You change the phenomenology of deciding. The person making the call has less contact with the raw material of the problem. They see the output of analysis rather than the struggle of analysis. And struggle, uncomfortable as it is, was where judgment was built.
The result is a workforce that is simultaneously more informed and less practiced in the act of judging. They have access to better answers but diminishing capacity to evaluate whether those answers address the right questions.
The Compliance Trap
Organizations have historically managed this tension through compliance structures. When individual judgment is unreliable or unevenly distributed, you replace it with rules. Compliance-based systems — whether regulatory, procedural, or cultural — function by specifying in advance what the correct action is for a given situation. The worker's role is not to judge but to match: identify the situation, locate the applicable rule, execute accordingly.
This approach works well when the environment is stable and the relevant situations are known in advance. It fails — sometimes catastrophically — when the environment shifts faster than the rules can be updated, or when novel situations arise that do not map cleanly to existing categories.
The introduction of AI into organizational workflows has dramatically accelerated this failure mode. Not because AI breaks rules, but because it generates situations that the rules were never designed to address. When an AI system produces a recommendation that conflicts with established policy, who decides? When an automated process yields a result that is technically compliant but contextually wrong, who intervenes? When the data supporting a decision is generated by a model whose reasoning is opaque, who takes responsibility for the outcome?
These are not edge cases. They are the new normal. And compliance-based organizations are structurally unprepared for them — not because their people lack courage, but because the system provides no legitimate space for the exercise of judgment. The compliance framework, by design, treats individual judgment as a source of error to be minimized. When the environment suddenly requires judgment at every level, the framework has nothing to offer.
This is where the call for "chutzpah" originates. It is a symptom. Organizations sense that something is missing — that their people are not making the kinds of decisions the moment requires — and they attribute the gap to individual temperament. If only our people were bolder. If only they would think for themselves. If only they had the nerve to challenge the status quo.
But nerve is not the issue. The issue is that the organization has built no structure within which nerve can be exercised productively. Boldness without a designated arena is indistinguishable from insubordination. Independent thinking without sanctioned scope is career risk with no corresponding organizational benefit. The people are not failing. The architecture is.
Decision Boundaries: The Missing Layer
This is the problem that the concept of Decision Boundary is designed to address. A Decision Boundary is the explicit demarcation of where human judgment is expected, permitted, and accountable within an organizational system. It answers the question that compliance frameworks leave unasked: not "what should be decided," but "who decides, under what conditions, and with what authority."
In most organizations, Decision Boundaries are implicit at best. Senior leaders are assumed to have broad judgment authority. Frontline workers are assumed to follow procedures. The vast middle — where the most consequential operational decisions actually occur — operates in a grey zone where judgment is simultaneously required and unsanctioned. People in this zone learn to navigate politically rather than intellectually. They develop an instinct for what they can get away with deciding, rather than a clear understanding of what they are responsible for deciding.
AI makes this ambiguity untenable. When automated systems handle routine decisions and surface increasingly sophisticated recommendations for complex ones, the remaining decisions — the ones that still require human involvement — are by definition the hardest, the most ambiguous, and the most consequential. These are precisely the decisions that demand clear Decision Boundaries: explicit agreements about who holds judgment authority, what criteria they are expected to apply, and how they will be accountable for outcomes.
Without defined Decision Boundaries, organizations face a predictable pattern. AI handles everything it can. The residual decisions — the genuinely difficult ones — land on people who have no clear mandate to make them. Those people either escalate (creating bottlenecks at the top), defer to the AI's recommendation (abdicating the judgment they were retained to provide), or make a call and hope no one questions it. None of these responses constitutes functional decision-making. All of them are rational adaptations to an environment where Decision Boundaries have not been designed.
Decision Design as Structural Work
If Decision Boundaries define where judgment lives, then Decision Design is the discipline of constructing those boundaries deliberately rather than allowing them to emerge by default. Decision Design treats the allocation of judgment as an architectural challenge — comparable in importance to organizational design, process design, or system architecture, and deeply interdependent with all three.
The work of Decision Design begins with a question that most organizations skip: for any given class of decision, what is the appropriate locus of judgment? This is not a question about who is smartest or most experienced. It is a question about where the necessary information, context, authority, and accountability converge. Sometimes that locus is a senior leader. Sometimes it is a frontline team. Sometimes — and this is the case organizations find most uncomfortable — it is an AI system operating within human-defined parameters.
What Decision Design rejects is the default assumption that judgment should always flow upward, or that it can be safely embedded in process rules, or that AI will eventually make the question moot. Each of these assumptions produces a specific failure mode. Upward flow creates decision bottlenecks and strips context from judgment. Process embedding produces rigidity in the face of novelty. AI delegation without boundary specification produces accountability vacuums.
The alternative is to treat decision allocation as a first-class design problem. This means mapping the decisions an organization actually makes (not the ones its org chart implies), identifying where judgment is currently exercised versus where it is merely assumed, and constructing explicit boundaries that align authority with information, context, and accountability.
This is unglamorous work. It does not produce the thrill of a bold AI strategy or the comfort of a new compliance framework. It produces clarity — the organizational equivalent of knowing, at every level, what you are responsible for deciding and what you are not. That clarity is the precondition for everything organizations say they want from their people: independent thinking, courageous judgment, the willingness to make hard calls.
The Structural Nature of Courage
Return now to the original tension: the widespread demand for people who can make bold, higher-level decisions in an environment increasingly shaped by AI. The conventional interpretation frames this as a human capital problem — a gap in skills, mindset, or character that can be closed through better hiring, training, or cultural change.
The Decision Design interpretation is different. It suggests that what looks like a deficit of courage is actually a deficit of structure. People do not lack the capacity for judgment. They lack a system that tells them where their judgment is wanted, protects them when they exercise it, and holds them accountable for the outcomes. In the absence of that system, the rational response is compliance — not because people are timid, but because compliance is the only behavior the architecture rewards.
This reframing has practical consequences. If the problem is temperamental, the solution is motivational: inspire people, empower them, tell them it is safe to be bold. If the problem is structural, the solution is architectural: define Decision Boundaries, allocate judgment authority explicitly, redesign accountability systems to match the actual distribution of consequential decisions.
The motivational approach feels good and changes little. The architectural approach feels bureaucratic and changes everything. Organizations that invest in Decision Design do not need to search for people with chutzpah. They build environments where ordinary judgment — applied consistently, within clear boundaries, with real accountability — produces the outcomes that boldness was supposed to deliver.
Where Judgment Lives
The quiet irony of the present moment is that AI has made judgment more important than ever while simultaneously degrading the conditions under which it develops. Organizations respond by calling for bolder people. But the call itself reveals the gap. If the architecture supported judgment, you would not need to demand courage. Courage is what you need when the structure offers no guidance.
The competitive advantage of the next decade will not belong to organizations with the most advanced AI, the most sophisticated automation, or even the most talented people. It will belong to organizations that have done the patient, structural work of deciding where judgment lives — and designing everything else around that answer. The question was never whether humans or machines would make the decisions. The question, as it has always been, is whether anyone has designed the decision itself.