Why AI literacy programme matters now
The EU AI Act is no longer a theoretical compliance concern. With most of the Regulation applicable since 2 August 2026 — and the high-risk obligations following on 2 December 2027 — every European company that builds, deploys, or even procures AI systems sits somewhere inside the Act's risk framework. Building a role-based AI literacy programme — the topic of this piece — is one of the concrete mechanisms by which the regulation reaches into the day-to-day operations of an SME.
The vocabulary, done properly
Before going into implementation, it's worth fixing the vocabulary. A surprising amount of the practical confusion around building a role-based ai literacy programme comes from people using the same words to mean different things. Here are the definitions we work with internally at Innopulse:
Ai literacy programme — in the context of building a role-based ai literacy programme, this refers to the operational reality most DACH SMEs encounter when they move from theory to implementation. The term gets used loosely in marketing material; the regulatory and practical definitions are tighter and worth pinning down.
Ai training sme — in the context of building a role-based ai literacy programme, this refers to the operational reality most DACH SMEs encounter when they move from theory to implementation. The term gets used loosely in marketing material; the regulatory and practical definitions are tighter and worth pinning down.
Role-based ai training — in the context of building a role-based ai literacy programme, this refers to the operational reality most DACH SMEs encounter when they move from theory to implementation. The term gets used loosely in marketing material; the regulatory and practical definitions are tighter and worth pinning down.
Article 4 compliance — in the context of building a role-based ai literacy programme, this refers to the operational reality most DACH SMEs encounter when they move from theory to implementation. The term gets used loosely in marketing material; the regulatory and practical definitions are tighter and worth pinning down.
How to actually do this
The move from reading about building a role-based ai literacy programme to actually implementing it is where most SMEs stall. In our experience, the blockage is rarely capability — it's sequencing. Attempting to do everything in parallel burns out the small team that's responsible; attempting to do it in the wrong order means early work has to be redone.
The mistakes that slow everyone down
The first is scope creep disguised as ambition. A project scoped to address building a role-based ai literacy programme gradually expands to address everything adjacent. By month three, the original deliverable is two quarters away and the team has lost focus. The fix is ruthless: write down what's out of scope as explicitly as what's in.
What we actually do internally
On building a role-based ai literacy programme specifically, our internal practice has evolved considerably. The early version was manual, error-prone, and didn't scale past three products. The current version is partly automated, documented in runbooks, and survives the addition of new products without degradation.
What this means for the DACH landscape
Stepping back from the immediate operational picture, building a role-based ai literacy programme points at some broader shifts in how Swiss and DACH firms are going to operate over the next 24–36 months.
What to do next
If you're reading this because you have an active project around building a role-based ai literacy programme, here are the next steps we'd suggest — based on where most SMEs we work with are starting from.
Either way: pick your first step, put a calendar date on it, and start.