A practical guide to writing learning objectives: Bloom's revised taxonomy, choosing the right verb, and aligning objective to assessment.
Got an LMS decision on your plate?
45-minute call. Plain-English audit. Fixed-price quote if there's a fit, or a "no" if there isn't. No deck. No pitch.
A practical, phase-by-phase walkthrough of the ADDIE instructional design model for L&D teams building their own training.
A step-by-step way to run a training needs analysis, from gathering data at three levels to prioritizing gaps and turning them into a training plan.
A step-by-step guide to building a competency framework, with a reusable template and how to run it on a platform you own.
Writing learning objectives is the single highest-leverage step in course design, and the one teams rush most. A good objective states exactly what a learner will be able to do after the training, in terms you can observe and test. Get it right and the content, the assessment, and the evaluation all fall into place. Get it vague and you end up with a polished course nobody can prove taught anything.
This guide covers what makes an objective measurable, how Bloom's revised taxonomy helps you pick the right action verb, how to keep objectives observable, and how to align each objective to its content and its assessment. It assumes you have already done the surrounding design work: writing objectives sits inside a larger process like ADDIE, and it should be driven by a real training needs analysis rather than invented at the whiteboard.
A learning objective is a promise about the learner, not the course. It is not "this module covers lockout/tagout"; it is "the learner will perform a lockout/tagout on a guarded conveyor without a prompted step." The difference is that the second version describes an observable action you could watch someone do or set a task to verify.
A well-formed objective usually has three parts:
Not every objective needs all three spelled out, but the performance is non-negotiable. If you cannot picture someone doing the thing, the objective is not finished.
Bloom's taxonomy is a classification of cognitive skill originally published in 1956 and revised in 2001 by Anderson and Krathwohl. The revision restated the levels as verbs and reordered the top two. The six levels, from foundational to advanced, are:
The taxonomy earns its keep as a verb picker. Decide what level of cognition the job actually requires, then choose a verb from that level. A new hire on a compliance topic may only need Remember and Understand. A supervisor investigating an incident needs Analyze and Evaluate. Matching the verb to the real demand keeps you from over- or under-building the course, and it maps cleanly onto the levels in a competency framework.
The chosen level also dictates how you assess. A Remember objective is fair game for a multiple-choice question. An Apply objective needs a task, a simulation, or a demonstration, not a quiz about the task. If your objective says "perform" but your test only asks people to "identify," the assessment is measuring a lower level than the objective promises, and the mismatch quietly invalidates your Level 2 evidence.
The most common failure is the invisible verb. "Understand," "know," "appreciate," "be aware of," and "be familiar with" all describe things happening inside someone's head that you cannot observe. They feel like objectives but cannot anchor a course or an assessment.
The fix is to translate the internal state into a visible behavior that would only be true if the learner had it. You cannot see "understand the refund policy," but you can see "apply the refund policy correctly to three sample cases." The observable version is what you actually wanted; the vague version was just shorthand for it.
A quick test: for each objective, ask "how would I know?" If the answer is a thing you could watch, score, or check off, the objective is measurable. If the answer is "I would just have to trust they got it," rewrite it.
A learning objective is only useful if the rest of the course lines up behind it. Three things must agree:
When these three drift apart, you get familiar failure modes: content that covers far more than the objectives require, so learners drown; assessments that test recall of facts the objectives never mentioned; or objectives that promise application while the course only delivers explanation. Building a simple grid, one row per objective with its content and its assessment item beside it, exposes every gap and every orphan in a single glance. It also gives your Level 2 measurement its backbone, because a passing score now maps to a named capability.
Enough to cover the real capability gap and no more. A short module might have two or three; a full onboarding course will have many, grouped by section. If a single course has thirty flat objectives, it is probably several courses, or several of those objectives are content notes in disguise.
No, though they are related. A competency is a broad capability a role requires, often spanning many courses and on-the-job experience. A learning objective is a specific, testable outcome of one piece of training. Competencies live in a competency framework; objectives are how individual courses ladder up to them.
Usually yes. Stating up front what someone will be able to do sets expectations and helps them self-check. Just phrase them in plain language for the learner, "by the end you will be able to process a refund," rather than exposing the internal taxonomy scaffolding you used to write them.