The Consistency Problem: Why the Same Decision Produces Different Outcomes Depending on Who Brings It

Most organizations believe they make decisions on the merits. Proposals are evaluated, tradeoffs are weighed, and leadership chooses a direction. That is the formal account. The operational reality in many mid-size and large organizations is considerably messier: the same request, carrying the same business logic and the same cost, receives a different response depending on who walks it into the room.

This is not primarily a fairness problem, though it becomes one. It is first a reliability problem. When outcomes depend on sponsorship rather than substance, the organization cannot learn what it actually values, teams cannot predict which investments will earn approval, and leaders cannot build confidence that the decisions flowing from them reflect consistent priorities.

How Sponsorship Substitutes for Criteria

Decision inconsistency rarely develops because senior leaders intend to apply different standards. It develops because those standards were never made explicit in the first place.

When a leader is asked to approve a request, they must evaluate it against something. If the organization has not defined shared evaluative criteria, each leader constructs their own informal framework, drawing on experience, intuition, and the relational trust they hold for whoever is presenting. Two leaders can both act in good faith and still reach opposite conclusions on identical requests, because they are each solving a different implicit problem.

The sponsorship variable enters precisely here. A high-credibility sponsor does not just advocate for a proposal; they also transfer their credibility to the evaluation. A leader who might otherwise hesitate approves the request because they trust the sponsor's judgment. A lower-credibility sponsor presenting the same proposal receives skepticism that is really directed at the sponsor rather than the substance.

Over time, teams learn this. They stop thinking about what makes a proposal strong and start thinking about who should carry it. Resources flow toward politically connected teams not because those teams produce better proposals, but because they have figured out how to route them more effectively.

What Consistent Decisions Actually Require

Consistency does not require uniformity. Not every decision of the same category should produce the same outcome. It requires that variation in outcomes traces to variation in the relevant factors, not to variation in who is asking.

Achieving that requires three things that many organizations skip.

First, the criteria for a category of decision need to be named before specific proposals arrive. When criteria are constructed in response to a specific proposal, they are almost inevitably shaped by whether the decision-maker is already inclined to approve or reject it. Criteria built before proposals arrive are far more likely to be applied consistently because no individual case has yet primed the evaluator's judgment.

Second, the criteria need to be shared across everyone who makes or substantially influences decisions in that category. An individual leader's clarity about their own standards is insufficient if other leaders applying different standards are reviewing requests from the same population of teams. The inconsistency experienced by the organization reflects the aggregate, not the individual.

Third, the criteria need to be recorded in a form that can accompany decisions. When a request is approved or declined, the record should indicate which criteria the proposal satisfied or failed to satisfy. This serves two purposes: it allows decision-makers to audit their own consistency over time, and it gives the teams who submitted proposals an actionable account of what to change, rather than a response that can only be read as interpersonal.

A Practical Starting Point for Leadership Teams

Organizations that want to address decision inconsistency often benefit from beginning with a narrow, high-frequency category rather than attempting to define criteria across all decisions simultaneously.

Consider, as a hypothetical, a technology organization where teams frequently request additional headcount. If the evaluation criteria for those requests are never articulated, each request becomes a negotiation whose outcome reflects relationships, timing, and the persuasiveness of individual managers as much as the underlying need. A leadership team that convenes specifically to define what a strong headcount case looks like, before any specific requests are in the room, is in a far better position to evaluate those requests consistently.

The exercise itself is often revealing. When leadership teams attempt to articulate shared criteria, they frequently discover that they do not agree on what they are optimizing for. One leader weights strategic alignment most heavily. Another weights near-term revenue impact. A third is primarily concerned with risk. This disagreement was always present in their individual decisions; it was simply never visible because each decision appeared to resolve cleanly. Making criteria explicit surfaces the underlying disagreement and creates the opportunity to resolve it once, rather than relitigating it invisibly inside every subsequent request.

The Audit Most Organizations Have Not Run

A useful diagnostic for leadership teams is to select a decision category, gather a sample of decisions from the past twelve to eighteen months, strip out the names and organizational affiliations, and ask whether a neutral observer could identify a consistent logic across the approvals and rejections.

In organizations with strong evaluative criteria, the logic is generally visible. Approved requests share characteristics; rejected ones share different characteristics. The pattern holds regardless of which team submitted the proposal.

In organizations with inconsistency problems, the pattern does not hold. Approved and rejected requests look similar in their content. What differs is harder to see in the substance of the proposals themselves.

This is not a comfortable audit. It frequently reveals patterns that leaders would prefer not to see. But it provides an honest baseline from which improvement is actually possible, and it is far less costly than discovering the inconsistency through the talent consequences it eventually produces.

What Teams Experience When Criteria Are Absent

The organizational cost of decision inconsistency is not limited to the quality of individual decisions. It compounds into a set of behavioral adaptations that are individually rational and collectively damaging.

Teams that learn to optimize for sponsorship rather than substance invest in political positioning instead of proposal quality. Leaders who recognize they are operating in a variable system begin to advocate more forcefully for their teams, because neutrality disadvantages them. Senior leaders absorb energy managing the perception that they apply different standards to different people, even when they believe they do not.

None of this is inevitable. It is the predictable result of leaving evaluative criteria implicit in an environment where many people are making frequent decisions. Making those criteria explicit does not eliminate judgment from organizational decision-making. It gives judgment a stable foundation to work from, and it allows the organization to learn, over time, whether the criteria it has chosen are actually producing the outcomes it values.