Ann Handley: AI Literacy Is Judgment Literacy, Not Prompt Skills

Ann Handley, a Wall Street Journal bestselling author and one of marketing’s most respected voices, recently posted something on LinkedIn that stopped me cold. She asked a question the entire AI training industry seems to be ignoring: “Why do we keep teaching people how to use AI – without ever teaching them when not to?”

I reached out to her immediately. Where, I wondered, could someone actually learn that skill? Her honest answer was telling: “I don’t know of a course that teaches exclusively this.” At MarketingProfs, she explained, their AI sessions might include a few slides on avoiding hallucinations, but a whole session or series dedicated to restraint simply doesn’t exist. She added that this gap is the real story: “We have an entire industry built around AI skills training – prompt engineering bootcamps, certification programs, tools tutorials… What we don’t have is anything that asks: when should you put the tool down?”

That gap is profound, and it matters far more than the AI training industry currently acknowledges.

Prompt literacy is teachable in an afternoon. You learn the syntax, the structure, the iterative refinement loop. It’s genuinely useful and quickly learnable. Judgment literacy is something else entirely. It’s knowing when the speed of AI output erodes something you needed to build slowly. It’s recognizing when the struggle itself is the point. As Ann put it, it’s understanding “when AI helps and when it shortcuts the very struggle that teaches us something.” One commenter on her post nailed it: “Prompt literacy is teachable in an afternoon and judgment literacy takes years, because judgment is mostly knowing the value of the struggle you’d be skipping.”

I have spent months analyzing the AI training landscape. The pattern is consistent. Courses teach you what tools can do. The better ones teach you how to deploy them strategically. Almost none of them teach you when to put them down. This is not a minor curriculum gap. It is the central question of our current moment.

The industry has a structural incentive problem. Courses that teach tool use generate demand for more tools and more certifications. There is no business model for teaching restraint. But the cost of skipping the judgment question is real and measurable. Anthropic’s own research found that junior engineers who leaned heavily on AI coding agents demonstrated weaker understanding of their work afterward. The output and the expertise are not the same thing.

For SEO professionals and content marketers, the exposure is direct. MIT’s AI Labor Exposure Map found that nearly three-quarters of a marketing specialist’s work time goes to tasks AI can already handle. The question is not whether to use AI for those tasks. The question is which tasks in that 74% are the ones where the doing is the learning, where outsourcing the execution also outsources the understanding you needed to build.

When I asked Ann where practitioners should develop this judgment, she reframed the question. “Do we actually need a course? What we need instead is permission and better modeling. Leaders who visibly choose the long road. Managers who say out loud when they are not going to use AI for certain things, and here’s why. Said another way: culture not coursework.”

That reframe is worth sitting with. The judgment about when not to use AI is a professional norm transmitted through observation, not a certificate program. Ann has a book coming out in February 2027 called “ASAP (As Slow As Possible): When to Take the Long Road in a Shortcut World.” The title captures the tension precisely. Choosing slowness requires not just judgment but courage.

While that culture is still forming, practitioners need something concrete. Consider a workflow I tested with the editorial team at The Acton Exchange, a nonprofit community newspaper in Massachusetts. Facing a deadline on a complex school district reorganization question, the team crafted a detailed prompt and uploaded 156 pages of materials to four AI engines simultaneously: ChatGPT, Gemini, Perplexity, and NotebookLM. Each took a different route. We reviewed all four drafts together, chose Perplexity’s as the most accurate foundation, and then did what no AI engine could: we added direct quotes from people who were in the room.

Town Manager John Mangiaratti had observed earlier that the tools were helpful for the first 75% of content, but that “the remaining 25% of details, nuance, and context are either missing or incorrect.” That 75/25 split is a practical frame. Use AI to get 75% of the way there quickly. Then apply human expertise, primary source verification, and direct observation to close the gap. The 25% that requires a human is not a bug in the workflow. It is where the judgment lives.

Before adopting any AI tool, have an explicit conversation with your editor about which tasks the AI will handle and which require human oversight. Document your prompt. Run the same prompt through more than one engine when the stakes are high. Verify outputs against primary sources. And disclose your process to your audience.

Ann Handley is right. The real skill is judgment: knowing when speed is useful and when it erodes something you needed to build. Prompt literacy gets you to 75%. Judgment literacy is what closes the rest.