Seasons of Exceptions
If you were close to cloud technology fifteen years ago, you lived through several seasons of exceptions.
The cloud is less sustainable. The cloud has worse total cost of ownership. The cloud is less secure. The cloud cannot scale. Each of these was presented not as an opinion but as a finding, backed by papers and panels and the kind of certainty that comes from measuring the present and projecting it forward in a straight line.
And each of them had basis. They were rooted in decades of hard-won understanding about how infrastructure worked: how it was priced, how it was deployed, how it was secured, how it scaled. That understanding was not wrong. It was the product of experience, and the people who held it were acting in good faith. But it assumed constraints that belonged to the old model. On-premises infrastructure had physical boundaries, capacity ceilings, procurement cycles, and security perimeters that shaped how every CTO and CIO thought about what was possible. When cloud computing arrived, the evaluation happened through that existing lens. And through that lens, the exceptions looked like facts.
In the best cases, these were blind spots. We did not think about what elastic pricing would do to total cost of ownership once workloads were designed for it rather than migrated to it. We did not anticipate that cloud infrastructure would eventually enable security investments that no single organization could justify alone. In the worst cases, they were something more stubborn: things we knew for certain that turned out not to be true.
The exceptions were seasonal. They arrived with conviction, held the room for a while, and then quietly fell away as the technology matured, as operational models adapted, as the sheer weight of investment and iteration closed the gaps. Efficiency improved. Cost models sharpened. Security postures in the cloud surpassed what most organizations could achieve on their own. Scale became normal.
Today, nobody serious argues that the cloud is fundamentally less secure or less sustainable or worse on total cost of ownership. You can find pockets where it is true. Specific workloads, specific configurations, specific contexts where on-premises might be workable. But those are third and fourth standard deviation cases. The exceptions prove the rule precisely because they exist only at the edges.
Same pattern, different lens
The organizations who succeeded were not the ones who waited for every exception to be fully resolved. They were the ones who recognized the trajectory early enough to build for where it was going. The skeptical had defensible positions. The cynical had valid concerns. And the teams that moved anyway, not recklessly but with conviction, captured value that the wait-and-see crowd never recovered. By the time the exceptions were settled, the advantage had already been allocated.
We are now in that same moment with AI.
The current season of exceptions sounds familiar, but the exceptions come from a different place. With the cloud, objections were about infrastructure: cost, security, scale, sustainability. They were rooted in how we thought about machines and systems and operations. With AI, the objections are about intelligence itself. AI cannot be creative. AI cannot exercise judgment. AI cannot be empathetic. AI cannot be trusted. These are not claims about infrastructure. They are claims about capabilities we consider to be fundamentally, perhaps uniquely, human.
I am not someone who finds it helpful to anthropomorphize technology, particularly in an enterprise context. But I do not think you can understand what is happening with AI adoption unless you recognize that the lens through which we evaluate it is increasingly the same lens through which we evaluate each other. When someone says AI cannot be creative, they are not making a technical claim about token prediction. They are drawing a bright line around what they believe is innately human, and declaring that no machine will cross it.
This is a different kind of exception than \"the cloud is too expensive.\" It runs deeper. It feels more permanent. And that is precisely what makes it more dangerous to build strategy around.
Bright lines are fading
These bright lines follow the same pattern as the infrastructure exceptions, just from a more personal starting point. They are rooted in a lifetime of experience with the only intelligence we have ever known: our own and each other's. That understanding is not wrong. But it assumes constraints that belong to a particular kind of intelligence, and those constraints do not necessarily transfer to a new one.
The creativity objection assumes that recombination at scale cannot produce novelty. The judgment objection assumes that pattern recognition across thousands of cases cannot approximate contextual reasoning. The empathy objection assumes that a system which does not feel cannot meaningfully help someone who does. Each of these is a thing we know for sure. And the cost of being wrong is not that you tried something that failed. It is that you waited while others did not.
We are already watching the exceptions ease. AI systems are producing creative outputs that professional creatives find genuinely surprising, not because the AI understands what it is doing, but because the combinatorial space it explores is larger than what any individual could traverse alone. Businesses are using AI for judgment calls in underwriting, in triage, in strategic scenario planning, not because the AI replaces human judgment but because it introduces a consistency and breadth that human judgment alone cannot sustain at scale. Mental health support is the fastest growing use case for AI assistants in the consumer world, which tells you something about empathy that is worth sitting with: millions of people are choosing to talk to AI about their most personal struggles, and reporting that they feel heard. You can debate whether that is empathy. You cannot ignore that millions of people are finding value in it.
The trust story
The remaining exception is probably trust. But even that is shifting, and I want to tell you a story about how.
A year ago, I attended an industry event. The AI keynote was whimsical. It was a look at the funny robot falling over, a curated reel of AI getting things charmingly wrong. The audience laughed. The implicit message was clear: this is interesting, this is entertaining, this is not yet something you would rely on for anything that matters.
This year, the same organization presented analysis produced by Claude. Not with an apology. With authority. The framing was not \"here is what an AI said, take it with a grain of salt.\" The framing was \"this analysis is worth reading because it came from AI.\" The provenance was the credential, not the caveat.
Now, you can argue that the first presentation was late. That it underplayed value that was already obvious, that it chose comedy when the audience needed clarity. And you can argue that the second presentation was early. That the CEO was too bullish, that AI still makes factual errors, that presenting AI-generated analysis with authority carries risk. Both of those criticisms have merit. But even at the extremes of those two positions, the change in trajectory is unmistakable. In twelve months, the default posture moved from amusement to reliance. From \"isn't that cute\" to \"we should pay attention to this.\"
That shift is not contained to your organization. Your clients' defaults are moving too. So are your competitors'. The organizations that move early on AI are not just improving their own operations. They are becoming the place where their clients' attention lands first. The organizations that wait are watching that attention move elsewhere.
Where trust goes, value follows
And where trust shifts, value follows. It always has. And as it did with cloud, that behavioral trust will formalize — in policy, in governance, in standards — long before every objection is resolved.
Trust in cloud security shifted, and the organizations that had already built cloud-native capabilities captured disproportionate value. Trust in mobile commerce shifted, and the companies that had already invested in mobile-first experiences pulled ahead. In both cases, the winners were not the ones who were right about every exception. They were the ones who were right about the direction, and who moved before the exceptions were fully settled.
The same window is open now. The bright lines that feel most permanent — creativity, judgment, empathy, trust — are easing on the same timeline the infrastructure objections did. The fact that they feel more personal, more fundamental, more tied to what it means to be human, does not make them more durable. If anything, it makes them harder to see clearly, because we are not evaluating a technology. We are evaluating a challenge to our assumptions about ourselves.
The seasons of exceptions are ending. Not all at once, and not uniformly. There will be pockets where the exceptions hold, specific domains, specific tasks, specific contexts where AI falls short in ways that matter. Those pockets will exist for years. They will be cited by people who need them to be true.
But the trajectory is clear. And the question is the same one it was with cloud, with mobile, with every platform shift that came before: are you building for the world where the exceptions still hold, or for the world where they no longer do? The skeptics were right about the details last time too. The shift happened anyway.