How to Measure AI Fluency on Your Team: The 5-Milestone Framework

Every business leader wants their team to be better at AI. But very few can answer the follow-up question: better how, exactly?

That gap between wanting AI adoption and actually measuring it, is exactly what Alane Boyd and Micah Johnson tackle in Episode 106 of the Automate Your Agency podcast. After Micah attended a COO conference where the topic of AI fluency dominated the room but nobody had a framework for it, the two hosts sat down to build one themselves.

The result is a five-milestone model for tracking individual AI progress, a clear, sequential ladder that gives business leaders a real answer to the question: where does my team actually stand?

Why AI Fluency Is a Business Problem, Not a Personal One

Before diving into the milestones, Alane makes a point worth sitting with:

"If half my team is doing something in five minutes and the other half is doing the same thing worse for hours, why the hell would I pay for that?"

The issue isn't whether people like using AI. The issue is that without defined milestones, business owners have no way to set expectations, measure progress, or build an operation that runs efficiently. Undefined fluency goals aren't just unhelpful, they're a silent drain on productivity and payroll.

Setting a clear baseline, the hosts argue, is the single most important step most businesses haven't taken yet.

The 5 Individual AI Fluency Milestones

Milestone 1: Basic Cowork Usage

The very first milestone has nothing to do with automation, agents, or advanced AI tools. It's simply this: can someone on your team open Cowork and use it to do their actual job faster?

No Skills. No Connectors. No folder architecture. Just the basics, help me draft this document, help me build this spreadsheet, help me get through this task I'd otherwise do manually.

That's it. And according to Alane and Micah, even this baseline already shows meaningful efficiency at the individual level.

Milestone 2: Skills, Folders & Connectors

Milestone two is where the real foundation gets built. At this stage, team members understand what Skills and Connectors are, can navigate and use the Cowork folder system, and know how to route work through integrated platforms.

This is the milestone the hosts describe as the minimum bar for everyone on the team. Not optional. Not aspirational. This is how we work now.

The compounding value here is significant. Micah shares a real example: one team member spent five minutes building a Skill that saves 45 minutes on a daily task. Multiply that across a team, and the efficiency gains become impossible to ignore.

Milestone 3: Building Basic Skills and Memory Workflows

At milestone three, team members move from using Skills to creating them. They can identify repetitive workflows, translate them into basic Skills, and understand how to leverage the folder system to create memory, saving progress between sessions so work can be resumed and built upon over time.

This is where the difficulty curve starts to steepen. The jump from milestone two to three is where Alane and Micah note many people slow down, and that's completely normal.

Milestone 4: Human-in-the-Loop Micro App Design

Milestone four is where strategic thinking becomes essential. At this level, team members aren't just building Skills, they're designing them. They understand when to stay in the LLM, when to push logic into Python code to save tokens, and how to build in human approval checkpoints so the AI does the heavy lifting at the start and end, while a person reviews and approves the output in the middle.

As Micah explains it: "AI executes the first part, comes back to the human with output, the human approves or adjusts, and then AI handles the rest." This mirrors how a well-run human team operates, and it's a powerful framework for responsible AI delegation.

Milestone 5: Full System Architecture

The final milestone on the individual track is reserved for the builders. At this level, someone can look across a business operation and identify which pieces should be Cowork Skills, which should be n8n workflows, and how to stitch them together with APIs, webhooks, and database connections,. with AI helping to build all of it.

Importantly, Alane and Micah are clear: not everyone needs to reach milestone five. And expecting your whole team to get there is a setup for disappointment. What matters is knowing who can reach it, giving those people room to build, and not letting the pursuit of milestone five delay the returns that come from milestones one and two.

The Strategic Insight: Start Small, Win Fast

One of the most counterintuitive points in this episode is about where to focus first.

Most businesses, when they get excited about AI, want to solve the big problems, the expensive workflows, the complex bottlenecks, the high-visibility wins. Micah's take: you're not ready for those yet, and chasing them before your team has the foundation will slow everything down.

"Get people to milestone one and two. Your returns are going to be so much quicker and so much bigger. And then the big problems start to identify themselves — and they'll be a lot clearer to solve."

This is the paradox of AI adoption: the fastest path to big results is to start as small as possible.

What Comes Next

Episode 106 covers only half the picture, the individual track. In Episode 107, Alane and Micah will walk through the organizational milestones: the systems, structures, and foundations a company needs to build in parallel with individual fluency development.

Both tracks matter. And as the hosts explain, you won't see the full payoff of one without building the other.

Listen to EP 106 of Automate Your Agency

If you're a business owner or team leader trying to figure out where your people actually stand with AI, and what to do about it, this episode is a must-listen.

And if you found this useful, a five-star review goes a long way. New episodes drop every week.

‍

Most business leaders talk about AI adoption, but Alane Boyd and Micah Johnson are asking a sharper question: how do you actually measure it? In this episode, they introduce a concrete five-milestone framework for tracking individual AI fluency on your team, built from a real gap they identified at a recent COO conference where everyone agreed the topic mattered but nobody had answers.

If AI adoption at your company feels more like chaos than progress, there's a good chance your team has no shared baseline — and no way to know who's moving forward and who's stuck. Alane and Micah make the case that undefined fluency goals are a business problem, not a personal one, and that the fix is simpler than most leaders think.

In this episode, you'll learn:

• How to define milestone one so every team member has a clear, achievable starting point with Cowork
• Why Skills, Folders, and Connectors mark the jump to milestone two, and why that baseline alone drives major efficiency gains
• What human-in-the-loop design looks like when someone reaches milestone four and starts building AI workflows with built-in approval checkpoints
• Why milestone five isn't for everyone — and how chasing it too early can actually slow down your results
• How one team member spent 5 minutes building a Skill that now saves 45 minutes every single day
• The two-track model — individual vs. organizational, and why both need to be measured to see real AI success

If you're ready to stop guessing about where your team stands with AI and start building a measurable path forward, this episode gives you the exact framework to do it, press play now.