JP Dinnell Podcast 133: "Prevent Communication Breakdowns"

Date: April 10, 2026
Hosts: JP Dinnell & Lucas Pinckard
Theme: The Power of the "Read Back" (Reback) to Protect Teams from Communication Failure

Episode Overview

In this episode, JP Dinnell and Lucas Pinckard dive deep into preventing communication breakdowns using the military practice of "read back"—a technique where instructions are repeated back to ensure mutual understanding. Drawing on JP’s extensive SEAL and leadership experience at Echelon Front, the discussion focuses on practical strategies for leaders to gain alignment, eliminate miscommunication, and drive ownership up and down the chain of command—without causing members of their team to feel micromanaged or distrusted.

Key Discussion Points & Insights

1. What is a "Read Back" and Why Does It Matter?

• Definition & Purpose:
  • In the military, after a leader brieifed a plan, someone was asked to repeat key details (timeline, objectives, constraints, priorities) to ensure everybody’s on the same page. The process goes both ways (up and down the chain of command).
  • JP: "When people don't understand, they can't execute. When someone repeats information back, it gives both sides a chance to catch misunderstandings early before time, effort and resources are wasted." [01:00]
• Why It’s Needed:
  • Misalignment leads to mistakes, inefficiency, safety issues, and morale problems.
  • Readbacks are about verifying communication, not a test of trust or attention.

2. Addressing "Trust" and Ego: How to Frame the Read Back

• Bad Framing:
  • If a leader says "Repeat that back to me" with the wrong tone, team members can interpret it as distrust or micromanagement.
• Good Framing:
  • Instead, phrase it as "Just to make sure I communicated that clearly, what are the key takeaways?" or, when speaking up the chain: "Just to ensure I understand your guidance…".
• Responsibility:
  • Shifts from testing others to ensuring your communication is effective. Removes ego, fosters open discussion, and builds team trust.
  • JP: "The read back is a test for whether or not you communicated effectively." [02:30]

3. Making Read Backs a Habit—Not a Pop Quiz

• Implement Gradually:
  • Let the team know in advance that you’ll use read backs—not as a test, but to improve your communication.
  • Rotate who is asked, so it's not always the same person or just the "trusted" team members.
• Benefits:
  • Forces better listening, encourages note taking, increases comfort with asking questions, and builds a positive learning culture.
  • JP: "When it becomes part of your culture, people are comfortable doing it because they understand all the boss wants is alignment so that we can go out there and do our job the right way..." [12:32]

4. When Mistakes Happen: The Leader Owns Communication

• When a team member doesn't get a detail right, the leader takes responsibility—clarifies, reiterates the message, and checks understanding again.
  • JP: "Hey Lucas, I'm sorry, I wasn't clear… The reason why we're starting at 7 is this... I'm sorry, I wasn't clear on that... Remember, what time are we starting? It's not eight, it's what time?" [15:50–16:30]

5. The False Objection: "I Don't Have Time"

• Many leaders skip the read back (or similar verification) because it seems too time-consuming.
• In reality, the time lost to errors, rework, and safety issues is far worse.
  • JP: "[The read back] could take an extra 5, 10, 15 minutes...But I've worked with companies...that the read back has saved them tens and tens, and some hundreds of thousands of dollars." [18:00–21:41]

6. Adapting the Technique to Context and Individuals

• Meeting Length: For a long meeting, do several short read backs at checkpoints, plus a final recap.
• Shy or Struggling Team Members:
  • Start with small asks, coach note-taking, and build their confidence gradually.
  • Always aim to build people up, not embarrass them.
• Everywhere, Not Just Work:
  • Technique applies in business, family, even informal situations (e.g. confirming which restaurant to meet at).
  • Lucas: "Reminders app for the grocery store is a form of read back!" [23:57]

7. Real-Time Assessment & Culture Building

• Read back provides instant feedback on the clarity of your communication.
• Gaps may reveal issues with relationship, trust, or engagement that a leader must address—with humility and ownership.
• Avoid embarrassing or "popping quiz" a team member who struggles in the moment.
  • JP: "If I just go, alright, cool, you don't know, hey Josh, you know...Are you like, man, that was awesome of JP I’m really glad he did that? Not at all." [46:46]

Notable Quotes & Memorable Moments

• "Mistakes are made when people don’t understand all the key pieces of information. And when we look at things through the lens of Extreme Ownership, we always have to bring it back on ourselves." — JP [03:53]
• "The reback should be non-negotiable. It was non-negotiable in the SEAL teams because we wanted to make sure our people were going to be safe and understood right." — JP [13:35]
• "If people are getting multiple things wrong with the brief you just gave, why is that? Were you too vague? Did you give too much information? Were you too complicated with your communication? Man, there’s so many things that we do wrong when we’re communicating." — JP [29:30]
• "If I have somebody that struggles… and they’re not taking notes, I have failed as a leader to not explain to them the importance of taking notes." — JP [32:46]
• On readbacks and team confidence: "Anybody can give one thing. So you give that one thing. I’m like, cool, good to go Lucas. Then I move on to the next person." — JP [39:30]
• On calling out disengaged team members: "Because that’s your ego flaring up and you’re frustrated at them, not at yourself. Instead of saying, 'Hey Lucas, I’m sorry I wasn’t clear,' it’s actually pointing the finger."** — JP [46:01]
• "You don’t have to do it alone. Show humility, ask for help, ask for feedback, receive it with humility and grace." — JP [52:37]

Timestamps for Important Segments

• 00:01 - 03:50: Introduction & reading from Echelon Front’s "Rundown" on the read back
• 05:00 - 06:27: The real-world value of read backs & analogy to meeting minutes
• 06:27 - 12:30: How to frame read backs to build trust and alignment (not suspicion)
• 15:14 - 18:20: How to handle mistakes during a read back (ownership and humility)
• 21:03 - 21:41: Why time invested in the read back pays off much more than the risk of rework
• 22:05 - 24:25: How to implement read backs during long meetings, and in personal life
• 32:46 - 41:16: Coaching shy or struggling team members; lessons on note-taking
• 43:00 - 45:15: Phones, engagement, and overcommunicating your intent
• 45:15 - 47:30: Avoiding public pop quizzes; how to correct without ego or embarrassment
• 52:37: Final advice on fighting complacency, seeking feedback, working as a team

Actionable Takeaways

• Make read backs standard: Announce their use as part of improving your own communication, not to catch others.
• Always own communication errors: If someone misunderstands, go back and clarify. It’s your job.
• Coach & build up your people: Help team members develop skills and confidence. Never use read backs to embarrass.
• Apply read backs everywhere: Family, personal, and professional life all benefit from alignment.
• Combat complacency: Continuous self-assessment and adaptation is necessary—don’t settle for “good enough.”

Tone & Language

Warm, direct, highly practical, and focused on humility, Extreme Ownership, and caring for your people—a tone reflective of both hosts' SEAL background and coaching style.

This episode is a masterclass in practical leadership communication, combining military discipline with deep empathy—a must-listen for anyone looking to prevent costly, frustrating misalignment in any context.