Writing Learning Objectives That Work

A measurable objective names an observable behavior — something you can actually test. "Understand photosynthesis" is not measurable. "Explain the role of chlorophyll in converting sunlight to chemical energy" is.

The test: could you write an assessment question based on this objective? If you can't, the objective is too vague. "Appreciate the importance of X" will never generate a useful test question.

Action verbs make objectives concrete: define, identify, explain, compare, apply, evaluate, construct, analyze. Avoid: understand, know, appreciate, be aware of, be familiar with.

A fuller objective can also state the conditions and the standard of success. Conditions describe the context: "Given a data table," "Without a calculator," "Using the course style guide." Criteria describe what counts as success: "with at least 90% accuracy" or "citing at least two primary sources."

You don't need conditions and criteria for every objective — they can make short lessons feel bureaucratic. They are most useful for skills-based and assessed work, where students need to know exactly what standard they are aiming for.

Example: "Given a short passage, identify the thesis and two supporting claims, with correct identification in at least four of five practice passages."

• "Understand the causes of the First World War" → "Explain how the alliance system turned a regional conflict into a continental war." The revision names an observable behavior and a specific focus.
• "Know the parts of a cell" → "Label the nucleus, mitochondria, and cell membrane on a diagram, and describe the function of each." The revision makes clear what a student must do and how you would check it.
• "Be familiar with spreadsheet formulas" → "Write a formula that calculates a monthly total from a column of daily figures."

Each revision can be turned straight into an assessment task.

Bloom's taxonomy describes levels of cognitive complexity: remember → understand → apply → analyze → evaluate → create. Lower levels are foundational; higher levels require deeper processing.

Introductory sections should lean on lower-order objectives: "Define the main terms" and "Identify the key differences between X and Y." Advanced sections should lean on higher-order objectives: "Evaluate competing explanations using the given data."

A mismatch between objective and instruction is a structural problem. If your objective asks students to "evaluate" but your content only "explains," either raise the content or lower the objective.

• Objectives that cover an entire course: "Understand the history of Western philosophy." Too broad to be useful — break it into chapter-level objectives.
• Objectives that describe what you'll cover, not what students will be able to do: "This section covers photosynthesis" is a topic, not an objective.
• Multiple objectives crammed into one: "Explain, apply, and evaluate X." Split them — a combined objective can't be assessed cleanly.
• Objectives listed but never referenced again: if an objective doesn't shape the content, assessment, or review, the objective isn't doing anything.

After writing a section, check each objective: is it actually addressed? Is it testable from the content you've written? If an objective is listed but not taught, either add the content or cut the objective.

Run it the other way: does any content present that doesn't map to an objective? If so, ask whether it belongs. Good textbooks are selective — they include what students need to meet the objectives, not everything the author knows about the topic.

Three to five objectives per chapter or lesson is usually enough. More than that suggests the section covers too much, or that some objectives are really steps toward a bigger one.

State objectives at the start of the section so students know what to focus on, then return to them at the end in review questions or a summary. Returning to them closes the loop and lets students check whether they met the promise the section made.

Yes — describe the performance or behavior that shows the skill or attitude. Not every goal is purely knowledge. Practical skills need objectives that describe a performance: "Set up a microscope and focus on a prepared slide." Attitudes are harder to measure, but you can target the behavior that shows them: rather than "value peer feedback," write "Give two specific, actionable comments on a classmate's draft."

If a goal truly can't be expressed as an observable behavior, it may still belong in the course description — just not in the list of objectives you assess.