Deliver What Matters · LinkedIn

The Best Argument Doesn’t Always Win

In many organizations, the next priority isn’t determined by evidence .

It’s determined by influence—the loudest voice in the room, the highest-ranking leader, the most persuasive presentation, or the stakeholder with the strongest opinion.

We’ve all seen it happen. A decision is made, work begins, and months later everyone wonders why the expected improvement never materialized.

The problem wasn’t the team’s ability to deliver. The problem was that no one ever asked whether the decision was supported by evidence .

At CAIP, ideas came from every direction. Leaders had priorities, program staff had suggestions, applicants shared frustrations, and operations teams highlighted pain points. Every perspective mattered because each represented a different view of the system.

But perspectives alone weren’t enough. The question wasn’t simply, “Who has the best idea? The question became, “What evidence do we have?” That changed the conversation.

Evidence doesn’t eliminate judgment. It informs it.

Sometimes the evidence is quantitative:

Completion rates.
Processing times.
Call volumes.
Abandonment rates.
Sometimes it’s qualitative.
User interviews.
Observations.
Feedback from frontline staff.
Journey mapping.

Together, they paint a much clearer picture than either could alone.

One of the biggest mistakes organizations make is treating opinions as evidence.

An executive says users are confused. A manager believes another approval step will reduce errors. A stakeholder insists a dashboard will solve the visibility problem.

Maybe they’re right. Maybe they aren’t. The point isn’t to dismiss experience. The point is to distinguish between what we believe and what we know . Those are not the same thing.

One question has become a staple of my coaching. “What evidence led you to that conclusion?”

Notice what that question doesn’t ask. It doesn’t challenge the person’s intelligence. It doesn’t dismiss their experience. It simply invites them to separate observation from assumption. That’s a healthier conversation.

Something interesting happens when evidence becomes part of everyday decision-making. People become less attached to being right and they become more interested in learning. Ideas stop competing against each other and, instead, they compete against reality. That’s exactly where they should compete.

Evidence also changes what happens after delivery.

Instead of asking: “Did we finish?” Teams begin asking: “What happened?”

Did adoption increase?
Did processing time improve?
Did users complete the task more easily?
Did the change produce the outcome we expected?

Those questions turn delivery into learning. And learning becomes the engine of continuous improvement.

Evidence isn’t about proving people wrong. It’s about reducing uncertainty.

Every meaningful decision begins with incomplete information. That’s unavoidable. The goal isn’t perfect certainty. The goal is making the next decision with more confidence than the last one. That’s how organizations improve.

At CAIP, some of the most valuable conversations happened after the work was delivered. The team compared expectations with reality. Some assumptions proved correct. Others didn’t. Neither result was a failure. Both produced learning. And that learning made the next decision better than the previous one.

Many organizations believe they’re making data-driven decisions.

What they’re often making are opinion-driven decisions supported by selective data. There’s a difference.

Evidence doesn’t guarantee the right answer. But it dramatically improves the quality of the conversation. And better conversations lead to better decisions.

The goal isn’t to win arguments.

The goal is to better understand reality. Because reality has a way of settling every debate eventually. Evidence just helps us get there sooner.

What decision has your organization made recently that would have benefited from better evidence? Reply or comment—I read every one.

CAIP is a program we follow throughout my book,

Read at the original source