Problem-Based Learning

Problem-Based Learning is a workshop design approach in which the session is built around a complex, open-ended problem that participants work through to solve. The problem is introduced first, before any relevant content is delivered. Participants identify what they need to know, apply what they already know, research what they do not, and propose a solution — and the workshop leader extracts the transferable principles in the debrief.

The approach originated in medical education. Howard Barrows and colleagues at McMaster University Medical School developed it in the late 1960s in response to a pattern common in medical training at the time: students could pass exams on physiology and pharmacology but struggled to reason through an actual patient case. The fix was structural. Reorganize learning around the cases themselves. The method has since spread across engineering, business, law, and professional education. In its original academic form, Problem-Based Learning was group-based — small-group tutorials of five to eight students were central to how Barrows deployed it. Workshop applications are more flexible. The method adapts directly to both group and individual configurations depending on what the session's outcome requires.

Problem-Based Learning places the seven guiding principles into their most demanding configuration. Participants do the cognitive work for the full session, the design structurally requires autonomy, and the problem has to be chosen specifically to produce the capability the session exists for. Method pages that follow describe lighter configurations; Problem-Based Learning is the most cognitively active of the six.

What Problem-Based Learning Is

Four structural components define Problem-Based Learning, independent of whether the session runs group or individual.

• An ill-structured problem. The problem has multiple possible approaches, no single obvious answer, and enough complexity that participants cannot solve it by applying a formula. Ill-structured problems force genuine reasoning; well-structured problems produce exercise.
• Problem-first presentation. The problem is introduced before any relevant content is taught. Participants encounter the problem cold, identify what they know and do not know, and discover the gaps by trying to close them. This is the opposite of the standard sequence, where content is taught first and applied afterward.
• Tutor, not instructor. The workshop leader guides the participant's process without directing their conclusions. The tutor asks questions, surfaces assumptions, and redirects when the reasoning is off-track — and stays out of the content work itself.
• Debrief as the teaching moment. The transferable principles get extracted at the end. The workshop leader names what separated stronger reasoning from weaker, what patterns appeared across the work, and what lessons generalize beyond the specific case.

Group and Individual Configurations

Problem-Based Learning was originally structured as a group process — small-group tutorials of five to eight were central to how Barrows deployed it in medical education — and the group form remains the most widely documented. Workshop applications are more flexible. The method runs in either group or individual configuration, and each produces a recognizable Problem-Based Learning session. They produce different kinds of learning.

Group configuration. Participants work on the problem together in small groups of five to eight. The cognitive work distributes across the group through discussion, division of labor, and collaborative reasoning. The workshop leader circulates between groups as a tutor, asking questions and surfacing assumptions. The group form is the canonical version and fits sessions where the outcome includes the ability to problem-solve collaboratively, or where the problem benefits from diverse perspectives.

Benefits of the group form:

• Diverse perspectives surface assumptions a solo participant would not catch.
• Collaborative reasoning models the group problem-solving participants will use in practice.
• Social accountability keeps each participant engaged through the session.
• Patterns across perspectives produce richer debrief material.

Individual configuration. Each participant works on their own version of the problem, applied to their own context, with the workshop leader circulating as a tutor. This fits smaller workshops, 1:1 coaching, or sessions where the outcome is for each participant to leave with a specific solution for their own situation rather than a group consensus. The leader moves between individual participants the way they would move between groups — asking questions, redirecting, surfacing assumptions.

Benefits of the individual form:

• The participant applies the problem directly to their own context, which activates the self-reference effect and produces stronger encoding.
• No group dynamics to manage — no free-riders, no dominant voices, no overhead on group formation.
• The full cognitive load sits with the participant, which produces faster and deeper engagement with the problem.
• Each participant leaves with their own specific, applicable solution rather than a group consensus.

Choosing the configuration. Group is stronger when the problem benefits from multiple perspectives, when participants can contribute meaningfully to each other's reasoning, and when collaborative problem-solving is itself a target outcome. Individual is stronger when participants are working on their own specific situation, when the cohort is small or the session is 1:1, or when the solution depends on the participant's own context rather than on collective discussion. Hybrid configurations are common — a group-configured problem for shared learning, followed by an individual application where each participant works the same framework through their own context.

When to Use It

Problem-Based Learning fits workshops where the outcome is applied problem-solving in a complex domain — sessions where participants need to develop the judgment to navigate ambiguous situations, not just to execute a known procedure. It is strongest for audiences who bring real expertise and can reason productively through ambiguity, whether working with others or independently.

Good candidates:

• Workshops on strategy, diagnosis, and judgment rather than on skill-execution.
• Participants with enough domain expertise to reason productively.
• Outcomes that require transferring principles across contexts.
• Sessions of 90 minutes or longer.

Less suitable:

• Workshops on procedures or techniques where a clear right answer exists.
• Participants without the foundational knowledge needed to engage with an ill-structured problem.
• Short sessions or introductory content.
• Audiences who expect instruction rather than inquiry.

What It Looks Like in Practice

A 90-minute group-configured Problem-Based Learning session for mid-career coaches working on client retention might run like this:

• Pre-work (30 minutes, done before the session). Participants read a short case summary — a coaching business with a 40% client attrition rate over six months, along with the basic numbers (revenue, cohort composition, offer structure). No analysis, just the facts.
• Problem launch (10 minutes). The workshop leader frames the problem and the desired outcome: by the end of this session, your group will present a diagnosis and three specific interventions for this business. Groups form.
• Group inquiry (50 minutes). Groups work on the problem. The leader circulates, listens for assumptions, redirects when groups skip analysis, and pushes back when conclusions go thin. The leader does not teach content. The leader asks questions.
• Group presentations (20 minutes). Each group presents its diagnosis and interventions. Other groups push back. The leader captures the patterns that appear across presentations.
• Debrief and extraction (10 minutes). The leader names the transferable principles that emerged — what separated stronger diagnoses from weaker ones, what assumptions had to be surfaced, what patterns repeated across groups.

An individual-configured version of the same session keeps the same flow: problem launch, inquiry period, presentation, debrief. Each participant works their own version of the problem — their own client-retention data and business context — and the leader rotates between individual participants the way they would between groups. Presentations become paired exchanges or a whole-room round-robin, and the debrief extracts patterns across individual cases rather than across group conclusions. The participants leave with a diagnosis and intervention plan for their own business, plus the generalizable principles that apply beyond it.

How It Differs From the Other Methods

Problem-Based Learning is distinct from the other five methods in specific ways.

• From Project-Based Learning: Problem-Based is about solving a specific problem; Project-Based is about producing an artifact over extended time. Problem-Based sessions typically run 60–180 minutes; project-based sequences unfold over weeks.
• From Inquiry-Based Learning: Problem-Based starts with a defined problem; Inquiry-Based starts with an open question. Inquiry can range wider; Problem-Based is bounded by the problem's scope.
• From Case-Based Learning: Cases present a resolved scenario for retrospective analysis; Problem-Based presents an unresolved problem for forward solving. Case-based extracts principles from what happened; Problem-Based generates principles by working forward.
• From Collaborative Learning: Problem-Based uses collaboration, but the method is defined by the problem, not the group structure. Collaborative Learning can use many group structures; Problem-Based always centers on the ill-structured problem.
• From Action Learning: Action Learning uses the participant's own current workplace problem and cycles between action and reflection over time. Problem-Based can use simulated or historical problems and is primarily cognitive rather than action-taking.
• From Simulation-Based Learning: Problem-Based works on real or realistic problems and generates solutions. Simulation-Based enacts a specific scenario to practice performance. The material of Problem-Based is the problem; the material of Simulation-Based is the interaction itself.

Design Considerations

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

• Choose an ill-structured problem, not a well-structured one. If the problem has a known right answer, participants will identify it quickly and the session collapses into solving-by-formula. Ill-structured problems have enough ambiguity to require genuine reasoning.
• Calibrate difficulty to participants' expertise. Too easy, and the session becomes exercise. Too hard, and groups get stuck and frustrated. The sweet spot is where participants' current skill falls short by enough that they have to stretch, but the gap is reachable.
• Build in time for non-linear thinking. Problem-Based Learning does not run on a neat timeline. Groups go in circles, backtrack, rebuild. Compressing the time kills the method.
• Match the configuration to the participant load. In group configuration, cap group size at five to eight — larger groups produce free-riders; smaller groups lack diversity. In individual configuration, cap the total session size at eight to twelve — above that, the workshop leader cannot circulate to every participant often enough to keep the tutor role functional.
• Train the workshop leader out of content-delivery mode. The hardest move in Problem-Based Learning is staying silent when you know the answer. Leaders who keep teaching mid-session undo the method. Questions are the only intervention.
• Design the debrief as carefully as the problem. Most of the generalizable learning gets consolidated in the debrief. A weak debrief means participants leave with one case's insights rather than transferable principles.

Connection to the Guiding Principles

Problem-Based Learning is the most demanding configuration of the seven principles. Every principle is actively engaged.

• Active Learning (80/20): Participants are doing the cognitive work for roughly 80% of the session; the leader's 20% is framing, circulating, and debriefing.
• Autonomy: The participants own the inquiry and the conclusions — whether working in a group or individually. The leader designs the path; the participants walk it.
• Purposeful Initiative: The problem itself creates initiative. In group configuration, participants who do not engage cannot contribute to their group. In individual configuration, they cannot produce an outcome of their own. Either way, the natural consequence is visible.
• Engaged Interest: Authentic problems produce intrinsic engagement. Participants care because the problem is recognizably real — and even more so in individual configuration where the problem is applied to their own context.
• Status Awareness: The leader reads the room by circulating between groups or between individuals, listening to reasoning, and catching when participants go thin. Temperature checks are continuous.
• Honest Reflection: The debrief is the reflection moment. It surfaces what participants got right, what they missed, and why.
• Focused Outcomes: The problem is chosen specifically to produce a capability — the outcome drives the problem selection, not the other way around.

Problem-Based Learning activates all seven principles simultaneously. The other five methods configure the principles differently, foregrounding some more than others. Problem-Based is the reference point against which the other methods can be calibrated.

Where this goes next: Problem-Based Learning centers the session on one complex problem to solve in real time. The next method extends the timeline and shifts the emphasis from solving to building an artifact over multiple sessions. See Project-Based Learning.

Related

Read this next:

• Project-Based Learning — the next method; extends the timeline and shifts the focus from solving to building

Foundations of this concept:

• What Active Learning Is (and What It Isn't) — the pillar page; the definition and mechanisms Problem-Based Learning operates on top of
• The Guiding Principles of Active Learning — the seven principles Problem-Based Learning activates in their most demanding configuration
• Warm vs. Cold Information — the principle the pre-work case summary is built around
• The 80/20 Workshop Engagement Ratio — the structural ratio Problem-Based Learning pushes to an extreme

Where this leads:

• DESIGN — Architect the Experience the Participant Will Move Through — the Roadmap phase where Problem-Based Learning becomes session architecture
• DELIVER — Facilitate Like a Coach — the Roadmap phase where tutoring replaces instructing in real time

References

Barrows, H. S., & Tamblyn, R. M. (1980). Problem-based learning: An approach to medical education. Springer.

Hmelo-Silver, C. E. (2004). Problem-based learning: What and how do students learn? Educational Psychology Review, 16(3), 235–266.

Savery, J. R., & Duffy, T. M. (1995). Problem based learning: An instructional model and its constructivist framework. Educational Technology, 35(5), 31–38.