Chat is not fluency.

Walk into almost any firm today and you'll find the same thing: every leader has access to the most capable AI ever built, and almost none of them are getting real leverage out of it. The licences are paid. The keynotes have been watched. And yet the executive's week looks exactly as it did two years ago.

The instinct is to assume this is a tooling problem, or a training problem — that the right course or the right app will close the gap. It won't. The gap is not access. It is fluency.

Three states, not one

There is a progression that separates a casual user from a genuine force multiplier, and it has three states.

The first is chat. One question in, one answer out. It is reactive, it is unrepeatable, and it is where the overwhelming majority of senior people live. They open the tool, ask it something, copy the answer, and close the tab. Useful, occasionally. Transformative, never.

The second is workflows. This is where it begins to pay. Instead of asking the same kind of question over and over, the leader has repeatable structures — projects, custom skills, scheduled tasks — that do the recurring work for them. The output stops depending on remembering the right prompt. The work starts to run itself.

The third is agents. Here the work compounds. Agent-assisted processes operate across connected systems, handling multi-step tasks that used to require a person at every step. One leader starts producing the output of a team — not because they're working more, but because the system is.

Why the leap doesn't happen on its own

Almost nobody crosses from chat to workflows to agents alone. Not because senior people aren't capable — they are some of the most capable people in any organisation — but because the leap isn't an information problem. You cannot read your way across it. It requires building the new way of working on the real work, and most executives have neither the time nor the technical depth to do that for themselves.

This is exactly why the standard playbook fails. A cohort ends. A deck gets filed. A subscription renews, unused. None of those things build the workflows, and so within two weeks the leader is back in the chat window, asking one question at a time.

What actually closes the gap

What closes the gap is having someone capable sit beside the executive and build the workflows with them — on their actual responsibilities — and stay until the new way of working holds on its own. Not a trainer talking about AI. An operator building it, in the leader's real week.

That is the entire premise of how we work. The measure of success isn't whether someone learned about AI. It's whether they became fluent in it — and you can see that in only one place: their calendar-week.