Case-Based Learning

Case-Based Learning is a workshop design approach in which participants analyze a specific, resolved scenario — the case — to draw out transferable principles they can apply to similar situations later. The case carries enough detail to reward careful reading, describes events that have already played out, and becomes the material participants think through as the workshop leader asks questions. The outcome is not a fresh solution to a live problem. It is the pattern recognition participants build by working through the case carefully.

The approach began in law. Christopher Columbus Langdell became dean of Harvard Law School in 1870 and argued that law should be studied the way natural sciences were — by looking at the raw material directly, not through a textbook's explanation of it. His 1871 casebook A Selection of Cases on the Law of Contracts gave students the court opinions themselves. Class time shifted from lecture to sustained questioning of those opinions.

Wallace Donham brought the method to Harvard Business School as dean in 1919. He adapted it for the messy, context-heavy decisions managers actually face — situations where the right answer depends on details the textbook cannot anticipate.

By the time Barnes, Christensen, and Hansen codified the method in Teaching and the Case Method (1994), it had spread across law, business, medicine, public policy, and professional education. The classic academic form is group-based — a seminar discussion led by a skilled questioner. Workshop applications work well in both group and individual configurations.

Case-Based Learning looks at situations that have already finished, while Problem-Based Learning and Inquiry-Based Learning work on situations that are still open. The case has already happened. The decisions have already been made. The outcome is already known, or will be revealed during the session. What participants build through the analysis is the pattern recognition needed to handle similar situations when they meet them fresh — the judgment to see what kind of situation they are in.

What Case-Based Learning Is

Four structural components define Case-Based Learning, whether participants analyze together or individually.

• A specific, resolved case. The case is a detailed account of a particular situation — real or closely modeled on reality — including the decisions made, the context around them, and the outcome that followed. Thin cases produce thin analysis. The case has to carry enough detail that participants can disagree about what the decision-maker should have done, what they missed, and what they got right.
• Participant preparation. Participants read the case before the session. Reading it for the first time in the room turns the analysis into guesswork. Reading it ahead lets participants form their own view before the discussion starts. The preparation is the foundation — without it, the method collapses into a lecture about the case.
• Question-led analysis. The workshop leader guides the analysis through Socratic questioning — what did the decision-maker see at the moment of the decision? What did they miss? What would you have done with the same information? What changes if you learn the outcome? The leader does not narrate the case or deliver the lessons. Participants work them out by answering the questions.
• Principle extraction. The closing move names what carries over beyond this one case. A case discussion that ends at "that was an interesting story" has failed. A case discussion that ends at "here is the pattern we saw, and here is how to recognize it next time" has done what the method was designed to do. The workshop leader runs the extraction explicitly, drawing the general lesson from the specific material.

Group and Individual Configurations

Case-Based Learning's classic form is the group seminar — Langdell's law classroom, Donham's business-school class, the questioning discussion that has defined the method for 150 years. Workshop applications work in both group and individual configurations. Each produces a different kind of learning.

Group configuration. The cohort discusses the case together while the workshop leader asks probing questions. Participants take positions, push back on each other, and refine their reading through the discussion. The leader keeps the analysis honest by asking what evidence supports each reading and where the reasoning is weak. The group form is the classic configuration. It fits sessions where one of the outcomes is the ability to reason about cases in conversation with other practitioners.

Benefits of the group form:

• Different readings surface patterns a single reader would miss.
• Disagreement forces participants to defend their reading with evidence from the case.
• The discussion models the kind of peer conversation participants will have about real situations after the workshop.
• The group together remembers more case detail than any one person brings.

Individual configuration. Each participant analyzes the case on their own, while the workshop leader moves between them asking probing questions. The leader asks the same kinds of questions a seminar discussion would generate, but directed at one participant's reading at a time. This fits 1:1 coaching, small cohorts where each participant is analyzing the case against their own business context, or sessions where participants benefit from slower, uninterrupted time with the case.

Benefits of the individual form:

• The participant applies the case directly to their own context, which activates the self-reference effect and produces stronger encoding.
• The analysis runs at the participant's pace — slower thinkers get the time they need, and faster thinkers can push further.
• No averaging toward group consensus — the analysis lands on what is true for the participant, not on what the group can agree on.
• Each participant leaves with a specific diagnosis applied to their own situation, not a shared class interpretation.

Choosing the configuration. Group is stronger when the case benefits from different interpretations, when participants can challenge each other's reasoning productively, or when peer case discussion is itself a target skill. Individual is stronger when each participant is analyzing the case through their own context, when the cohort is small enough for the leader to circulate to every person, or when the reading benefits from sustained solo attention. Hybrid configurations are common — participants analyze the case individually first, write down their reading, then enter the group discussion with a position already formed.

When to Use It

Case-Based Learning fits workshops where the outcome is judgment — the ability to recognize what kind of situation you are in and respond appropriately. It is strongest in domains where patterns repeat, where practitioners already work by comparing new situations to past cases, and where participants need to build the case library that fast judgment depends on.

Good candidates:

• Workshops on diagnosis, strategy, or judgment in domains where patterns repeat.
• Participants with enough domain knowledge to engage with a detailed case.
• Outcomes that require recognizing situation types rather than executing procedures.
• Sessions of 60 minutes or longer — case analysis needs time to develop.

Less suitable:

• Workshops on procedures or techniques where the same move applies regardless of context.
• Introductory content where participants lack the background to read a detailed case.
• Audiences who expect explicit frameworks and will read case analysis as the leader withholding the answer.
• Sessions too short for preparation, analysis, and extraction.

What It Looks Like in Practice

A 90-minute group-configured Case-Based Learning session for coaches studying behavior-change workshop design might run like this:

• Pre-work (45 minutes, done before the session). Participants read a detailed case — a coaching business that ran a six-month group program for 40 mid-career professionals. The case includes the program structure, the pricing, the marketing, the facilitation approach, the satisfaction scores (consistently 4.7/5), the completion rate (72%), and the behavior-change outcome six months later (12% of participants reported meaningful changes to their practice). Participants come in having formed their own initial reading of what went wrong.
• Opening framing (5 minutes). The workshop leader opens by naming the discussion question: how do you explain the gap between the satisfaction scores and the behavior-change outcome? The leader notes that the case does not hand over a single right answer — the discussion is what produces the reading.
• Socratic discussion (60 minutes). The leader works the room with questions. What did the designer optimize for? What did they assume about how learning transfers? What evidence in the case points to a design failure versus a participant-commitment failure? What would you change if you were running this program next quarter? Participants take positions, disagree, refine. The leader surfaces assumptions and pushes back on weak reasoning. No lecture.
• Principle extraction (20 minutes). The leader names the patterns that emerged across the discussion — usually some combination of satisfaction scores reporting how the session felt rather than what it produced, the absence of design moves that force transfer, and the confusion between being engaged in the room and actually changing behavior afterward. The extraction names the pattern so participants can recognize it when they see it in their own programs.

An individual-configured version of the same session keeps the same arc: case preparation, analysis, extraction. Each participant analyzes the case against their own coaching business, with the workshop leader rotating between them as a Socratic questioner. The extraction at the close names the patterns that emerged across the individual analyses and points each participant toward the specific diagnostic question their own business is ready to answer.

How It Differs From the Other Methods

• From Problem-Based Learning: Case-Based analyzes a resolved scenario by looking back at it; Problem-Based solves an unresolved problem by working forward. Case-Based draws principles from what happened; Problem-Based generates principles by working through what has not yet been decided.
• From Project-Based Learning: Project-Based produces a tangible artifact the participant will use; Case-Based produces pattern recognition the participant will apply. A participant can leave Case-Based Learning with no deliverable and still have learned what the method was designed to teach.
• From Inquiry-Based Learning: Case-Based analyzes a specific, already-resolved situation; Inquiry-Based investigates an open question that applies across situations. Case-based looks backward and is bounded by the case; inquiry is investigative and ranges across evidence.
• From Collaborative Learning: Collaborative Learning is defined by the group dynamic itself; Case-Based Learning is defined by the case and runs well in individual configuration too. A case discussion uses group dynamics, but the group dynamic is not what defines the method.
• From Action Learning: Action Learning grounds the learning in the participant's own current, unresolved workplace problem and cycles between acting and reflecting over time. Case-Based Learning uses past resolved scenarios — the participant's or someone else's — for analysis, not live action.
• From Simulation-Based Learning: Case-Based analyzes a resolved scenario by looking back at it. Simulation-Based enacts a scenario prospectively, with participants producing what happens in the moment. Case-based reads what happened; Simulation-Based practices what could happen.

Design Considerations

Case-Based Learning has specific failure modes the design has to account for.

• Choose cases rich enough to reward close reading. A case with three facts and an obvious lesson produces an obvious discussion. The case needs enough detail that reasonable practitioners can disagree about what happened, what the decision-maker should have done, and what carries over.
• Decide deliberately whether to reveal the outcome upfront. The Langdell tradition often holds back the outcome until the end, forcing participants to commit to a prediction before they learn what actually happened. Revealing the outcome upfront shifts the analysis toward why did this outcome follow from those decisions? Both are legitimate designs. The choice should be deliberate.
• Calibrate case familiarity. A case too close to participants' own businesses triggers defensive reading — they put themselves in the decision-maker's seat and lose the ability to analyze clearly. A case too far from their context produces observation without transfer. The sweet spot is similar-but-not-identical: close enough that the patterns apply, far enough that participants can see the situation clearly.
• Match group size to the discussion method. In group configuration, eight to twenty participants is the workable range for a single Socratic discussion. Below eight, the discussion thins; above twenty, the leader cannot call on enough voices to sustain the method. In individual configuration, cap the cohort at what the leader can circulate to meaningfully — typically six to ten.
• Train the workshop leader out of narration mode. The hardest move in Case-Based Learning is letting participants build the reading through their own questioning, rather than telling them what the case means. Leaders who narrate the case's lessons turn the method into a lecture with a case as prop.
• Design the extraction as carefully as the case selection. Without explicit principle extraction at the close, participants leave with observations that apply only to the case itself. The extraction is where the method's durability lives.

Connection to the Guiding Principles

Case-Based Learning activates all seven principles, with particular weight on focused outcomes, honest reflection, and status awareness.

• Active Learning (80/20): Participants are reading, analyzing, taking positions, and defending them for most of the session. The workshop leader's 20% is framing, questioning, and extraction. The discussion does not run if participants do not come in having done the analytical work.
• Autonomy: The participants own their reading of the case. The leader designs the questions and sets the target; the participants produce the analysis. Each interpretation — whether in a group discussion or individual analysis — is the participant's own.
• Purposeful Initiative: A participant who has not prepared the case cannot contribute to the discussion or produce their own analysis. The consequence is visible right away. This is one of the tightest feedback loops in any method.
• Engaged Interest: A well-chosen case is engaging on its own — the unresolved tension of "what should have been done?" holds attention without the leader having to perform. The case itself carries the energy.
• Status Awareness: The workshop leader reads where the analysis is by listening to the quality of the reasoning. Weak reasoning needs a sharper question; over-confident reasoning needs a challenge; quiet participants need a direct prompt. Temperature checks run continuously through the discussion.
• Honest Reflection: Looking back at a case in this structured way is one of the cleanest forms of reflection. Participants look at a decision, see what followed, and revise their judgment. The method makes honest reflection structurally unavoidable.
• Focused Outcomes: The case is chosen specifically to produce the pattern recognition the workshop exists for. A case about client-retention failures builds retention pattern recognition; a case about pricing decisions builds pricing pattern recognition. The outcome drives the case selection.

Case-Based Learning is particularly well-aligned with the PLAN phase of the Workshop Doctor Roadmap — the phase where the workshop leader diagnoses what situation they are actually in before committing to a design. The pattern recognition that case analysis builds is the same pattern recognition the Roadmap's PLAN phase asks the leader to use on their own workshop.

Where this goes next: Case-Based Learning uses specific resolved scenarios to build pattern recognition. The next method shifts the focus from the material being analyzed to the collaboration itself — the group dynamic becomes the method rather than the vehicle. See Collaborative Learning.

Related

Read this next:

• Collaborative Learning — the next method; shifts the emphasis from the material being analyzed to the structure of the collaboration itself

Foundations of this concept:

• What Active Learning Is (and What It Isn't) — the pillar page; the definition Case-Based Learning operates on top of
• The Guiding Principles of Active Learning — the seven principles Case-Based Learning activates with particular weight on focused outcomes and honest reflection
• Problem-Based Learning — the adjacent method; problem-based works forward through unresolved problems, case-based works backward through resolved ones
• Inquiry-Based Learning — the adjacent method; inquiry investigates open questions, case-based analyzes specific resolved situations

Where this leads:

• PLAN — Diagnose Before You Design — the Roadmap phase where the pattern recognition case analysis builds becomes the leader's own diagnostic practice

References

Barnes, L. B., Christensen, C. R., & Hansen, A. J. (1994). Teaching and the case method: Text, cases, and readings (3rd ed.). Harvard Business School Press.

Donham, W. B. (1922). Essential groundwork for a broad executive theory. Harvard Business Review, 1(1), 1–10.

Garvin, D. A. (2003). Making the case: Professional education for the world of practice. Harvard Magazine, 106(1), 56–65.

Langdell, C. C. (1871). A selection of cases on the law of contracts. Little, Brown.