30-day AI literacy plan for your teams, week by week
A 30-day AI literacy plan: take stock, set rules, practise with short games, measure by skill and keep records for Article 4 of the EU AI Act.
This plan gives you a concrete sequence for launching data and AI literacy in a team or a whole organisation within a month. It asks little of participants (one 5 to 10 minute game a week, plus a 30-minute kick-off) and leaves you with measured results and a record of what was done. Adapt it to your size and to how you use AI.
Before you start: who does what?
| Role | Responsibility in the plan |
|---|---|
| Sponsor (leadership, CDO, HR director) | announces the programme, explains why, approves the policy |
| Owner (L&D team or AI champion) | prepares the games, tracks participation, sends reminders |
| Business champions | check that the cases look like their team's real work |
| DPO or legal counsel | reviews the policy and the rules on personal data |
In Maketools, the programme owner is usually an Editor (forks and adapts the games) and the sponsor an Analyst (reads the reports). See roles.
Week 1: take stock and set rules
Goal: know where you are starting from and set three or four simple rules.
- Map current use. Which AI tools are in use, officially or not? By which teams? With what data? A short survey or a handful of interviews is enough.
- Write a one-page policy. What AI may be used for, what it must never receive (named personal data, decisions with consequences), mandatory review before anything is shared, and who to ask when in doubt.
- Choose your audiences. Everyone gets the core programme; high-risk teams (HR, legal, finance, customer service) get an extra layer.
- Prepare the first game. Fork AI or Not AI? and adapt a few requests to your own tools and teams (see fork a game). Give it Organisation access. How many private games can be live at once depends on your plan: check plan limits before planning several games in parallel, or undeploy one game before publishing the next.
Week 2: kick-off and first habit
Goal: everyone has played a first game.
- 30-minute kick-off, in a meeting or on a video call: why the organisation is doing this (the uses you found, the framework of Article 4 of the AI Act), the policy, then one game played together on screen.
- Share the game link with every participant. Members play with their own account, at your organisation's address.
- First participation check at the end of the week, in the game's report: plays started, completion rate.
Skills covered: knowing when AI fits, protecting personal data, keeping a human accountable, reviewing before publishing, choosing a script over a model.
Week 3: asking well and checking answers
Goal: move from "when to use AI" to "how to use it well".
- Second game: Prompt Quest, to structure a request (context, constraints, examples, output format).
- Third game for regular users: Hallucination Hunter, to spot hallucinations and bias and know when to verify.
- Targeted reminders for people who have not played yet. Reports are pseudonymised by default and show participation by group (from 5 players per group).
Week 4: data, depth and review
Goal: consolidate, go deeper where needed, and keep a record.
- Data literacy: Data Cleaning Rush for teams that work with spreadsheets (duplicates, missing values, formats, outliers). See data literacy.
- Role-specific depth: for high-risk teams, a fork whose cases reflect their situations (a hiring decision, a contract, a customer complaint).
- Skill review: in each report, find the skills below 50% correct answers. They set the agenda for the following month.
- Keep a record: export reports to CSV or PDF, or let your LMS receive results through SCORM or xAPI. Log in your internal register the actions taken, the audiences covered and the date the policy was last updated.
After 30 days
Literacy is not a one-off project: tools change, and so do teams. A few habits worth keeping:
- one game a month, with refreshed content (a fork can be edited and republished in minutes, see releases);
- onboarding: the core games in every new joiner's first weeks;
- a policy review each time a new AI tool is adopted;
- a quarterly look at the reports with the sponsor.
What this plan does not guarantee
This plan organises training measures and their records; it is not a compliance assessment. Obligations specific to your AI systems (especially those classified as high-risk) call for advice from your lawyer or DPO. See the disclaimer on the Article 4 of the AI Act page.
Start today
Play a game of AI or Not AI? yourself from the catalogue, no account needed. Then follow Getting started to create your organisation and fork your first game.