The Ceiling You've Put on Yourself Isn't Real Anymore

AI hasn't just changed what tools we use. It has changed what any individual can credibly attempt.

There is a sentence you have said to yourself — maybe recently, maybe so many times it has become fact — that goes something like this:

"That's not my domain."

It might sound like: "I'm not technical enough for that." Or: "I'm in delivery, not strategy." Or: "I only do X, not Y." The specific words vary. The function is the same. It is a line you drew around your competence — rational at the time, based on real experience, probably accurate for a long while.

Here is what has changed: the line is no longer where you drew it.

"The only bottleneck left is intention."

That is not a motivational claim. It is a structural one. And the evidence for it is showing up in the most unlikely places — including in the commit history of a CEO who had not written production code in years.

What Actually Happened

Ankur Gupta, CEO of Axelerant, started writing code on a live client engineering project. Not as a learning exercise. Not as a proof-of-concept demo. As a real contribution, on a real codebase, on a real delivery timeline.

His own framing of it was direct: "If you told me a year ago I'd be doing that, I'd have laughed. That wasn't my thing. I'm a CEO — I do strategy, I think about the business."

What changed was not a sudden rediscovery of technical skill. What changed was the distance between intent and execution. That distance — the long stretch of trial, error, documentation-reading, waiting for the right person, and second-guessing whether you know enough to even start — compressed dramatically.

Not to zero. But from months to days. From weeks to hours. From "I'd need to hire someone" to "I can investigate this myself."

The ceiling he had placed on himself — "I'm not technical enough anymore to do that" — turned out to be a product of that distance. Remove the distance, and the ceiling goes with it.

The Ceilings Worth Examining

This is not a story about one CEO. It is a pattern showing up across every function, at every level, in every organisation moving seriously with AI.

The developer who decided years ago that strategy was someone else's job. The delivery lead who assumed sales conversations were out of scope. The designer who never felt confident enough to prototype the interaction behaviour, only the visual. The engineer who knew one stack deeply and quietly wrote off everything adjacent to it.

These were not failures of ambition. They were rational adaptations to a world where domain specialisation had a real cost-benefit logic. Crossing lines took time. Getting it wrong was expensive. The specialists were faster, better, and available.

That logic has not disappeared. But its parameters have shifted significantly.

The question is no longer whether you have the accumulated expertise to contribute to something outside your primary domain. The question is whether you have the judgment to direct capable tools, the clarity to describe what you want, and the discernment to evaluate what comes back.

Those are things most senior people already have in abundance. They just have not been applied this way before.

"The barriers that used to take years to overcome can now be compressed into weeks or days."

What This Means for How You Lead

If you are a leader watching your organisation navigate an AI transition, the Ankur story is worth taking seriously — not as inspiration, but as signal.

When the CEO starts doing work that was previously categorised as someone else's, it creates structural permission for everyone else to renegotiate their own categories. The developer sees that strategy is not off-limits. The delivery lead sees that commercial thinking is accessible. The engineer sees that adjacent stacks are learnable, faster than they thought.

This is not about dissolving specialisation. Deep expertise still matters — probably more than ever, because the judgment layer is now the scarce resource, not the execution layer. What is dissolving is the fixed boundary between domains. The walls are becoming permeable.

The organisations that move fastest in this environment will not be the ones with the most AI tools. They will be the ones where the most people have stopped asking "is this my area?" and started asking "what is actually stopping me from contributing here?"

The Question Worth Asking

There is a line worth sitting with — one that came directly from reflecting on this shift:

"Stop putting arbitrary ceilings on yourselves."

"I'm a developer, I can't do strategy." "I'm in delivery, I can't do sales." "I don't know enough about X to contribute to Y." "I only do Drupal and not this other stack."

Those limits were real once. They are not as real now. The tools have changed the geometry of what is accessible.

The question worth asking — for yourself, and for every person on your team — is a simple one:

What is the thing you have been telling yourself you cannot do?

And what if you just started?