Micromanagement isn’t always a leadership flaw. Sometimes, it’s an information problem.

When executive leaders repeatedly receive conflicting versions of reality, they eventually stop trusting the system built to inform their decisions. Deprived of a clear operational truth, they move closer to the floor, insert themselves into tactical choices, and substitute personal judgment for organizational process.

I think of this phenomenon as Decision Drift.

Decision Drift is the gradual migration of decisions away from their intended owners when leadership loses confidence in the underlying information, definitions, or processes used to make them. It is rarely intentional, but once it takes hold, it degrades operational agility and leaves leadership acting as referees rather than strategists.

The Pattern

The sequence is strikingly consistent across organizations.

It starts with a surface-level contradiction: Marketing reports that lead volume is strong and targets are being met, while Sales insists that pipeline quality is degrading and revenue is at risk.

Seeking clarity, leadership asks for more reporting. But more reporting simply leads to more reconciliation. Teams spend hours in offline spreadsheets attempting to align their numbers, yet the fundamental disagreement remains. Why? Because no one has addressed the conflicting definitions underneath the metrics.

When the system cannot resolve disagreement, authority eventually tries to.

Without a reliable framework to evaluate who is right, executives step into the void. They make tactical mandates, overrule operational teams, and absorb day-to-day decision-making power—all in an attempt to manually force alignment. Executive intervention becomes the only rational response to a system that cannot resolve its own contradictions.

The Story: A Dispute Over Direct Mail

In revenue organizations, one of the most common fracture points for Decision Drift is the handoff between marketing and sales.

Consider an organization where the executive team slowly absorbed routine marketing choices. The drift began when the sales leader complained that lead volume had dropped below historical highs, insisting that past success was driven by heavier direct mail investments.

The marketing team had already conducted a matchback analysis on recent direct mail campaigns. Their analysis demonstrated a negative ROI for matches on the email addresses included in the mail list and highly disputed returns for broader company matches, largely because many converting accounts were simultaneously receiving outbound sales calls and renewal prompts.

Marketing was asking a specific financial question: Can we demonstrate that direct mail caused enough incremental revenue to justify its cost?

Sales was asking a very different operational question: Did accounts receiving direct mail subsequently enter or advance through our pipeline?

Both departments produced defensible analytics that supported their respective positions, but they were answering fundamentally incompatible questions. Because the organization lacked an agreed-upon attribution standard to reconcile those questions, leadership couldn't determine which dataset represented reality.

Lacking a unified framework to adjudicate the claim, the executive team defaulted to intuition. They sided with Sales and mandated an immediate increase in direct mail volume.

Marketing complied, and volume rose. Almost immediately, the narrative shifted: Sales claimed the incoming leads were now poor quality. The metric changed, but the structural disagreement remained.

Frustrated and seeking control, leadership began micromanaging the tactical execution itself, reviewing individual content assets and dictating campaign focus areas. They weren't acting out of a desire to micromanage; they were stepping into an operational void created by low information trust.

What Was Actually Happening

The problem was never direct mail. It wasn't lead volume, and it wasn't a personality clash between sales and marketing leaders. Decision Drift doesn't require one side to have bad analytics—it occurs precisely because two competent teams can produce defensible answers from incompatible definitions.

The organization had simply failed to establish a shared definition of success capable of surviving disagreement.

When you trace the direct mail dispute to its origin, you find two departments operating on completely different sets of assumptions. Marketing measured success by total response volume and cost per incremental match, while Sales measured success by closed-won revenue and pipeline progression, ignoring any lead that required significant multi-touch nurturing.

Without co-created definitions for what constituted a qualified lead, an ideal customer, or a valid touchpoint, any fluctuation in volume or pipeline became an emotional, highly subjective crisis.

When operational process cannot resolve disagreement, executive judgment eventually has to.

Finding the Drift: Trace the Disputed Metric

Decision Drift does not happen everywhere at once. It accumulates around specific points of friction. One reliable way to locate it is to take the single metric generating the most executive disagreement and trace it backward:

Dashboard → Calculation → System → Process → Definition → Owner

At every single step, ask one question: Does everyone still mean the same thing?

In the case of the direct mail dispute, tracing "lead volume" backward through the stack eventually hits a dead end at the definition level. Marketing had one definition of a qualified lead; Sales had another.

The executive dashboard wasn't generating two competing realities out of thin air—the organization had created two separate realities long before the data ever reached the screen.

Start With the Disagreement

You don't have to overhaul your entire data architecture to begin correcting Decision Drift. A new dashboard built on unresolved definitions simply makes the underlying disagreement easier to visualize. Start directly with the disagreement itself:

1. Identify the disputed metric. Which number repeatedly creates executive friction?

   
   

2. Agree on its definition. What explicitly qualifies, and what explicitly does not?

   
   

3. Establish ownership. Who owns the definition, data entry, exceptions, and changes?

   
   

4. Trace the decision path. Where does the metric originate, how is it transformed, and which executive decisions depend on it?

   
   

Decision Drift reverses when the organization becomes capable of resolving disagreement without escalating it.

Leadership doesn't need perfect information. It needs enough confidence in the definitions, ownership, and decision path to let decisions remain where they belong. Operational trust isn't created when everyone agrees—it's created when the system can reliably resolve what happens when they don't.

If you trace your organization's most disputed metric back to its origin today, would you find a shared operational definition—or two departments managing their own isolated realities?

Best,

Alfred McNair, MBA, ITIL®4, PSPO™   

Founder & Principal, Kinetic Scale Partners