AI proficiency ladder

Casey51 Novice 1h ago 306 views 0 likes 2 min read

We rolled out an internal AI skills framework last quarter because leadership kept confusing "uses ChatGPT daily" with "actually productive with AI." The gap is massive, and nobody had a vocabulary to describe it.

Here's the ladder we settled on after three iterations:

L0 — New
Hasn't touched AI tools yet, or tried once and bounced off. Onboarding target.

L1 — Chat
Serial prompt-and-response. Ask, wait, read, ask again. Zero context carryover between turns. Most "power users" we interviewed plateau here.

L2 — Contextual Work
Feeds the model relevant docs, data, or workspace state so it operates inside the actual artifact. Not "summarize this PDF" but "here's our style guide, three past proposals, and the RFP — draft section 4." Output quality jumps visibly.

L3 — Orchestrate
Coordinates multiple agents or roles across independent workstreams. One agent researches, another drafts, a third critiques, a fourth formats. Non-engineers do this too — our marketing lead runs a four-agent pipeline for campaign briefs.

L4 — Automate
Workflows triggered by business events, running headless. "When a deal closes in Salesforce, generate the onboarding packet, provision accounts, and ping the CS lead" — no human at the keyboard directing each step.

L5 — Loop
Output feeds back into shared knowledge so future runs improve. The onboarding packet generator learns from every edge case the CS team flags. This one's controversial — some argue it's inherently a team capability, not individual. Curious where others land.

Two things surprised us building this:

First, frequency ≠ proficiency. We have L1 users prompting 50 times a day and L3 users prompting five times with better results. Self-assessment is wildly inaccurate — people over-index on volume.

Second, the ladder creates psychological safety. Framing it as "observable behaviors" rather than "skill level" lets a senior director admit "I'm solid L2, working on L3" without feeling like they're falling behind.

Open questions we're still wrestling: Is L6 "teaches others to build L4/L5 systems"? Or "designs organizational AI strategy"? Does Loop belong on an individual ladder at all?

If your team has something similar — or tried and abandoned it — what did you learn?

WorkflowAI Implementation
Hands-on notes on AI tools and LLMs are collected in a library of Claude prompt techniques, with plenty of directly applicable cases.

All Replies (5)

M
MicroPanda Intermediate 1h ago
"Automate" and "Loop" are terrible labels — everything AI does is automation, and even cheap tiers loop through steps. Also, these "proficiency levels" feel way too granular. Someone comfortable with chat UIs jumps from 0 to 2 in minutes. And 3/4/5? In a tech tree, they'd all unlock simultaneously once you research level 2. Feels like artificial stratification.
0 Reply
R
Riley2 Advanced 1h ago
L9 hits the nail on the head. Everyone's obsessed with "10x dev speed" but nobody asks if the loop was worth running in the first place. Seen too many teams use AI to generate technical debt faster instead of stepping back to fix the architecture. The real leverage is killing the loop entirely.
0 Reply
M
Max75 Advanced 1h ago
Honestly, just knowing how to prompt effectively puts you ahead of 90% of devs. Don't waste time trying to build models—apply them to your actual domain now. You'll hit the limits fast, and that's where your real value kicks in. Let the tool handle the grunt work; you handle the judgment.
0 Reply
N
NeonPanda Intermediate 54m ago
Calling it a ladder implies a linear progression, but it's really just a toolbox. RAG, fine-tuning, agents, long context — they solve different problems. Pretending one "levels up" to the next just confuses the actual engineering work: picking the right trade-offs for your constraints.
0 Reply
D
Drew36 Advanced 52m ago
Same here. Stopped worrying about "skill level" months ago. It's just iteration — prompt, see what breaks, adjust, repeat. The model doesn't care about your title either.
0 Reply

Write a Reply

Markdown supported