Lesson 6

Card 0.1: How a Socratic Seminar Works

New to lesson cards? See what a lesson card is.

Before Class Reading: Arguing Like an Engineer

In 1910, engineers argued about whether the Titanic needed more lifeboats. The ones who lost that argument were not wrong; they lost because the room ran on authority instead of reasons. A century later, accident reports from aviation, medicine, and engineering keep finding the same failure: someone in the room knew, and the room had no way to hear them.

A Socratic seminar is a room designed to hear them. The name comes from Socrates, who taught by asking questions instead of announcing answers, but the format matters more than the history. In a seminar, participants sit where everyone can see everyone, speak to each other instead of to the teacher, and follow one rule that changes everything: claims travel with reasons. “The claw failed because we started too late” is a move in the game. “The claw failed” alone is not, and neither is “Jake messed it up.”

This is not a debate. In a debate you defend a side and winning means the other side loses. In a seminar the group is trying to get somewhere together, and changing your mind in public is a respected move, not a defeat. Some of the best contributions are questions. Some are five words long: “What is your evidence for that?”

There are moves you will use constantly. Building: “Adding to what she said…” Challenging the idea, never the person: “I see it differently, because…” Asking for evidence. Naming a pattern: “Three people have now said versions of the same thing.” And the most underrated move in any technical discussion: silence while you actually think.

Why does an engineering class train this? Because every design review, every sprint retro, and the MATE engineering presentation itself runs on exactly this skill. Judges will probe your reasoning in real time, in a room, out loud. Teams that have argued well all year are relaxed in that room. Teams that have not are reciting.

One more thing: the seminar only works if people arrive loaded. A seminar where nobody prepared is just a slow conversation about vibes. That is what prep notes are for, and it is why they are the artifact for every seminar card this year.

Prep prompt (bring in writing): Our first practice seminar topic is “Our claws keep failing. Why?” Write (1) one claim about why, with your reasoning, (2) one piece of evidence from something you personally saw or did on this team, and (3) one question you honestly want the group to take up. Your evidence must be something that happened in our studio or at our pool days; nobody outside this room can write it for you.

Unit: 0, Engineering Process Format: Short instruction, then a live practice seminar Time: 40 minutes (10 minutes on the format, 25 on the practice seminar, 5 debrief) Prerequisites: None. This is one of the first cards of the year.

Core Question

Engineers argue for a living: about designs, tradeoffs, and evidence. How do you have a real discussion where ideas get tested instead of people getting defended, and where the quiet people talk and the loud people listen?

Resource (~10 minutes, in class)

The teacher explains the format, which has only a few rules:

We sit where everyone can see everyone.
You speak to each other, not to the teacher. The teacher asks questions and otherwise stays out.
Claims need reasons or evidence. “I think X because Y” is the unit of speech.
Build on or push against what was just said. “Adding to what she said” and “I see it differently because” are both good moves.
Disagree with the idea, never the person.
Silence is allowed. Thinking pauses are not failures.

Practice Seminar Topic

“Our claws keep failing. Why?” Everyone here has watched or lived at least one claw project run out of time. Bring your honest theory. Possible directions the teacher may probe: Is the problem ambition, planning, skills, or something else? What would a claw project that finishes on time look like from week one? What should this team refuse to attempt this year?

Prep Notes (your artifact, written before the seminar)

One claim about why claw projects overrun, with your reasoning. 2 to 4 sentences.
One piece of evidence from something you actually saw or did on this team.
One honest question you want the group to take up.

Clearing This Card

Participate in the practice seminar with at least one contribution that uses the “claim plus reason” form, and turn in your prep notes. The bar is genuine engagement, not brilliance. Students who find speaking in groups hard can clear by submitting prep notes plus a written response to two things other people said during the seminar.

If You Miss This Class

Seminars cannot be done alone. Write the prep notes for the topic, then join the next scheduled seminar on any topic and clear there. Prep notes for both topics are due.

Why This Matters for Competition

The MATE engineering presentation IS a seminar: judges probe your reasoning and you defend design decisions in real time. Every seminar this year is a rep for that room. It is also how our design reviews will run, so this format is not a school exercise; it is how the company makes decisions.