← Curriculum

Module 01

Learning Objectives and Educational Design

How to turn a broad simulation idea into specific, observable objectives that focus case content, learner expectations, assessment, and debriefing.

By the end of this module you can


Start with the difference between a goal and an objective

A simulation case can begin with a broad educational goal: “Residents should manage pediatric drowning” or “Junior residents should recognize and escalate STEMI on the ward.” That kind of goal gives direction, but it is not yet strong enough to design a case, choose an assessment, or run a focused debrief.

A specific measurable objective narrows the goal into learner performance. It names the learner, the action, the standard, the content or task, and the time frame. In practical terms, a useful objective answers five questions:

  1. Who is the learner?
  2. What will the learner do?
  3. How well, how much, or to what standard?
  4. Of what clinical task, concept, behavior, or work product?
  5. By when?

For simulation design, this distinction matters because goals describe the general destination, while objectives tell the facilitator what to watch for. The objective becomes the filter for the scenario stem, vital sign changes, confederate prompts, equipment, checklist items, and debrief priorities.

Why objectives matter in simulation

Objectives are not administrative decoration. They make the case teachable. Thomas emphasizes that objectives direct content priorities, suggest teaching methods, shape learner and curriculum evaluation, define the boundaries of a curriculum, connect local teaching to program-level expectations, and communicate intent to learners and faculty.

In simulation, the same logic applies at the case level:

Use precise verbs

Weak objectives often hide behind verbs such as “know,” “understand,” “learn,” or “appreciate.” Those words are hard to observe. They may be acceptable in a broad goal, but they do not tell a facilitator what counts as success during a case.

Prefer verbs that describe visible performance:

Instead ofTry
know the treatment for drowningtroubleshoot post-intubation hypoxemia using a structured sequence
understand shock physiologydifferentiate obstructive, distributive, cardiogenic, and hypovolemic shock from available data
appreciate family-centered communicationexplain the plan to the caregiver using plain language and invite questions
learn airway managementcall for airway support and prepare backup airway equipment before decompensation

The verb should match the level of performance expected. “List” is appropriate when recall is the target. “Interpret,” “prioritize,” “demonstrate,” “manage,” “lead,” and “adapt” usually ask more of the learner and require a different case design.

Match the objective type to the learning need

Thomas separates objectives into learner, process, and outcome objectives. For simulation educators, learner objectives are usually the center of the case, but the other types still help define the curriculum around the case.

Objective typeSimulation useExample
CognitiveWhat the learner should recognize, interpret, explain, or decideBy the end of the case, each PGY2 will identify post-submersion respiratory failure and name a broad differential for persistent hypoxemia after intubation.
AffectiveWhat the learner should value, attend to, or reflect onBy the end of the debrief, each learner will describe how stress during a pediatric resuscitation affected communication, role clarity, and prioritization.
Psychomotor or skillWhat the learner should demonstrate in the simulated environmentDuring the case, the airway learner will select weight-based pediatric airway equipment and confirm intubation with EtCO2 and chest X-ray.
BehavioralWhat the learner should incorporate habitually in clinical workDuring subsequent ED shifts, learners will routinely call for help and assign roles early when caring for unstable pediatric patients.
ProcessWhat must happen for the educational intervention to be deliveredBefore the simulation session, each learner will complete the assigned prework and review the emergency medication dosing card.
Patient or system outcomeThe downstream clinical aim the curriculum ultimately supportsThe curriculum aims to improve early recognition of pediatric bradycardia with poor perfusion and earlier consultation for refractory hypoxemia.

Not every simulation needs every objective type. Most cases work best with a small number of learner objectives and a few explicit process expectations. Use patient or system outcomes to clarify why the case matters, even when those outcomes are not directly measurable from a single session.

Aim for the highest meaningful performance

Objectives can target different cognitive levels. A novice may need to recall a time-critical dose or recognize a classic presentation. A senior resident may need to integrate competing data, manage uncertainty, lead the team, and adapt when the first plan fails.

Choose the highest level that is reasonable for the learner and the available simulation time. Then write any necessary enabling objectives underneath it. For example, a pediatric drowning objective might be:

During a simulated pediatric post-submersion resuscitation, the PGY2-3 team will assign roles, prepare a weight-based airway plan, and call PICU or ECMO support before intubation.

That objective requires enabling knowledge: pediatric airway sizing, drowning physiology, hypoxemia management, and the local pathway for PICU or ECMO consultation. The case does not need to list all of those as separate headline objectives, but the facilitator should know they sit underneath the main performance.

Map objectives to competencies without losing specificity

Competency-based education asks educators to describe observable work, not just time spent in training. EPAs describe professional tasks or units of work. Milestones describe developmental progress toward competence. These frameworks are useful because they connect a single simulation case to the larger training program.

The risk is that competency language can become too broad for case writing. “Provide patient care” or “communicate effectively” may be true, but it does not tell anyone what to build. Treat the competency, EPA, or milestone as the map, then write the simulation objective as the local, observable performance.

For example:

Program languageSimulation objective
Patient Care: recognizes and manages unstable patientsDuring the case, the PGY2 will recognize persistent post-intubation hypoxemia and work through tube position, obstruction, pneumothorax, ventilator settings, bronchospasm, sedation, and ventilation strategy.
Interpersonal and Communication Skills: communicates with teams and consultantsDuring the case, the team leader will state a shared mental model, assign medication and airway ownership, and communicate the patient’s condition to PICU or ECMO consultants.
Systems-Based Practice: mobilizes appropriate resourcesDuring the case, the senior resident will request pediatric airway support, PICU backup, and ECMO discussion early enough that help arrives before arrest physiology dominates the case.

This approach lets the case serve program requirements without becoming generic.

Keep the list short enough to use

Objectives usually need revision. A first draft often includes too many facts, too much detail for the learner level, or objectives that are easier to write than to teach. A strong module objective set should be manageable enough that learners can remember it and facilitators can debrief it.

Use this audit before finalizing a case:

  1. Does each objective answer who, will do, how well, of what, and by when?
  2. Does each objective use an observable verb?
  3. Is the expected performance appropriate for the learner level?
  4. Does the objective support the broader educational goal?
  5. Can the objective be mapped to a competency, EPA, milestone, or local program expectation?
  6. Does the case include a moment where the learner can demonstrate the objective?
  7. Does the assessment or debrief return to that moment?
  8. Is there anything in the case that does not serve one of the objectives?

Apply it to the pediatric drowning exemplar

The pediatric drowning case is intentionally progressive. The first learning target is not simply “intubate the child.” The case asks the team to lead a high-stress pediatric resuscitation, anticipate the airway, troubleshoot post-intubation hypoxemia, recognize bradycardia with poor perfusion, and call for help before the case narrows into a code.

A broad goal might be:

Residents will manage pediatric drowning.

A stronger objective is:

During a simulated pediatric post-submersion resuscitation, the PGY2-3 team will use closed-loop communication to assign roles, prepare a weight-based airway plan, troubleshoot post-intubation hypoxemia, and begin PALS bradycardia management when the heart rate falls below 60 with poor perfusion.

That objective now tells the case writer what to build. The case needs early post-submersion respiratory failure, a difficult airway cue, a predictable post-intubation hypoxemia state, and a bradycardia transition that forces the team to use pediatric arrest-adjacent physiology. It does not need every possible drowning complication, prolonged PICU management, or a complete ECMO lecture inside the scenario.

Working product

By the end of this module, you should have one broad goal, one to three specific measurable objectives, and a short list of success criteria. Those products will become the design constraints for Module 2, where the case structure, progression, cues, and distractors are built around the objectives rather than added after the fact.

Sources Used

Cases for this module

Module responses

Submit your reflections

These responses are saved for faculty review. They are not shown to other learners.