Hearing an airline CEO talk about crisis leadership, one phrase stopped me cold:
"Outcomes never lie."
Admitting when you're not hitting the mark, taking responsibility, then systematically fixing it — these were the principles at the heart of the talk.
"See it, own it, change it."
This concept hit me because it's exactly what's missing in many enterprise technology initiatives.
I see this pattern repeatedly: organizations measure technology implementation but struggle to connect those investments to business outcomes. They can tell you about data lakes deployed, APIs integrated and data scientists hired. But when you ask about revenue impact, customer satisfaction improvements or operational efficiency gains, the conversation gets murky.
Over time, this pattern drives more and more distance between business and technology teams. IT tracks projects delivered. The business tracks results achieved. Neither is looking at the same scoreboard.
The cycle can be broken. But it takes people, not technology.
The most successful data transformations I've witnessed — ones delivering 3x ROI in under 12 months — started with someone finally saying: "Our data quality isn't where it needs to be, our teams don't fully trust the numbers, and we're making too many decisions based on gut feeling."
That kind of vulnerability unlocks everything. Once it's safe to name the problem, teams stop chasing the next platform and focus on the fundamentals. They define shared metrics everyone can trust. They create feedback loops between the people building systems and the people using them. They start measuring what the business actually cares about instead of what the technology makes easy to count.
At one organization, this shift — from measuring technical delivery to measuring business outcomes — cut project approval time by 65% while tripling ROI on data investments. Not because the technology changed, but because the conversation changed.
The principle holds. Outcomes never lie.
Making data work for leaders means having the courage to recognize when technology isn't driving the results it should be, owning the gaps and changing the fundamentals to get back on track.
See it. Own it. Change it.