AI Literacy und KI-Kompetenz: Definition, Stufen und Artikel 4

Menschen arbeiten gemeinsam in einem moderierten Technologie-Workshop

Short definition (citable, 49 words)

AI literacy is the ability to use AI systems in your own work context in an informed, critical and responsible way. It includes understanding what a system can and cannot do, judging its output, and weighing legal and ethical consequences. Under the EU AI Act, this ability is now a duty for companies.

Competence that lands in the process. In just one week your team builds on real cases and documents its learning. Book a discovery call, or enter your email below.

Where the term comes from and how it shifted

Literacy first meant reading and writing. Over decades it produced derived competence terms such as media literacy and data literacy, each the basic ability to deal with a medium responsibly. AI literacy stands in that line. The shift came in 2025. Before, it was a soft educational goal, nice to have but non-binding. Since Article 4 of the EU AI Act took effect on 2 February 2025, it is a requirement for providers and deployers of AI systems. The term changes register, from a description of skill to a duty with an addressee and a context. That is why AI literacy is worth treating not as a buzzword but as something you must build and document in a demonstrable way.

The mechanism: competence has levels

AI literacy is not a yes or no quantity, it is a ladder. Reaching only the bottom rung means operating a tool without being able to judge it. The higher rungs carry responsibility. In practice it helps to name the levels and map roles onto them.

  Level 4  Governance   set rules, assess risk, own the deployment
  Level 3  Judge        check output, see limits, spot hallucination
  Level 2  Apply        solve tasks with AI, steer prompts
  Level 1  Operate      open a tool and run a basic task
     |
     +--> Article 4 asks for the level that fits each role, not the top level for everyone

The key is the arrow at the bottom. The EU AI Act does not ask everyone to reach the governance level. It asks for competence that fits the role and the risk. A caseworker using an approved tool needs level 2 and a feel for level 3. Whoever decides on AI deployment needs level 4. That role logic is the difference between a meaningful competence measure and a tick-box training for all.

A worked mini-example

An illustrative model, not a client figure. A 200-person company wants to take Article 4 seriously. Instead of rolling a 60-minute mandatory course out to everyone, it maps roles to levels.

  • 200 people with basic AI contact, target level 2, a short practical format.

  • 40 people using AI in customer-facing or data-facing processes, target level 3, hands-on building on real cases.

  • 8 people with decision responsibility, target level 4, plus governance and risk assessment.

Effort concentrates on the 48 people where competence really carries impact and risk. The numbers are a planning model, not a rule. The point is the structure, since one course for all is expensive and hits the wrong people, while a role-based mapping is cheaper and more defensible.

Team during the AI hackathon

Use cases by function

FunctionWhat competence targetsCritical skill
Marketingcheck AI content, clear sources and rightsspot hallucination and image rights
Salesframe AI research before the customerverify facts against a source
HR and recruitingfair, traceable use on applicationssee bias and discrimination risk
Finance and controllingvalidate figures from AI analysisrecompute instead of trust
IT and softwareintegrate models and assistants safelyknow data leakage and prompt injection
Leadership and legalown and document the deploymentmap roles, risks and duties

Industries where AI literacy matters most

The pressure is the same everywhere, the consequence is not. In finance, insurance and healthcare the cost of a misjudged AI output is highest, so the focus is levels 3 and 4 and documentation. In marketing agencies, our first target market, the need is broad application skill and clean checking of sources and rights. In HR and recruiting the discrimination risk leads, invisible without competence. In industry and IT competence meets security, because data and systems are touched. The common thread is that competence is measured against the role, not against an attendance certificate.

When building competence is urgent, and when it can wait

It is urgent when AI is already in use, when staff use AI in customer-facing or data-facing processes, and when Article 4 documentation is missing. It can wait when AI is not used and not planned, because then the application context that competence attaches to is absent. Competence without application fades, so the best moment is when real use begins.

Team during the AI hackathon

AI literacy and the EU AI Act, Article 4

Since 2 February 2025, Article 4 of Regulation 2024/1689 requires providers and deployers to ensure a sufficient level of AI literacy among their staff and others operating on their behalf. Sufficient means role and context specific, measured against technical knowledge, experience, education and the purpose of use. A practical competence measure, such as building on real cases with a documented learning state, can support and evidence this duty. It is not an official certificate and does not guarantee automatic conformity. The company assesses adequacy itself, with qualified counsel where needed.

Article 4 scope note: this page explains the competence concept and how a measure can support and document competence building. It is not legal advice and not proof of automatic conformity.

Next step

Two ways, depending on where you are.

  • Book directly: Book a discovery call. 30 minutes to map roles to competence levels and look at your Article 4 need.

  • Read along first: Enter your email and get the competence-levels template plus Article 4 notes. No spam, unsubscribe anytime.

Ready for your first prototype?

Start with one team. In one week you leave with skills, shipped output and momentum.

Book a discovery call

Client voices

What teams say after the week

Short feedback from hackathons with engineering, marketing, operations and leadership teams.

Our engineers built a code-review assistant in two days that the whole team still uses. No training ever did that.
Engineering leadNavVis
The whole agency was building. Marketers with zero coding background shipped content pipelines that saved real hours.
Managing directorYOYABA
Procurement workflows that used to sit on a roadmap were prototyped and demoed inside the same week.
Head of operationsOnventis
Our leadership cohort left with five working agents and a completely different sense of what AI can do for us.
Programme ownerAdobe cohort

Book a slot

Ready to turn learning into working prototypes?

Start with one team. In one week, leave with practical skills, shipped output and momentum. Just pick a free slot below.

The calendar is loaded from Cal.com and sets its own cookies. It only starts once you request it here.

FAQ

Frequently asked questions

Still something open? We clear it up in 20 minutes.

Book a discovery call