The Consistency Gap: Why Leaders Make Different Decisions on Identical Problems Depending on When They Are Asked

The Problem Hiding Inside Good Judgment

An executive at a mid-sized logistics company approves a budget exception for a sales team requesting additional headcount in Q1. Three months later, a comparably scoped request from an operations team is declined. The business case quality is similar. The strategic rationale is coherent in both instances. The difference is that Q1 was optimistic and Q3 is cautious. No policy changed. No formal criteria shifted. The executive simply felt differently on two different days inside two different quarters.

This pattern is not a character flaw. It is an organizational design flaw, and it is far more prevalent at director and above levels than most leadership teams are willing to examine carefully.

The term behavioral scientists use for this phenomenon is decision inconsistency, sometimes described as "noise" to distinguish it from directional bias. Where bias pulls decisions in a predictable direction, inconsistency produces variability across identical or structurally similar choices. The result is an organization where outcomes depend not just on the quality of a proposal, but on timing, mood, recent events, and conversational framing. Teams learn this, even when they cannot articulate it, and they begin to optimize for access and timing rather than substance.

Why This Is an Executive-Level Problem, Not a Process Problem

The instinct in most organizations is to solve consistency problems through process. More approval layers, more documentation requirements, more committee review. These interventions sometimes reduce variance, but they address the symptom rather than the mechanism, and they typically add coordination cost without changing the underlying judgment pattern.

The actual mechanism is the absence of durable criteria. When leaders have not committed in advance to the standards they will apply to a class of decisions, they reconstruct those standards in the moment, using whatever inputs are most salient. Last week's board conversation. A peer's offhand comment. A recent setback in an adjacent function. The reconstruction is unconscious and feels like judgment, which is part of what makes it difficult to detect.

At director and above, this matters in ways that compound. Senior leaders are making fewer decisions than their teams, but the decisions carry higher stakes and longer consequence horizons. A single inconsistent call about strategic investment, vendor selection, or organizational design can cost quarters of execution capacity before the inconsistency is even recognized. More importantly, the people observing those decisions are highly capable professionals who draw inference from what they see. Inconsistency at the top teaches teams that the formal rationale is not the real rationale, and once that lesson lands, it is difficult to unlearn.

What Durable Decision Criteria Actually Look Like

The solution is not a rubric for every decision the organization faces. That would be both impractical and counterproductive; many executive decisions require contextual judgment that resists standardization. The more useful target is identifying the categories of decision that recur often enough that inconsistency is likely, and creating explicit criteria for those categories in advance.

Consider a hypothetical example: an organization that regularly faces requests to add headcount outside the annual planning cycle. Without pre-committed criteria, each request is evaluated as if it were unique. With durable criteria, the team has already agreed on questions that must be answered before approval is possible: Is this role replacing throughput already committed in the plan? Is the funding source identified and approved? Is the work requiring this role expected to persist beyond eighteen months? None of these questions eliminate judgment. They do ensure that judgment is applied to the same factors each time.

The criteria do not need to be elaborate to be effective. They need to be documented, shared with the people whose proposals will be evaluated against them, and reviewed when they stop fitting the decisions the organization is actually making. That review step matters. Criteria that are never revisited become outdated constraints rather than useful anchors.

The Disclosure Discipline

One of the highest-leverage habits a senior leader can build around this problem is the practice of stating the criteria before seeing the options. This is distinct from deliberating carefully after reviewing a proposal. It means naming, in advance, the conditions under which a yes is appropriate and the conditions under which a no is appropriate for a given category of choice.

This sounds simple. It is surprisingly uncomfortable in practice, because it forecloses the flexibility that leaders often interpret as sophistication. The instinct is to preserve optionality, to see the full picture before committing to a framework. But that instinct, applied broadly, is precisely what creates inconsistency. The leader who evaluates every case on its own merits, without reference to pre-committed standards, is not exercising superior judgment. In many instances, that leader is reconstructing criteria after the fact to justify a choice already made by less deliberate means.

A practical suggestion for teams working with a senior leader is to request that the evaluative criteria be surfaced as part of the briefing conversation, before the recommendation is presented. This creates a moment where the leader can articulate the standards that should govern the decision, independent of the specifics of the case at hand. When the case is then presented, the subsequent conversation is more disciplined and the outcome is more likely to reflect the organization's actual priorities rather than the context of that particular day.

Building Consistency as an Institutional Capability

Organizations that manage this well tend to have a few practices in common. They distinguish between decision categories with enough specificity that criteria can actually be written. They create lightweight records of significant decisions that include the criteria applied, not just the outcome reached. And they conduct periodic reviews where similar decisions are placed side by side to test whether the organization applied consistent reasoning across cases.

That last practice is underused. Comparing a set of related decisions made over a twelve-month period, with an honest question about whether the same standards were applied, is an uncomfortable exercise. It also tends to surface the inconsistencies that are costing the organization the most. Teams that have received different answers to similar questions are rarely confused about this. They have usually already reached conclusions about what the variability means. The review gives leadership a structured opportunity to either confirm that the conclusions are wrong, or to acknowledge the gap and commit to closing it.

Consistency is not uniformity. Good executive judgment will always require adaptation to context. The goal is not to eliminate variation in outcomes, but to ensure that variation in outcomes reflects variation in the relevant facts rather than variation in the leader's state of mind on the day the question arrived. That distinction, maintained deliberately over time, is one of the clearest signals of institutional maturity a senior leader can offer.