How to Design a Lesson Plan

A repeatable process from experienced teachers.


How to design a lesson plan

Overview: Start with what students should be able to DO by the end, then build backward. Design the final task first, then the path that gets them there, then the individual lessons.

A structured “First Five” and “Last Five” that runs every day does most of the rest. Review what students produce, or the next lesson is a guess.

A lesson plan is the thinking you do before class so that during class you can watch your students instead of your notes. The plan itself can fit on one page. What matters is the order you build it in, and that order is the whole trick. Here's how experienced teachers do it:

Most plans start with an activity. You found a great video, you have a worksheet that worked last year, the textbook has a lab for this chapter. The activity goes into the plan first and the purpose gets backfilled around it. Sometimes that works. More often it produces a pleasant class period where students did things, and a week later they can't tell you what any of it was for.

Planning backward flips the order. First, decide what students should be able to do when they walk out. Second, decide what you would accept as proof they can do it. Only then choose activities, and keep only the ones that move students toward that proof. Teachers know this as backward design, from Grant Wiggins and Jay McTighe's Understanding by Design, and it is the closest thing lesson planning has to a consensus. Destination, evidence, then activities, in that order.

The test for any activity that wants into your plan is one question: what does this get my students closer to doing? If there's no answer, it's filler, however engaging it looks.

"Students will understand the causes of World War I" sounds like a goal, but you can't see understanding. You can see a student rank the causes and defend the ranking in a paragraph. The difference is the verb.

This is what Bloom's taxonomy is for: verbs. Label, solve, compare, diagram, explain in writing, defend, build. If your draft goal says understand, know, or appreciate, trade it for a verb that names something you could watch a student do.

Weak next to strong:

  • Weak: Students will understand theme.
  • Strong: Students will identify the theme of a short story and defend their choice with two lines from the text.
  • Weak: Students will know the water cycle.
  • Strong: Students will draw the water cycle and label evaporation, condensation, and precipitation.

Some teachers go one step further with the ABCD frame: Audience, Behavior, Condition, Degree. Ex. "Given a ruler and a protractor (condition), students (audience) will construct (behavior) three triangles accurate to within two degrees (degree)." You won't need all four parts every time. A goal with none of them is not a goal yet.

Last rule: two or three goals per lesson, ranked. When time runs short, and it will, you cut from the bottom of the list instead of deciding under pressure.

Before you plan a single activity, decide how you'll find out whether the goal happened. Most plans do this backward: teach first, then write a quiz that matches whatever got taught. Choosing the evidence first keeps the lesson honest, because every activity now has a target to point at.

Proof does not have to mean a quiz. An exit ticket. A one-sentence summary. One worked problem on an index card. Thirty seconds of listening while a pair explains the idea to each other. Anything that makes each student's thinking visible counts, and small beats elaborate, because you will read the small one.

One habit worth stealing: do the assignment yourself before you teach it. You'll find the confusing step, you'll learn how long it takes, and you'll walk in with an exemplar to show. Ten minutes spent doing your own worksheet can save a class period of confusion.

Strip the branding off any lesson framework and the same skeleton is underneath. An opening that surfaces what students already know and gives them a reason to care. A middle where the work shifts from you to them, which teachers shorthand as "I do, we do, you do": you model it, everyone tries it together with feedback, then students do it on their own. A close that makes the learning stick.

Two named models are worth knowing, because they fit different jobs:

  • Madeline Hunter's seven steps: objective, anticipatory set, input and modeling, checking for understanding, guided practice, independent practice, closure. Built for direct instruction. When you're teaching a skill or a procedure, this is the lane.
  • The 5E model: Engage, Explore, Explain, Elaborate, Evaluate. Students explore the idea before you explain it. Built for inquiry, and the default in many science classrooms.

Hunter's model turns rigid when the lesson calls for discovery or creative work, and 5E wastes time when students simply need to be shown a procedure. Pick by the job in front of you. Neither one is a compliance checklist.

Most teachers plan the middle and improvise the ends. It shows. The first five minutes decide whether students are with you, and the last five decide what they keep.

The opening has two jobs: wake up what students already know, and give them a reason to care. A question on the board they can argue about. A quick poll. A wrong answer to critique. Ninety seconds is enough. "Take out your books" starts the class, but it is not an opening.

The close belongs to the students, not to you. If you do the summarizing, all you've confirmed is that you learned it. Make them do it: one sentence on what they learned today, the muddiest point, a single problem that proves the goal. If the bell ends your lesson, the lesson didn't have a close.

A check for understanding only matters while there's lesson left to act on what you find. Learning from Friday's quiz that Tuesday's class was lost is an autopsy. You want a pulse check at minute twenty, when re-teaching is still an option.

Write the actual questions into your plan ahead of time, along with what you'll ask when the first answer comes back blank. Predict the misconception too. Every topic has a classic wrong turn, and if you know it's coming you can plan a question that surfaces it. "Does everyone get it?" is not a check; nobody says no.

Fast checks that work: mini whiteboards held up at the same time, a cold call after everyone gets think time, one problem on a scrap of paper, thumbs at chest height with eyes closed so nobody copies the room. Whatever you pick, it has to show you every student, not just the four who always answer.

Write minutes next to every block of the plan, then assume they're wrong. Discussions run long. The "quick" warm up eats twelve minutes. Every transition costs two or three, so a lesson with four transitions just spent ten minutes changing gears.

Plan for the room you teach, not the room in your head: two or three chunks, a buffer at the end, and your goals ranked so you already know what gets cut when you're behind. Cutting from the bottom of a ranked list takes no thought. Deciding mid-lesson what matters costs you the minutes you were trying to save.

Keep one back-pocket extension for the class that finishes early: a harder version of the same problem, not a new topic. And when the plan bends, let it bend. A lesson that goes exactly to plan is a coincidence. A plan that knows where it will bend is a tool.

Every one of these comes from planning in the wrong order, and every fix points back to a section above.

  • Starting with the activity instead of the goal. The plan becomes a schedule of things to do. The fix is the order this guide opened with: destination first, then evidence, then activities.
  • Writing the assessment after teaching. You end up testing whatever happened to get taught. Choose what counts as proof before you choose activities.
  • Planning only the middle. Without an opening there's no reason to care, and without a close nothing sticks. Script the first five minutes and the last five.
  • Planning what you'll do instead of what students will do. If the plan is a list of teacher moves, students are spectators. Count the minutes students spend working versus watching, and shift the balance.
  • Losing the big idea. Each lesson should connect to a unit question, and a lesson that connects to nothing gets forgotten with the unit. Say the connection out loud at the start, and again at the close.

The Template

The one-page skeleton this guide builds toward: your goal, the evidence you'll accept, the arc with minutes next to each block, and your check questions. Free to download and print.

Print the Template

Teaching elementary, middle, or high school? Grade-level versions live on the templates page.

Common Questions

Common questions about lesson planning

One page. The plan is a thinking tool for you, not a document for your evaluator, so it only needs the goal, the evidence you'll collect, the blocks of the lesson with minutes next to them, and your check questions. If your school requires a longer format for observations, keep both: the long one for the binder, the one-pager for teaching.

Yes, shorter ones. After enough repetitions the process moves into your head, but the order stays the same: goal, evidence, then activities. Most veterans still write down the timing and the questions they plan to ask, because those are the two things that slip when you improvise.

An agenda lists what will happen: warm up, notes, practice, exit ticket. An objective names what students will be able to do afterward. A class can get through the entire agenda without meeting any objective, which is why the plan starts with the objective and not the schedule.

Sketch the unit first, so you know where each lesson points, then write detailed daily plans a few days ahead. Planning one day at a time produces lessons that don't add up to anything. Planning a whole month in detail wastes work, because what happens Tuesday changes what Thursday needs.

Explore related topics