Who Needs Which Level?
Not everyone on your team needs to learn the same thing. Even the state’s talent programme built three separate tracks: basic literacy, application-professional certificates and advanced specialisation. If you do not make the same distinction for your own team, one of two things happens. You teach everyone too much and nobody finishes. Or you teach everyone too little and nobody can use it.
This piece builds a three-level ruler. Who should stand where, how you measure it, which training feeds each level.
What Is the Problem?
BU BÖLÜMÜN ÖZETİ
- One course for everyone
- Only the curious one learns
- The manager never learns
Three scenes repeat in businesses without a training plan.
One course for everyone
A video set gets bought and assigned to the whole team. The accountant watches, the field technician watches, the marketer watches. Nobody sees an example that touches their own work. Three weeks later the completion rate sits at twenty percent.
Only the curious one learns
Someone teaches themselves and everyone else asks them. Short term, it works. Long term, it is dangerous. When that person leaves, the knowledge leaves too. And the curious person is rarely the right person, only the most willing one.
The manager never learns
The most commonly skipped link. A decision-maker who does not use the tools makes one of two errors. Either believing every proposal or believing none. Both are expensive.
Why Does It Happen?
BU BÖLÜMÜN ÖZETİ
- The capability need was never written down
- Training gets confused with tool demos
- Learning has no finish line
Three root causes.
The capability need was never written down
Businesses rarely write which role requires which capability. An unwritten need does not get measured. An unmeasured need cannot be matched to the right training.
Training gets confused with tool demos
Most courses explain “this tool does that”. The real question is how to connect the tool to your own work. Tools change; method stays.
Learning has no finish line
“Let’s learn AI” has no end point. Nobody commits serious time to work with no end point. Defining levels is how you draw a finish line.
How Is It Done?
BU BÖLÜMÜN ÖZETİ
- Step 1: define the three levels
- Step 2: assign every role a level
- Step 3: match levels to training
The ruler builds in three steps.
Step 1: define the three levels
Level one: safe user. Knows what the tool can do, notices when it is wrong, knows which data never goes in. Level two: applies it to their work. Uses the tool regularly in their own process, checks the output, measures the gain. Level three: designs the process. Connects the tool to the workflow, sets thresholds and approval points, teaches the team.
Step 2: assign every role a level
Take the team list and write a level next to each name. The rule is simple: everyone should reach level one. Roles where AI touches the work directly belong at level two. For level three, one or two people usually suffice. In a small team that person is often the owner. Most teams end up with a crowd at level one, a few at level two and one at level three.
Step 3: match levels to training
The mapping lines up with the national programme’s three tracks. Level one is served by the free literacy programme. Level two suits sector certificates and the application-professional track. Level three needs advanced programmes, a real project and mentoring. Once mapped, your training budget also becomes clear.
How Long, Where to Start?
BU BÖLÜMÜN ÖZETİ
- Half a day to build, weeks to months to run
- The return sits in two lines
- First step: distribute the list, start with yourself
The ruler is cheap to build and the first step is available today.
Half a day to build, weeks to months to run
The level definitions already exist; your job is distributing the team across them. Half a day for a team of ten. Training time then varies by level: a few hours at level one, a few months at level two, a project at level three. That split also answers the “training takes too long” objection. The long part does not apply to everyone.
The return sits in two lines
Level one cuts mistakes: data leaks, fabricated facts, fake content. Levels two and three add speed: time and cost fall. Level one is insurance, the others are investment. Do not defend them with the same argument; in a budget conversation they are stronger apart.
First step: distribute the list, start with yourself
Write a level and a date next to every name. The output is one page. Then complete your own level first — that is the strongest message you can send. Third, open a weekly hour in the calendar. The content changes by level; the hour does not. The first rung of the ladder gets climbed in that hour.
The Common Mistake
BU BÖLÜMÜN ÖZETİ
- Trying to push everyone to level three
- Assigning levels by age or seniority
- Moving on without measuring
Three traps while building the ruler.
Trying to push everyone to level three
Well-intentioned and exhausting. Not everyone needs to design processes. Few designers and many users is the normal shape.
Assigning levels by age or seniority
Levels follow the work, not the title. A senior whose work sits far from the tools needs only level one. A junior whose work sits close can reach level three. Seniority order and capability order are different things. Say this out loud when you assign levels; unsaid, a level reads like a promotion or a demotion.
Moving on without measuring
“Watched the training” and “learned it” are different states. The national programme’s micro-certificates depend on a minimum threshold. Set a simple internal test too: can the person explain what they did, using an example from their own work?
Frequently Asked Questions
Sık Sorulan Sorular
The opposite: it matters more when you are small. Sending all five people on a three-month course stops the business. The ruler tells you who spends three months and who spends three hours. The usual shape is four people at level one and one at level two — and that one is often the owner.
Usually one of two things. Either the level was mismatched and the person could not connect it to their work. Or no application space opened after the course. The second is more common. Within two weeks of training, give the person a small task: run one of their own processes through the tool and report what happened. Unused knowledge fades in a fortnight.
Tool knowledge goes stale; method knowledge does not. All three levels rest on method: knowing what not to share, checking the output, wiring it into a workflow. Those hold when the tool changes. Use the same test when choosing a course: does it teach the tool or the method?