Part of my role involves helping roll out AI tools to product marketing teams, and over the past year I've noticed a pattern that I think explains why so many AI enablement efforts plateau. The conversation in most organizations has become entirely about consumption—token usage, cost per query, utilization dashboards with red and green zones—when it should be about capability. We're measuring how much AI people are using without asking whether the work is actually getting better.

What I keep seeing is that tool access is essentially universal at this point, with everyone having some combination of Copilot, ChatGPT, or Claude at their disposal, but actual capability follows a much more uneven distribution. A relatively small percentage of marketers are using AI to genuinely elevate their strategic work, while the majority are using it as a faster way to produce outputs that aren't meaningfully different from what they would have created before—just more of them, and quicker.

The marketers who break through this plateau share something in common, and it has almost nothing to do with their prompting technique or their comfort with the tools. What distinguishes them is that they have strong foundations in the underlying craft—they understand positioning frameworks deeply enough to know when the AI's suggestions are off-target, they can identify weak messaging without needing someone else to point it out, and they have a clear mental model for what good work looks like that allows them to evaluate AI outputs with real discernment. When these people collaborate with AI, the output sounds like them, carries their perspective, and reflects genuine strategic thinking rather than a kind of averaged synthesis of everything the model was trained on.

"Are you outsourcing to AI, or co-authoring with it? That's the question that determines whether you're building capability or just building dependency."

That observation has become a working thesis for me. AI amplifies whatever capability you bring to it. If you have strong foundations, AI becomes a genuine thought partner that helps you explore more alternatives, pressure-test your assumptions, and refine your thinking faster than you could alone. If your foundations are shaky, AI becomes a way to produce plausible-sounding work that you can't actually evaluate—and you may not even recognize the gap between what looks good and what actually is good.

Two Kinds of Assessment

This is what led us to build assessment into the center of an AI curriculum we've been developing, and to think carefully about what we're actually testing for. We use two distinct types of assessment, and each one reveals something different about where people are and what they need.

The first is a baseline assessment of how teams are actually using AI today across the core domains of product marketing work—content development, competitive intelligence, and corporate marketing. We want to understand where people are starting from: Are they using AI primarily to check their work and catch errors? To generate first drafts they then heavily edit? To brainstorm ideas they wouldn't have thought of on their own? The baseline gives us a clear picture of current practice, which is essential for measuring growth over time.

What we typically find is a wide gap between where most people are and where they could be. The majority start somewhere around "having AI review my drafts" or "using AI to generate bullet points I then rewrite." The destination we're aiming for is something more like "co-authoring GEO-optimized positioning statements" or "building competitive narratives that synthesize market intelligence in real time." That's a meaningful journey, and you can't navigate it without knowing your starting point. The baseline assessment creates that honest self-awareness, and it also helps people see concretely what more sophisticated AI collaboration actually looks like.

The second assessment is what we call the cognitive assessment, and it focuses on how people actually think and collaborate with AI. This is where we explore the difference between delegation and co-authorship—between treating AI as a task-completion machine and treating it as a genuine thinking partner.

Most people start on the delegation side of that spectrum. They prompt AI to "write me a positioning statement" or "draft a competitive overview" and then accept or lightly edit whatever comes back. The co-author model is fundamentally different: you bring your own hypothesis to the conversation, you ask the AI to challenge your assumptions, you generate multiple alternatives and evaluate them against criteria you can articulate, and you treat the first draft as the beginning of a dialogue rather than the end of a task. The cognitive assessment helps people see where they fall on this spectrum, and in my experience that moment of recognition—realizing that there's a different way to work with these tools—is often what creates genuine interest in developing new capabilities. People get curious once they understand there's something more to learn.

Where Do You Sit?

The cognitive assessment we use is adapted from Helen Edwards' research at the Artificiality Institute, which studied how over 1,200 professionals integrate AI into their cognitive work. What Edwards found—and what we've seen play out in our own cohorts—is that the relationship between AI depth and professional capability isn't what most people assume.

The framework maps people across three dimensions: whether AI has entered your actual reasoning process (not just your workflow), whether your professional identity has reorganized around AI, and whether your definitions of what good work looks like are evolving. Those three dimensions produce distinct integration patterns, and the results are counterintuitive.

The Doer uses AI as an execution layer—queries it, reviews the output, takes what's useful, moves on—but keeps strategic reasoning firmly in their own head. There's nothing wrong with this posture, and many highly effective professionals operate here deliberately. But the question worth asking is whether you're keeping AI outside your reasoning because you've made a conscious choice, or because you haven't yet discovered what happens when you let it in.

The Partner is the pattern that best describes what we're aiming for with this curriculum. Partners let AI into their thinking and let it change what they think good work looks like—but their professional identity holds steady. This is the advanced practitioner: someone who brainstorms positioning in dialogue with AI, discovers that competitive analysis can be more dynamic than they ever imagined, rethinks what a launch plan should even contain—and still knows exactly who they are. The Partner has expanded their capability dramatically through AI collaboration without losing the judgment, taste, and strategic sense that makes them valuable.

The Co-Author goes even further. Everything is in play: AI is inside the reasoning, professional identity has reorganized, meanings are actively evolving. And here's the paradox that anchors the entire Edwards research—Co-Authors are also the most sovereign. The act of actively shaping deep AI collaboration requires so much awareness, agency, and accountability that it builds the very cognitive muscles it seems like it should erode. These are the people with the strongest grip on who they are precisely because they've engaged most deeply.

The pattern that should worry you is the Outsourcer. Outsourcers have let their professional identity reorganize around AI, but they haven't actually let AI into their reasoning process, and their definitions of success haven't evolved either. This is a red flag: the identity shift happened externally—job market pressure, org restructuring, the sense that you need to be "AI-native" to stay relevant—rather than through deliberate cognitive engagement. For a product marketer, this might look like someone who's rebranded themselves as an AI-native marketer while still using AI as a glorified text generator. They've adopted the label without doing the work, and that's where sovereignty erodes.

What makes this framework valuable is the clarity it brings to a confusing landscape. Most people assume that deeper AI integration means more risk to their professional identity and judgment. The research shows the opposite: depth of engagement isn't the risk. Passive identity coupling without cognitive engagement is. The people who've gone furthest in integrating AI into their cognitive processes aren't the ones losing themselves—they're the ones who know most clearly who they are.

Creating Safe Spaces to Learn

One thing we've learned is that the learning environment matters enormously. People are reluctant to experiment with AI when every prompt costs money, gets logged somewhere, and might be used in their deliverables before they've had a chance to develop real fluency. They play it safe, accept the first reasonable output, and never build the muscle memory for pushing back, iterating, and genuinely collaborating.

This is why we built what we call AI Labs—hands-on exercises where people can work through real marketing problems with AI as a collaborator, but in a designed environment where they're not burning through tokens, not producing anything that will be evaluated, and not afraid to make mistakes. The labs create a space where you can try prompting approaches that might not work, see what happens when you push back on the AI's first suggestion, and build intuition for the back-and-forth of real collaboration without any stakes attached.

This turns out to matter more than I expected. When people feel safe to experiment, they learn faster and develop more sophisticated mental models for how to work with AI effectively. They start to internalize the patterns—when to accept, when to push back, when to reframe the question entirely—in a way that transfers to their real work. By the time they're applying these skills to deliverables that matter, the fundamentals are already in muscle memory.

What's Actually Working

I want to be clear about something: this approach is working. The people who engage seriously with the curriculum come out different, and the difference shows up in their outputs. They produce work that has a point of view, that reflects genuine strategic thinking, and that sounds like it came from a human with something to say rather than from a sophisticated autocomplete. They also report feeling more confident—not because they've learned tricks for getting better outputs from AI, but because they've strengthened their own foundations and can now collaborate with AI from a position of expertise rather than dependence.

What strikes me most, though, is how much people want this kind of development. There's been remarkably little resistance to the idea that foundational skills matter, or that assessment is a valuable part of the learning process. If anything, people seem relieved to be offered something more substantial than another prompt-engineering cheat sheet or lunch-and-learn about the art of the possible. They want to get better at their craft. They want to be genuinely capable, not just more productive. They want to be valued for their judgment and strategic thinking, not just for their ability to generate more outputs with better tools.

That's the human premium, and I think it's what this moment actually calls for. The companies that invest in building real capability—not just distributing licenses and tracking consumption—will develop an advantage that compounds over time. Better people using AI become more effective, which frees them to learn more, which makes them better at using AI. But you have to kick-start that flywheel with genuine investment in human development, not just technology procurement.

Here's what I've come to believe: yes, tokens are getting cheaper, but the lack of guidance, education, and governance around AI is costing companies real money. People are spending hours producing work that doesn't meet the bar, or accepting outputs they can't properly evaluate, or reinventing wheels that a structured curriculum could have handed them on day one. The waste isn't in the API costs—it's in the human time and organizational capability that's being squandered without proper investment in development.

That's what this curriculum is designed to stop. It gives people a clear baseline, shows them what co-authorship actually looks like, creates safe spaces to build the skills, and moves them deliberately from wherever they are toward genuine fluency. The human premium is real, and it's finally possible to invest in it systematically.