TL;DR: The question “how much do I need to understand about AI?” stopped being a matter of personal ambition and became partly a legal specification. Article 4 of the EU AI Act, in force since 2 February 2025, requires providers and deployers of AI systems to ensure a sufficient level of AI literacy among their staff and anyone operating systems on their behalf. The rest of the Regulation became generally applicable on 2 August 2026. The Act also defines AI literacy in Article 3(56) as the skills, knowledge and understanding needed to make an informed deployment of AI systems and to be aware of the opportunities, risks and possible harm. Article 14 goes further and lists what a person assigned to oversee a high-risk system must be able to do: understand the system’s capacities and limitations, resist automation bias, correctly interpret its output, decide not to use it, and stop it. Separately, the NIST AI Risk Management Framework organises AI risk work into four functions and names seven characteristics of trustworthy AI. Neither document was written for the non-technical professional, but read together they specify one. Below is the join: a verified table of the provisions that already bind ordinary staff, and an Operator Literacy Matrix that converts those obligations into five competencies you can actually test yourself against.
There is a familiar genre of article that promises to make you AI literate and then hands you a glossary. Tokens, parameters, training data, hallucination, fine-tuning. You finish it knowing more words and possessing no new capability.
The glossary approach fails for a structural reason. Vocabulary is what you need to follow a conversation about AI systems. Competence is what you need to be accountable for a decision one of them influenced. Those are different things, and only the second one is now being asked of people in ordinary jobs.
What changed is that the question acquired an external answer. Regulators, having decided that AI systems would be operated largely by non-specialists, had to write down what those non-specialists must be capable of. That written-down answer is not complete and it is not a curriculum. But it is the first specification of minimum viable technical understanding that does not come from someone selling a course.
The provisions that already apply to ordinary staff
Most coverage of the EU AI Act concentrates on the prohibitions and on obligations for model providers. Both matter, and neither is the part that touches a marketing manager, a recruiter, or a finance analyst. The parts that do are narrower and, in one case, older than most people realise.
The following table records provisions as they appear in the Official Journal text of Regulation (EU) 2024/1689, with the application dates set out in Article 113.
| Provision | What it requires | Who it binds | Applicable from |
|---|---|---|---|
| Article 4 (AI literacy) | Take measures to ensure, to their best extent, a sufficient level of AI literacy of staff and other persons dealing with the operation and use of AI systems on their behalf, taking account of their technical knowledge, experience, education and training and the context of use | Providers and deployers of AI systems | 2 February 2025 (Chapter I) |
| Article 3(56) (definition) | Defines AI literacy as skills, knowledge and understanding allowing informed deployment of AI systems and awareness of opportunities, risks and possible harm | Definitional; frames Article 4 | 2 February 2025 (Chapter I) |
| Article 5 (prohibited practices) | Lists AI practices that may not be placed on the market, put into service or used at all | All operators | 2 February 2025 (Chapter II) |
| Article 14 (human oversight) | High-risk systems must be effectively overseeable by natural persons; the deployer’s overseer must be enabled to understand capacities and limits, remain alert to automation bias, interpret output correctly, decline to use the system, and interrupt it | Providers, with measures to be implemented by deployers | 2 August 2026 |
| Article 50 (transparency) | People must be informed when they are interacting with an AI system unless it is obvious; synthetic audio, image, video and text output must be marked in a machine-readable format | Providers and deployers of certain systems | 2 August 2026 (Chapter IV) |
| Annex III point 4 (employment) | Classifies as high-risk the AI systems used for recruitment and selection, including targeted job advertising, filtering applications and evaluating candidates, and those used for decisions on promotion or termination, task allocation, and monitoring or evaluating performance | Determines which workplace tools carry high-risk obligations | 2 August 2026 |
| Article 6(1) route | High-risk classification for AI systems that are safety components of products under Union harmonisation legislation | Product-embedded systems | 2 August 2027 |
Two things in that table deserve more attention than they usually get.
The first is the date on Article 4. AI literacy became an obligation eighteen months before the bulk of the Regulation took effect. It was placed in Chapter I, the general provisions, and Chapter I applied from 2 February 2025. Organisations that have been waiting for August 2026 to think about staff capability were already late.
The second is Annex III point 4. The high-risk category is widely imagined as something exotic: medical devices, biometric identification, critical infrastructure. It also covers filtering job applications and monitoring employee performance. That is ordinary HR software. It means the person most likely to find themselves designated as the human overseer of a high-risk AI system is not an engineer. It is a recruiter.
What the law says a competent operator can do
Article 14 is the only place in the Regulation where the required capabilities of a human being are enumerated rather than gestured at. It says the system must be supplied so that the person assigned oversight is enabled, as appropriate and proportionate, to do five things.
To properly understand the relevant capacities and limitations of the system. To remain aware of the possible tendency to automatically rely on or over-rely on output, which the text names automation bias, particularly where the system produces information or recommendations for a decision a human will take. To correctly interpret the output. To decide, in any particular situation, not to use the system or to disregard, override or reverse its output. And to intervene or interrupt the system through a stop button or an equivalent safe-halt procedure.
Read that list as a job description rather than a compliance clause and something becomes obvious. Not one of those five capabilities requires you to know how a transformer works. Every one of them requires you to know what this specific system is for, where it fails, and what its output means. That is a different kind of technical knowledge from the kind engineers have, and it is not a weaker kind.
The fourth capability is the one that reframes everything. The law assumes competence includes the standing to refuse. An operator who cannot say “I am not using this output” has not been made literate, whatever training they were given.
The other half: what the risk framework adds
The AI Act tells you what you must be capable of. It does not tell you what to look at. For that, the most widely used public reference is the NIST AI Risk Management Framework, published as NIST AI 100-1 and written to be voluntary, sector-agnostic and usable by organisations of any size.
Two of its structures are directly useful to a non-specialist.
The framework organises risk work into four functions: GOVERN, MAP, MEASURE and MANAGE, with governance designed to cut across the other three rather than sit beside them. And it names seven characteristics of trustworthy AI systems: valid and reliable; safe; secure and resilient; accountable and transparent; explainable and interpretable; privacy-enhanced; and fair with harmful bias managed.
NIST later published a companion document for generative systems specifically, the Generative AI Profile, issued as NIST AI 600-1 in July 2024. It enumerates twelve risks unique to or exacerbated by generative AI, and two of them belong on any non-technical operator’s list. The first is confabulation, which NIST defines as the production of confidently stated but erroneous or false content, and which it explicitly identifies as the phenomenon known colloquially as hallucination. The second is human-AI configuration, which NIST describes as arrangements or interactions between a human and an AI system that can result in inappropriately anthropomorphising the system, or in algorithmic aversion, automation bias, over-reliance or emotional entanglement.
That second risk is worth pausing on. The failure mode NIST names is not the model. It is the relationship between the model and the person using it, and it runs in both directions: over-trusting is a risk and reflexively distrusting is also a risk. Nobody can debug that for you from the engineering side.
The seven characteristics are, in effect, the failure modes stated as goals. Each one is a way a system can let you down, and each is something a non-technical operator can form a view about without reading model documentation. Whether an output was correct is a validity question. Whether you can tell why it produced that output is an explainability question. Whether it behaves the same way for different groups of people is a fairness question. None of those require code.
The Operator Literacy Matrix
Here is where the two documents do something neither does alone. The AI Act specifies capabilities without saying what to inspect. NIST specifies what to inspect without saying who must be able to. Joining them produces a competency set for the non-technical professional.
The matrix below is a CEOtudent editorial framework. The left two columns are sourced, the right two are our synthesis and should be read as an argument rather than a finding.
| Competency | Legal anchor (AI Act Art. 14(4)) | Risk lens (NIST AI 100-1) | The question you must be able to answer | What incompetence looks like |
|---|---|---|---|---|
| 1. Scope | Understand the relevant capacities and limitations of the system | Valid and reliable | What was this system built to do, and on what kind of input does it stop being reliable? | Using a tool outside its intended purpose because it produced a fluent answer |
| 2. Suspicion | Remain aware of the tendency to over-rely on output (automation bias) | Accountable and transparent | Under what conditions would I doubt this output, and did I check any of them today? | Approving output faster over time as trust accumulates without evidence |
| 3. Interpretation | Correctly interpret the system’s output | Explainable and interpretable | Do I know what this score, ranking or confidence figure actually measures? | Treating a ranking as a judgment, or a confidence number as a probability of being right |
| 4. Refusal | Decide not to use the system, or disregard, override or reverse its output | Fair, with harmful bias managed | On what grounds am I permitted to reject this output, and have I ever done so? | Never having overridden the system, and having no process that would let you |
| 5. Interruption | Intervene or interrupt the system safely | Safe; secure and resilient | Who stops this, how, and how long does stopping take? | Nobody in the room knows who has the authority to switch it off |
The matrix is deliberately short. Five competencies, each traceable to a specific legal capability and a specific trustworthiness characteristic. If a training programme cannot show where it develops each of the five, it is teaching vocabulary.
Notice what is absent. There is no row for model architecture, no row for training data volume, no row for prompt technique. Those are worth learning and they are not the floor. The floor is the ability to be accountable for a decision the system influenced, and the Act’s own list is a better guide to that than any curriculum currently being sold.
Reading the matrix against your actual week
The matrix earns its keep when you apply it to a system you already use rather than to AI in the abstract.
Pick one tool your team relied on this week. An applicant filter, a forecasting model, a drafting assistant, a fraud flag. Then answer the five questions in order, in writing, and notice which ones you cannot answer.
Most people find they can answer one and three, partially. They know roughly what the tool is for and roughly what its output means. They fail on two, four and five. They have no stated conditions under which they would doubt it, no grounds on which they may reject it, and no idea who stops it.
That distribution is worth taking seriously, because two, four and five are the competencies that make oversight real. One and three make you an informed user. Two, four and five make you an operator. The Act is asking for the second thing.
If you want to develop the underlying capability rather than the checklist, the related work on this site is the place to continue: the distinction between knowing about AI and working fluently with it is covered in AI literacy versus AI fluency, the argument for why prompt skill alone is insufficient in prompt engineering is not enough, the concepts you need before handing work to autonomous systems in agent literacy, the skill now displacing prompt craft in what is context engineering, and the question of where to spend learning time in which AI tools are worth learning deeply.
Where this framing has limits
Three honest caveats.
The AI Act is European law. If you work outside the European Union and your employer does not place systems on the EU market or use output in the EU, none of it binds you. The competencies still transfer, because they were derived from what oversight actually requires, but the obligation does not.
Article 4 is drafted softly. It requires measures to ensure a sufficient level of literacy, to the best extent of the provider or deployer, taking into account context. That is not a testable standard, and the Regulation does not attach a specific training requirement to it. Treating it as a precise mandate overstates the text.
And the matrix is a synthesis, not a codified standard. The AI Act does not reference NIST, and NIST does not reference the AI Act. Mapping them is our editorial judgment about what the overlap implies. Someone could map them differently and be equally defensible.
None of that changes the underlying shift. For most of the past decade, understanding AI systems was optional for non-technical professionals and rewarded the curious. It is now specified, dated, and in one jurisdiction required. The people who will do well are not the ones who memorised the glossary. They are the ones who can say, about a specific system, on a specific Tuesday, exactly what it does badly and what they are going to do about it.
Frequently asked questions
Does Article 4 mean my employer has to send me on an AI course?
No. The text requires providers and deployers to take measures to ensure a sufficient level of AI literacy, to their best extent, taking into account staff technical knowledge, experience, education and training and the context of use. It does not specify a format, a syllabus, a certificate or a number of hours. A structured internal briefing tied to the systems you actually operate is closer to what the provision describes than a generic course.
I am not technical. Am I really expected to oversee a high-risk system?
Frequently, yes. Annex III point 4 classifies AI used for recruitment, application filtering, candidate evaluation, promotion and termination decisions, task allocation and performance monitoring as high-risk. Those systems are operated by HR and line managers, not engineers. Article 14 places the oversight capability with the natural person assigned to it, whoever that is.
What is automation bias, and why is it named in the law?
It is the tendency to rely automatically or over-rely on the output of an automated system. The Regulation names it explicitly in Article 14 as something the assigned overseer must remain aware of, and singles out the case where a system provides information or recommendations for a decision a human will formally take. That is the common workplace case: the system does not decide, it suggests, and the human approves.
Is the NIST framework mandatory?
No. NIST AI 100-1 is a voluntary framework. It is included here because it supplies the inspection categories the AI Act leaves open, and because its seven trustworthiness characteristics are usable by someone who cannot read model documentation.
When did the EU AI Act actually take effect?
Article 113 sets the general application date at 2 August 2026. Chapters I and II, which contain the definitions, Article 4 on AI literacy and the prohibited practices, applied earlier, from 2 February 2025. Chapter III Section 4, Chapter V, Chapter VII, Chapter XII and Article 78 applied from 2 August 2025. Article 6(1), covering AI systems that are safety components of regulated products, and its corresponding obligations apply from 2 August 2027.
Which competency should I build first?
Refusal. It is the one most people have never exercised, it is the one that reveals whether oversight is real or ceremonial, and it is the only one that requires a change in process rather than a change in knowledge. If there is no path by which you can reject an output and have that stick, the other four competencies have nowhere to go.
Sources
- Regulation (EU) 2024/1689 of the European Parliament and of the Council of 13 June 2024 laying down harmonised rules on artificial intelligence, Official Journal of the European Union, Article 3(56) on the definition of AI literacy
- Regulation (EU) 2024/1689, Article 4 on AI literacy and Article 5 on prohibited AI practices, Chapter I and Chapter II
- Regulation (EU) 2024/1689, Article 14 on human oversight and Article 50 on transparency obligations
- Regulation (EU) 2024/1689, Article 113 on entry into force and application, and Annex III point 4 on employment and workers management
- National Institute of Standards and Technology, Artificial Intelligence Risk Management Framework (AI RMF 1.0), NIST AI 100-1, United States Department of Commerce, January 2023
- National Institute of Standards and Technology, Artificial Intelligence Risk Management Framework: Generative Artificial Intelligence Profile, NIST AI 600-1, July 2024
This content was compiled with the support of AI following in-depth research, then written and prepared for publication by the CEOtudent editorial team.
This post is also available in:
