The pedagogy behind Aristotl: Socratic, PBL, spaced retrieval

Most franchise training is built on the assumption that exposing a frontliner to information equals teaching them. Read the policy, watch the video, take the quiz, you are trained. The retention data on this approach is brutal: 70% of the content is gone within a week. Aristotl is built on three evidence-based methods that produce dramatically better retention — Socratic questioning, problem-based learning (PBL), and spaced retrieval. Each one solves a different part of the shift-based training problem. This is one of the few guides in this collection where pedagogy mechanism words are appropriate. The platform's mechanism is the proof point. The other guides talk about completion rates and operational outcomes; this one explains why those outcomes happen. ## Socratic questioning Socratic dialogue is teaching by question, not by lecture. Instead of telling the frontliner "escalate any harassment incident to your manager," a Socratic module asks: "You hear a colleague make an inappropriate comment about a customer. What is your first action?" The learner thinks, picks an answer, sees feedback. The next question builds on the first: "Your manager is on break. What now?" Then: "The colleague becomes defensive when you mention it. What do you say?" The frontliner is constructing the policy through their own decisions, not memorizing it from a slide. The construction process is what produces durable retention. Socratic teaching has 2,400 years of evidence behind it; modern cognitive science just renamed the principle ("generative learning," "productive struggle") and confirmed the mechanism with brain-imaging studies. The shift-work fit: a Socratic exchange is short. Three questions, 90 seconds each. It fits the cadence of a frontliner with 4 minutes between tasks. A 30-minute Socratic seminar is a contradiction in terms — but a 5-minute Socratic micro-dialogue, repeated and varied, builds operational judgment over weeks. ## Problem-based learning (PBL) PBL flips the standard sequence. Standard eLearning: present concept, then apply to problem. PBL: present problem, then derive concept through working it. For frontline training, PBL means starting a module with a real situation: "It is Saturday lunch. The kitchen printer just stopped working. You have 14 orders backed up. What is your first move?" The frontliner thinks through the problem before any procedure is named. Then the module unpacks the procedure as the *answer* to the problem they just struggled with — they remember the procedure because they wanted it. PBL has been the standard pedagogy in medical schools for 50 years (McMaster pioneered it in the 1960s) for the same reason: doctors-in-training remember procedures they applied to a real case better than procedures they read in a textbook. The frontline parallel is exact. A frontliner who derived the right escalation path while solving a hypothetical kitchen-printer crisis remembers it; a frontliner who read the escalation policy in a slide does not. The shift-work fit: PBL modules are scenario-based, which fits the 3-5 minute module length. A single problem, worked through in 4 minutes, with feedback. Better than 30 minutes of policy exposition. ## Spaced retrieval The third leg. Spaced retrieval (covered in detail in its own guide) is the practice of testing recall at increasing intervals — 1 day, 3 days, 7 days, 21 days. It is the most-evidence-supported learning method in cognitive science, and it solves the retention problem that the other two methods alone do not. A frontliner can construct a great answer Socratically and work through a PBL scenario brilliantly, and still forget the underlying principle within two weeks if it is not retrieved again. Spaced retrieval is the maintenance layer. Without it, the initial learning fades; with it, it durably retains. A 60-second retrieval check on the food-safety scenario the frontliner worked through 7 days ago, then again at 21 days, locks the principle in. The platform schedules the checks; the frontliner does the retrievals. The cumulative time investment is minutes; the retention gain is months. ## Why these three together Each method solves a different problem. - **Socratic questioning** builds the initial understanding through active construction — the learner makes the meaning, doesn't receive it. - **PBL** anchors the understanding to a recognizable real-floor situation — the meaning is operational, not abstract. - **Spaced retrieval** maintains the understanding over time — the meaning persists past the week of exposure. Missing any of the three breaks the chain. Socratic teaching alone (no spaced retrieval) creates great in-the-moment understanding that fades. PBL alone (no Socratic dialogue) creates problem-solving but not principle generalization. Spaced retrieval alone (no Socratic or PBL grounding) reinforces the wrong things — facts retrieved without depth. The combination is the difference between a frontliner who can pass a quiz and a frontliner who actually applies the right behavior on a Tuesday lunch shift three months after onboarding. ## Why this fits shift work specifically Classroom training assumes the learner has uninterrupted hours. Standard eLearning assumes the learner has uninterrupted 30-minute blocks. Both assumptions are wrong for frontliners. Shift work cadence — 4-minute windows, six to eight times a day, with cognitive load already on the customer in front of them — demands a pedagogy built for that reality. The three methods Aristotl applies were not invented for franchises. They are 50-year-old (PBL), 100-year-old (spaced retrieval), and 2,400-year-old (Socratic) evidence-based methods that happen to fit the shift-work constraint better than any classroom or e-learning alternative. The platform's job is to deliver them at scale, which is the part that historically required a teacher in the room. AI-assisted authoring and per-learner scheduling close that gap. ## What this looks like in a course A single Aristotl course on, say, customer-recovery interactions might contain: - A 4-minute PBL scenario opening the module with a difficult customer situation, with the frontliner picking their first move from realistic options. - A short Socratic dialogue working through the principle behind the right move — three questions, each building on the prior. - A knowledge check at the end of the module, focused on the decision (not fact recall). - Spaced retrieval checks fired automatically on day 1, day 3, day 7, day 21 — each a 60-second variant of the original scenario. Total cumulative time per frontliner: ~12 minutes over 21 days. Compare to a 30-minute lecture-and-quiz module that produces nothing past two weeks. The pedagogy is the moat. The platform is what makes it operational across 200 locations.

Ready to put this into practice?