How to Write Lesson Objectives

A lesson objective is the one thing students should know or be able to do by the end of the lesson. It is not a topic ('fractions') or an activity ('worksheet') — it is a specific, observable outcome. Everything else in your lesson exists to reach it.

When the objective is sharp, your instruction, practice, and assessment all align to it. When it is vague, the lesson wanders. Writing a strong objective first is the single most important planning move you make.

The verb is what makes an objective measurable. 'Understand,' 'know,' and 'appreciate' cannot be observed or assessed — you cannot see understanding directly. Replace them with verbs you can observe: identify, compare, calculate, explain, classify, construct, analyze.

Compare these two: 'Students will understand photosynthesis' versus 'Students will be able to diagram the inputs and outputs of photosynthesis.' Only the second tells you exactly what to teach and how you will know it worked.

Bloom's Taxonomy helps you target the right depth of thinking: Remember, Understand, Apply, Analyze, Evaluate, Create. A lesson that only asks students to 'list' (Remember) is shallower than one that asks them to 'compare' (Analyze) or 'justify' (Evaluate).

Match the verb to the cognitive level you actually want. If your standard calls for analysis, do not write a 'define' objective. Use Bloom's verb lists to push beyond recall when the content calls for it.

SWBAT — 'Students Will Be Able To' — is the most common and reliable format. It forces an action verb and an observable outcome. A complete objective often has three parts: the condition, the behavior, and the criterion for success.

Example: 'Students will be able to compare two fractions with unlike denominators (behavior) using visual models (condition) with at least 80% accuracy on an exit ticket (criterion).' Not every objective needs all three parts written out, but strong ones imply all three.

Your objective should map directly to the standard you are teaching. The standard tells you the destination; the objective is the specific step you are taking today. Reference the standard code so the alignment is explicit and reviewable.

If a standard is large, break it into several daily objectives. A standard about 'analyzing how authors develop theme' might become three lessons, each with its own narrow objective. This keeps daily lessons focused and the standard fully covered over time.

The most common mistakes: writing the activity instead of the outcome ('Students will complete the lab' is what they do, not what they learn), using unmeasurable verbs ('understand,' 'learn about'), and writing objectives so broad they cannot be taught or assessed in one lesson.

A good test: could you write an exit ticket that directly measures this objective? If not, the objective is too vague or too big. Rewrite it until a single question or task could prove students met it.