AI Impact = Fluency × Flow × Fit

Many organizations right now are focused on getting individuals up to speed with AI — fluent with Copilot, prompts, agents, slash commands. For most of us, these tools are new, and we all need some help building fluency with them every day.

But to achieve organization-wide impact with AI, individual fluency usually is not enough.

AI Impact = Fluency × Flow × Fit.

Let me explain:

Fluency is personal: can you actually put AI to work in your own job, end to end? It's the layer everyone's on right now — and almost the whole training budget goes here.

Flow is about the system: can the work you produce reach 'done' without a human becoming the bottleneck? This is the layer of pipelines, reviews, tests, and handoffs — the path your work has to travel once you've made it. When it's weak, AI writes the code in minutes, then waits for hours or days in someone's review queue. Flow isn't a skill you can teach a person — it's a path you have to redesign for.

Fit is the match between the organization's shape and the value it's meant to produce. Does its structure allow work to flow into real outcomes, and do people's jobs, as they are defined, aim at what the customer needs? When the shape fits the work, local speed turns into organizational performance. When it doesn't, you just make the wrong thing faster.

To make it simple: fluency is person-to-tool, flow is system-to-work, fit is organization-to-value.

AI Impact = Fluency × Flow × Fit.

That × is the whole point. Multiplication, not addition, so the weakest factor sets the ceiling, not your strongest. (I've mapped the same three layers as nested loops in The Value Factory.)

Most of my client work starts at Fluency, then we move on to Flow and Fit — because that's where the real leverage lies, where individual speed either becomes organizational performance or quietly disappears.

So which of your three is lowest right now — and what's it capping?