STOP LEARNING THE TOOLS. START LEARNING THE JUDGEMENT.
- Jul 29
- 5 min read
Week 12 · Blog Post 21 · Web 2.0-Based Learning and Performance · Summer 2026
THE ADVICE I GAVE WAS THE BORING HALF
A while back I wrote a post that, stripped down, said: get comfortable with the AI tools. Learn them, poke at them, put them in your workflow before someone else puts them in your job description. I still think that's true. I've also been quietly annoyed with myself about it ever since I read TalentLMS's 2026 L&D report, because it was the least interesting half of the advice and I handed it over like it was the whole thing. Here's what caught me. In 2025, 42% of HR managers said their organization was dealing with a skills gap, down nine points from 2022 (TalentLMS, 2026). Progress, surely. Except the report reads its own number correctly: the gap is shifting, not shrinking. Employers have made real headway on technical literacy. What's deepening is the shortage in strategic thinking, leadership, and adaptability. Which means the take-twelve-AI-courses advice — mine very much included — is training people for the gap that's already closing.
THE WAGE PREMIUM IS REAL. IT'S ALSO A TRAP.
I want to be fair to the tools-first argument, because the money backs it. Lightcast analyzed over 1.3 billion job postings and found that listings requiring AI skills pay 28% more — roughly $18,000 a year (Lightcast, 2025). PwC's 2026 barometer puts the premium higher still at 62%, up from 57% the year before, with AI-skill postings growing 69% against 9% for the market overall (PwC, 2026).
So learn the tools. Obviously. That was never the argument. The argument is what PwC found when it looked at 2.4 million US entry-level jobs.
Entry-level roles most exposed to AI are now seven times more likely to demand traditionally senior skills — judgment, leadership, face-to-face work.
Those roles grew 35% since 2019. Every other entry-level role shrank 10%. Read that twice. It's brutal, and nobody's saying it out loud between the hustle posts.
The rungs of the ladder where you used to develop judgment — the routine, repetitive, apprentice-y work — are the exact rungs AI is eating. The jobs that survive want the judgment on day one.
THE JOB TITLES CHANGED BEFORE THE ADVICE DID
Here's the part I can speak to directly. As a freelancer and contractor, I live in job boards — it isn't an occasional exercise, it's a standing appointment. And over the past year, the titles have drifted. Learning Architect. Learning Consultant. Learning Business Partner. Learning Strategist. Traditional instructional design postings are still out there. They're just no longer the whole board. So I stopped guessing and read nineteen of them properly. All nineteen — every single one — use consulting, partnering, or stakeholder language, and it lands in the opening lines, not the fine print. Eighty-nine percent name business outcomes or strategy. Fifty-eight percent name learning theory or methodology. Authoring tools? Twenty-six percent. One in four. And when a tool does show up, it's about halfway down the posting, well after the part about business impact.
The phrasing is what gets me. One Learning Architect role defines the job as "comfortable recommending solutions and making judgment calls without complete information." A Learning Partner posting wants "the credibility and judgment to shape how senior leaders think," and warns that "this is a role for someone who runs toward ambiguity, not away from it." A consulting role asked, verbatim, for "high-judgment owners."
Someone wrote high-judgment owners into a job posting. Not "Storyline proficiency." Judgment, listed as a hiring criterion, in plain English.
Indeed makes the same point by accident. It's hiring a Lead Learning Architect for AI enablement — a role that exists entirely to teach people AI — and lists six required competencies. "AI & Technology Fluency" is the sixth. Last. At number two sits "sound judgment about when to build directly vs. delegate."
Capital One handed me the detail I'll be thinking about all month. The posting is advertised as Principal Associate, Learning Experience Architect. Its own salary table calls the role "Learning Consultant," eight times. Same requisition, two titles, nobody bothered to reconcile them — which tells you these titles are doing positioning work, not describing distinct jobs.
Here's the honest complication, though. The tools didn't disappear; they got demoted. Capital One still wants Articulate 360, Camtasia, Snagit, and Captivate — at bullet four of six, underneath "translate complex business challenges," and above a basic qualification of a high school diploma. Meanwhile the contract role listing a dozen platforms pays forty to fifty dollars an hour, while the two postings that never name a product at all top out at $148,000 and $185,000.
Naming the tools is table stakes now. And it's priced like table stakes.
And the one listing that did mention AI buried it. "The ability to leverage AI-enabled tools" shows up as a subordinate clause inside a sentence about adult learning, instructional design, learning experience design, and performance improvement. AI is the modifier. The judgment is the noun.
OUR OWN FIELD SAID THIS FIRST AND NOBODY LISTENED
Instructional design has had the data sitting in plain sight for years, mostly ignored while everyone panic-bought authoring-tool courses. When Devlin Peck surveyed 101 ID hiring managers, 71.3% put "ability to apply ID theory and science" in their top three skills. Programming and coding? Six percent (Peck, 2023). And here's the line that should reorganize your week: 26.7% named applying ID theory as the skill most often lacking in the people they interview. The thing they want most is the thing they can't find.
Also, quietly, 65% of those hiring managers don't factor AI-tool familiarity into their decisions at all.
The portfolio data says the same thing in a different accent. Asked to rank six criteria, hiring managers put "ability to solve real-world problems with instructional design" first by a clear margin. One respondent said they look for the design statements — "the 'why' behind design decisions." Another put it more bluntly: "I want to know what design they did, rather than what they built." What you built is the tool. Why you built it that way is the judgment.
SO WHAT DOES JUDGEMENT LOOK LIKE ON A PAGE?
Credentials still open doors — Coursera's 2026 report found 94% of employers willing to pay higher starting salaries to micro-credential holders (Coursera, 2026). But a door isn't a room, and the Burning Glass Institute maintains an entire Credential Value Index precisely because plenty of them don't move the needle. What travels is documented reasoning. Mitchell and colleagues found ePortfolios worked when they were built against what employers actually said they wanted, not what programs assumed (Mitchell et al., 2021); NACE makes the same case, that the value isn't the artifact but the reflection attached to it (Rafanello-Bazar, 2026). Which is a fancy way of saying: stop stacking certificates and start writing down why you made the call you made. The constraint you designed around. The stakeholder you talked out of a forty-five-minute compliance module. And then, somewhere in the nineteen, I found this. A Learning Architect posting, describing the person it wants: "Externally, you are a trusted advisor who can turn complexity into clarity and articulate the rationale behind every design choice." Articulate the rationale behind every design choice. That isn't me being clever about portfolios. That's a company writing the advice into its own job description and waiting for someone to walk in who can actually do it. So I'll ask you what I've been asking myself. Look at what you've built this year: can you explain why any of it is shaped the way it is? And if someone asked you tomorrow, where would that explanation actually live?
Comments