Heidelberg AI Curriculum

4books in this track

L02 · Power user

Who is affectedYour team sees a bad document or a wrong figure

Show a Colleague AI on Their Own Task, in 30 Minutes

Run a 30-minute live demo on a colleague's own task instead of a slide deck. Pick the task with them, use material that's safe to show, check the result in front of them, hand over the keyboard, and let them decide to try, decline or wait, with the decision written down where the team can find it.

Outcome: A one-page demo record from a session with a real colleague: their task, the material and tool, the timed draft and check, the change they requested, the objection raised, and their own choice; it passes when the session took 30 minutes or less, the result was checked in front of them, and the choice is in their words.

Power user14 minLast edited: Sep 23, 2026

L03 · Builder

Who is affectedColleagues depend on something you built

T13-L03

Write a One-Page AI Rule Your Team Can Use Without Asking You

Write your team's AI working rule on one page: the approved route, green, yellow and red examples from your own work, the output check, who decides edge cases and what to do after a mistake. Test it with eight cards that have known answers, and hand it to a colleague who can keep it running.

Outcome: A one-page AI working rule, approved by the person accountable for the team, with its eight test cards and the results of three colleagues who didn't write it. It passes when every red card is stopped, each tester gets at least seven of eight right, the edge-case question gets an answer from the named person or deputy, and the deputy runs the card test with someone new without you.

Builder18 minLast edited: Sep 23, 2026

L04 · Integrator

Who is affectedCompany or lab systems and real data are in the loop

T13-L04

Roll Out an AI Assistant to a Whole Department, With Access, Cost and Consent Settled First

Take an AI assistant from a successful pilot to a whole department: seats by role, costed with the time it takes; oversharing fixed before it's switched on; the data protection officer and works council agreed; and waves with support, an objection route and a way back.

Outcome: A rollout plan and the results of its first wave; it passes when every seat is tied to a named role and task, the cost includes people's time, the oversharing check and its fixes are recorded, the DPO and the works or staff council have signed, access is removable by one group change, and after wave one the plan shows accepted outcomes, unused seats and every objection with its answer.

Integrator19 minLast edited: Sep 23, 2026

L05 · Operator

Who is affectedWork stops when it breaks, and it must survive you leaving

T13-L05

Keep Everyone's AI Skills Current, and Show It When Asked

Run AI literacy for a whole institute or company: a map of what each role must be able to do, short checks on real tasks instead of attendance lists, one register that follows people as they join, change role and leave, refreshers triggered by changes, and a record you can show an auditor or the works council.

Outcome: A role map and a training register for one real department, which pass when every role's abilities are written as checkable tasks, every person with access to an AI tool has a current check result or a dated reason why not, one monthly reconciliation with the access lists has been run and logged, one change has gone through the refresh decision, and a deputy answers an auditor's three questions from the register alone.

Operator19 minLast edited: Sep 23, 2026