The One Idea Behind Everything I Write: Why Confidence Is Not Evidence

I've published a lot of pieces this year.

Saudi Arabia's hotel supply against its tourism target. Dubai's airport, and the three separate dates it's been given. Qatar's post-World Cup occupancy collapse and its recovery. AI adoption claims in procurement, and the enormous gap between what's claimed and what's actually running in production. Read individually, they look like different subjects, infrastructure, technology, tourism, negotiation. They aren't. They're one argument, worn differently each time, and I've never actually said that plainly until now.

Here it is, plainly: a confident claim and a verified one are not the same fact, and the distance between them is where almost all real risk hides.

I didn't arrive at that as a business insight. I arrived at it in a minefield.

Where It Actually Started

In 2004, I spent a year in Burundi as a UN munitions inspector, leading a team clearing explosive ordnance across three sites. In that work, there is no room for a comfortable assumption. A device that looks familiar, a report that sounds confident, a colleague's certainty, none of it is evidence. Only physical verification is evidence. You confirm, specifically, every time, no matter how routine it feels, because the cost of trusting an unverified claim in that environment isn't a bad quarter. It's a casualty.

I didn't expect that discipline to still be running my career two decades later, in warehouses and spend sheets instead of minefields. But it never really stopped.

Where It Resurfaced, Without Me Naming It

At a warehouse in Karachi, I inherited a system reporting confident inventory numbers. The shelf told a different story, 67 percent accuracy behind what the system claimed. Closing that gap wasn't a technology project. It was one unglamorous rule: a pick didn't count as complete until a scan physically confirmed it matched the order and the location. Accuracy rose to 98 percent, not because anyone got smarter, but because the system stopped accepting a claim it hadn't checked.

At DHA Islamabad, I found a $54 million spend base running entirely on trusted relationships, no competitive tender, no verification that any given price was actually fair. Building tendering, supplier scorecards, and a spend-variance review from zero recovered $5.4 million within a year, not through harder negotiation, but by refusing to let an unchecked number stand in for a fact.

Neither of those projects was framed, at the time, as an application of anything I'd learned in Burundi. It's only in hindsight that I can see it was the same rule, applied to a completely different kind of risk.

Where It Lives Now

This year, I started applying that same instinct somewhere new: to public claims. When Saudi Arabia states a 150 million visitor target, the interesting question isn't whether the ambition is real. It's whether the hotel pipeline and the giga-project contract awards actually support it, checked against public data, not the announcement.

When Dubai's flagship airport has had three different completion dates across a decade, the question isn't whether Dubai's tourism story is credible. It's which specific claim inside that story has been verified, and which one is still just a confident date. When a survey says 100 percent of procurement leaders use AI, and independent research finds only 5 percent ever reached real deployment, the interesting fact isn't the technology. It's the size of the gap between what's claimed and what's been checked.

Different subjects. Same question, every time: what here is actually verified, and what am I just agreeing to because it sounds confident.

Why This Isn't Really About Skepticism

I want to be precise about what this instinct is not. It isn't cynicism, doubting everything by default is just as lazy as trusting everything by default, both let you skip the actual work of checking. It isn't caution for its own sake either, some of the pieces I've written this year found genuine, verified good news, Qatar's real recovery, Dubai's real tourism growth, real achievements in Saudi's own KPI tracking. The instinct isn't to expect the worst. It's to refuse the shortcut of assuming, in either direction, before something's actually been confirmed.

That distinction matters, because the discipline only has value if it's applied evenly. A verification habit that only ever looks for problems isn't verification. It's a different kind of bias wearing the same clothes.

What This Means for Reading Anything Else Here

If there's a single lens for reading everything else on this site, this is it. Not "trust nothing." Not "doubt everything." Just one honest question, asked consistently, about numbers, targets, technologies, and claims that are easy to repeat and expensive to get wrong: has this actually been checked, or does it just sound like it has.

That question first mattered to me with a device in my hands in Burundi. It still does, now, with a spreadsheet or a press release in front of me instead.

And I don't expect that to change.