"Employees will understand GDPR" is not a learning objective. It is a wish. An objective describes what the employee does differently after the module — the click, the decision, the action. An objective that cannot be measured cannot be verified. The module then becomes a compliance chore without effect.
Bloom's taxonomy (1956) and its revision (Anderson and Krathwohl, 2001) still offer the most practical frame for writing objectives. Six cognitive levels tell you where the employee should land after training. This article shows how that maps to concrete SMART objectives for HR teams under 150 employees.
Why a bad objective breaks the module
A weak objective costs you in three places. Content drifts without focus. The quiz tests memory instead of behavior. The report to leadership reads generically — "90 % completed" — with nothing about actual capability.
Three classic wrong verbs:
- "understand" — not observable; without a task, comprehension cannot be verified.
- "be aware of" — means the employee saw a slide. Nothing more.
- "know" — measures memory, not use.
An objective that starts with an active verb ("identifies", "classifies", "drafts") can be tested with a scenario, not a multiple-choice item about definitions.
Bloom's taxonomy in L&D — what works, what doesn't
The 2001 revision renames the levels as verbs and adds a knowledge dimension (factual, conceptual, procedural, metacognitive). The six levels from lowest to highest:
- Remember — the employee lists the 6 rights of a data subject under GDPR.
- Understand — the employee explains the difference between a controller and a processor.
- Apply — the employee spots 3 signs of fraud in an attached phishing email.
- Analyze — the employee breaks down an incident against internal policy and GDPR.
- Evaluate — a team lead judges whether a report falls under the whistleblower directive.
- Create — a case handler drafts an intake protocol for a new type of report.
For onboarding and compliance modules in SMBs, cover the first three levels. Analyze and evaluate belong to team leads and specialists. Create is for trainers and internal mentors.
A common mistake: the objective sits at "remember", but the quiz tests "apply". The module never trains the scenario, so completion drops below 60 %.
SMART: translating it to HR reality
The SMART frame (Specific, Measurable, Achievable, Relevant, Time-bound) adds the missing timeline and threshold. Sample transformation:
- Weak: "Employees understand fire safety."
- Better: "By 30 October 2026 all production staff correctly execute the 5-step evacuation protocol; verified on the annual drill, target ≥90 %."
The better objective has four parts:
- Who — production staff, not "everyone".
- What — the 5-step protocol, not "safety".
- Where verified — the annual drill, not "a quiz".
- When and how much — 30 October, target 90 %.
That structure solves two things. The content designer knows what to include. The audit report has a number to point at.
Two worked examples
Example 1: GDPR onboarding, 40 employees
A services company with 40 staff rewrites onboarding for anyone handling client data. The old module (60-min video) hit 55 % completion and 2 incidents in a year. The new objective set under Bloom:
- Remember (week 1) — the employee identifies the 6 categories of personal data their team handles.
- Apply (week 2) — the employee correctly classifies 5 client requests (access, erasure, rectification).
- Analyze (day 30) — in a "phishing from a supposed customer" scenario, the employee decides whether it is an incident and files the internal form in under 15 minutes.
The module becomes three 8-minute segments with scenario-based quizzes. Report at 3 months: completion 92 %, time-to-correct-report on a test phishing simulation 11 min. Incidents in the following half-year: 0.
Example 2: cybersecurity training, 130 employees
An IT services firm runs annual awareness training under EU network-security rules. Before: single 40-min module, completion 78 %, 12 % correct on phishing simulations. Objectives now split by role.
- All staff — in a 4-minute video, spot 4 signs of a suspicious email; the quiz covers 6 scenarios, pass at 5/6.
- Team leads — in a 15-min module, analyze an incident and decide when to escalate to the CISO. Verified with a tabletop exercise.
- System administrators — in a 45-min workshop, draft a playbook for a novel attack type; graded by peer review.
After the first cycle: phishing detection at 71 % (up from 12 %), median escalation time 22 min against a prior 4 hours.
Active verbs by level (short list)
For an HR team writing objectives, this short list covers 90 % of modules:
- Remember — list, identify, define, describe.
- Understand — explain, summarise, compare, classify.
- Apply — execute, calculate, use, demonstrate.
- Analyze — break down, correlate, contrast, derive.
- Evaluate — judge, rate, justify, recommend.
- Create — plan, assemble, design, formulate.
Avoid these verbs: understand, know, be aware, appreciate, familiar with. That is policy vocabulary, not training vocabulary.
Three writing traps
- Too many objectives per module. 4–5 solid objectives is the ceiling for a 20-min module. Ten objectives means none measure anything specific.
- Objective without a threshold. "The employee can report an incident" hides how many minutes, which form, and what pass rate. Pin the number in the objective, not in a separate document.
- Objective that skips the level the training needs. GDPR training for a service desk sits at "apply", not "remember". If the objective clings to memory, the quiz is irrelevant.
For linking objectives to measurable results, see 3 metrics for training ROI.
What consolidation actually solves
An objective written to Bloom and SMART discipline plugs cleanly into a quiz, a report, and a refresher. An LMS such as Mentor lets each objective carry its cognitive level and bind to a quiz that tests exactly that level. The audit trail then shows more than "who finished" — it shows what each person can actually do.