Socratic Method

---

Origins

The Socratic method dates from fifth-century BCE Athens and the Platonic dialogues. Socrates himself professed to know nothing, and used a relentless sequence of questions to expose the gaps in his interlocutors' confidently-held beliefs.¹ The technique survived into modern pedagogy through law schools, philosophy seminars, and — in the last few decades — through the work of professional coaches who recognized that the question, not the answer, is the most powerful intervention a coach can offer.

For agile coaches, the Socratic method is the antidote to the most common coaching failure mode: telling. A coach who answers questions teaches the team to bring more questions; a coach who asks questions teaches the team to find more answers.

The Core Move

The technique itself is simple: instead of giving a directive answer, ask a question that helps the other person reason their way to one. The questions are designed to do specific work — surface assumptions, examine consequences, generate alternatives, test for evidence. The coach's job is not to extract a predetermined answer; it is to help the team think more clearly.

Useful Question Patterns

A working repertoire of Socratic question types:

Clarification

• "What do you mean by that?"
• "Can you give me an example?"
• "How does that connect to what we discussed earlier?"

Probing assumptions

• "What are you taking for granted here?"
• "What would change if that assumption were wrong?"
• "Why do we believe that's true?"

Examining evidence

• "What evidence supports this?"
• "What would convince you otherwise?"
• "How did you come to that conclusion?"

Considering alternatives

• "What's another way to look at this?"
• "What would someone who disagreed say?"
• "What haven't we considered?"

Exploring consequences

• "If we do this, what follows?"
• "What's the cost of being wrong?"
• "What would have to be true for this to work?"

Reflecting on the question itself

• "What's the real question we're trying to answer?"
• "Why is this important?"
• "What did we learn from working through this?"

Why It Works

• The team builds its own thinking. An answer given is an answer the team has to remember. An answer reasoned out is an answer the team owns.
• Assumptions become visible. The simplest Socratic move — "what are you assuming?" — surfaces the unspoken premises that drive most disagreements.
• The coach scales. A coach who gives answers can advise one team at a time. A coach who teaches teams to ask their own questions multiplies effectiveness.
• It builds psychological safety. Questions imply respect for the other person's intelligence. Telling implies the opposite.

Common Failure Modes

• Socratic-as-interrogation. Questions can be weaponized to corner someone into a predetermined answer. The team feels manipulated. The technique requires genuine openness to where the questioning leads.
• The "I have the answer in my pocket" question. A question asked when the asker already knows what they want said is not a Socratic question — it is a Socratic-looking lecture. Teams detect this immediately.
• Asking when telling would be faster. When the team genuinely lacks specific information the coach has, "what do you think?" is unhelpful. Just tell them. The method is a tool, not a doctrine.
• Too many questions in a row. Three or four questions and a pause work better than ten questions in succession. Volume turns questioning into pressure.
• Avoiding direct feedback. Some coaches hide behind the Socratic method to avoid giving feedback they should give directly. If you need to say "this isn't working," say it. Questions aren't always kinder.

When To Use It

The Socratic method earns its keep when:

• The team has more context than the coach (which is most of the time).
• The thinking process matters as much as the answer.
• The team is capable of reasoning their way to a useful conclusion.
• You want the team to own the answer they reach.

It is the wrong tool when there is genuine information asymmetry (the coach knows something the team doesn't), when time pressure is extreme, or when the team needs reassurance more than reasoning. Recognizing those moments — and switching modes — is part of the skill.

The Quiet Half: Listening

The Socratic method is half questioning and half listening. The questions don't do work unless the asker is genuinely attentive to the answer. Coaches who learn the question patterns but skip the listening end up with a technique that feels mechanical to the team. The active ingredient, more than the questions themselves, is the quality of attention the coach brings to what comes back.

Coaching Tips

Default to questions.

When you're about to answer, pause and ask "what do you think?" instead. The pause alone changes the dynamic.

Be honestly curious.

If you already know the answer you want, you're lecturing, not coaching. Don't ask the question.

Use silence as a tool.

After a question, wait. Don't fill the silence. The first answer is rarely the most useful one — the second, after the pause, usually is.

Don't chain questions endlessly.

Three or four good questions, with real listening between them, beat ten in succession.

Know when to switch to telling.

If the team genuinely needs information you have, just share it. The method is a tool, not a vow.

Track which questions worked.

Keep a small list of the questions that unlocked something. Over time you build your own vocabulary of high-leverage prompts.

Summary

The Socratic method is the slowest-looking coaching intervention available, and one of the most lasting. By trading the immediate satisfaction of giving an answer for the longer-term gain of helping the team think more clearly, it turns each coaching interaction into a small investment in the team's autonomy. Over time, the cumulative effect is a team that needs the coach less — which is, paradoxically, the highest measure of coaching success.

Back to Guided Collaboration