I recently completed Anthropic's AI Fluency: Framework & Foundations course. A lot of the material wasn't new to me. I've been experimenting with AI tools since the early days and built my own resource directory because of it. But one thing genuinely stopped me.
Not the technology. The framework.
The course centers on human-AI collaboration rather than AI as a standalone tool, and that framing matters more than it sounds. There's a meaningful difference between knowing AI exists and knowing how to work with it in ways that are effective, efficient, ethical, and safe. Most organizations are still navigating that gap, and many don't realize how wide it is.
What stayed with me was the 4D framework: Delegation, Description, Discernment, and Diligence. The more I sat with it, the more I became convinced that this isn't just a useful mental model for individual contributors. It's a leadership issue. And it's one that most leadership conversations about AI are missing entirely.
The Question Most Organizations Aren't Asking
A lot of companies are treating AI like a standard technology rollout. Choose the platform. Buy the licenses. Encourage experimentation. Host a training session. Then hope people figure out the rest.
But effective AI collaboration isn't something people figure out through access alone. It requires a genuine shift in how work gets defined, how decisions get made, and where accountability sits. That shift has to be modeled from the top. If leadership doesn't understand how to work with AI thoughtfully, teams end up experimenting without guardrails and building habits without strategy behind them.
The question worth asking isn't whether your organization has access to AI. It's whether your leaders know how to lead in an environment where humans and AI are working together. That's a different question, and most places aren't asking it.
What the 4D Framework Actually Demands from Leaders
Delegation
In an AI context, delegation isn't just handing something off. It's knowing what should go to AI in the first place, what needs to stay human, and where oversight genuinely matters. A leader who can't think clearly about this will either underuse AI out of caution or overuse it in ways that create risk and erode quality across a team. Neither is a strategy. Both are symptoms of unclear thinking about where the boundaries belong.
Description
If people don't know how to frame a task clearly (defining the outcome, explaining the context, communicating what good looks like) the quality of the collaboration breaks down immediately. This isn't new to AI. Poorly defined work has always been a problem. AI just exposes it faster and at greater scale. Leaders who are vague about what they want have always created downstream confusion. Now that confusion gets multiplied through every AI-assisted output the team produces.
Discernment
This may be the most important and most underestimated leadership skill in an AI-enabled environment. Speed is not the same as accuracy. Volume is not the same as quality. Someone still has to evaluate the output, notice what's missing, question what feels off, and decide what should and shouldn't be trusted. In many organizations, this is exactly where risk accumulates quietly. People assume that because something was generated quickly it's ready to act on. That assumption is where things go wrong.
Diligence
Not the most exciting of the four, but in some ways the most consequential. Diligence is the layer of care, review, and ethical consistency that keeps AI use grounded in responsibility. It's what prevents teams from drifting into lazy shortcuts, overconfidence in unverified outputs, or a gradual erosion of the standards that good work requires. It doesn't happen automatically. It has to be expected, modeled, and reinforced by leadership.
Why the Conversation Is Still Too Shallow
There's plenty of organizational enthusiasm about what AI can do. There's not nearly enough attention on what it requires from the people leading teams that use it.
The four areas above aren't technical skills. They're cognitive and operational ones. They're about how work gets defined, how judgment gets applied, and how accountability gets maintained in an environment that's changing faster than most management frameworks can keep up with. That's precisely what makes them a leadership issue rather than an IT one.
Organizations that get this right won't necessarily be the ones with the most sophisticated tools or the most aggressive adoption timelines. They'll be the ones where leadership understands the human side of the collaboration well enough to build teams that use AI effectively, consistently, and responsibly.
What Real Fluency Looks Like
Technology will keep changing. Tools will evolve. New models will arrive, and workflows that look settled today will shift again. That pace isn't slowing down.
What holds up through all of it isn't familiarity with any particular platform. It's the underlying capacity to delegate thoughtfully, describe clearly, discern wisely, and apply diligence consistently. Those skills travel. They work regardless of which tool is in front of you, and they compound over time in ways that tool knowledge doesn't.
That's what real fluency looks like. And for any organization serious about AI, developing it in leadership isn't optional. It's the foundation everything else is built on.
Want more practical approaches to AI in the workplace? Explore my curated library of tools, prompts, and workflows at resources.taneilcurrie.com