TEAM TREK — COACH TRAINING PODCAST Episode 35: Facilitating the Group PI Debrief — The Honest Mirror in Practice

EP35 — Facilitating the Group PI Debrief: The Honest Mirror in Practice

You've read the data. Now you're in the room. This episode walks through the full group PI facilitation — from the opening frame that determines whether the data lands or gets explained away, through the strengths conversation (why it's anchoring, not warming up), into the growth areas segment where most coaches get tentative. You'll get the exact language for holding the standard when explanation creep starts ("context explains the score — it doesn't change the gap"), specific facilitation approaches for the five highest-impact behavioral items, and how to run the Part Two segments so that agency data generates ownership and environment data generates action rather than resignation. The episode closes with the Diagnostic Triangle as a facilitation move — and why the session must end with a specific behavioral commitment, not just a diagnosis.

Keywords: group PI facilitation, honest mirror, group debrief, culture by design, explanation creep, feedback culture, agency, work environment, coaching facilitation

Transcript

SPEAKER_00 0:00

Team Trek Coach Training Podcast Episode thirty five Facilitating the Group PID Brief The Honest Mirror in Practice In the last episode we talked about how to read a group PI before you walk into the room. Today we're in the room and the difference between a group PID brief that produces real movement and one that produces polite discussion and then nothing. That difference is almost entirely determined by what you do in the first five minutes. So let's start there. Before you show a single number, you need to establish one thing. What this data is for, not what it is, what it's for. Because when you put group scores in front of a leadership team, their instinct, especially a high performing leadership team, is to manage it, to explain it, to contextualize it. Well, that score is low because of the quarter we just had. We've been through a lot of change. That explains the feedback number. That's not really how we operate. That was a specific situation. You will hear all of these, probably in the first fifteen minutes. And none of them are wrong. Context is real. But context is also the primary mechanism by which teams avoid sitting with what the data is actually telling them. So before you show the first table, you say something like this. What you're about to see is not a judgment, it is a snapshot. The most honest picture we have right now of where we are as a team and as a culture. The goal is not to explain it, the goal is to see it clearly. Because you cannot build a culture strategy on top of a version of reality that is more comfortable than true. Say that. Mean it. Then show the numbers. The strengths conversation is where you establish the tone for everything that follows. Occasionally, we move through the strengths too quickly. We show the top scores, make a few affirmations, and move on to the growth areas, which is where we think the real work is. That's a mistake. The strengths conversation is not just acknowledgement, it's anchoring. When you show a group that their highest scoring behavior is honesty and integrity, say it landed at nine point three six out of ten, and you spend three minutes helping them understand what that actually means about who they are. You're not warming them up for the hard conversation. You're building the foundation the hard conversation has to stand on. Because when you get to growth areas twenty minutes later and someone feels exposed, what grounds them is the memory of what they heard about their strengths. They're not a team that lacks integrity. They're a team with deep integrity, that is underinvesting in a specific set of daily practices. That reframe only works if the strengths conversation landed first. So when you present the top cluster, don't rush. Ask this. Before we talk about what these numbers mean strategically, I want to hear from you. Where do you actually see these behaviors showing up in your culture? Not in your best moments, but in your ordinary ones. That question does two things. It makes the strengths concrete, not abstract. And it begins to surface the difference between aspiration and practice, which is exactly the tension you need alive in the room when you get to growth areas. The growth areas segment. This is where most coaches get tentative. And I want to name why, because it matters. When you put a list of low scoring behaviors in front of a leadership team, you are implicitly telling them this is where you are failing. Even if you've done the reframe, even if you've said these are signals, not indictments. The data still lands that way for some people in the room. And when it does, the default response is defensiveness, which wears the costume of explanation. Your job is not to make that defensiveness go away. Your job is to hold the standard long enough for the group to move through it. Here's the move. When someone explains a low score, you acknowledge the explanation and return to the data. I hear that. And what does it tell us that this team scores here in this context right now? That one sentence is the most important thing you can say in the growth areas segment. It says, I'm not dismissing your context, and I'm not letting the context replace the signal. Now, let's talk about the specific items that almost always generate the most important conversations. Seeking constructive feedback. This is typically the lowest item in a group PI for a senior leadership team. And it's the most important item in the whole data set. Not because it's surprising, because of what it means at the leadership level. When a senior leadership team doesn't seek constructive feedback from each other and from the people below them, the feedback culture of the entire organization takes its signal from that. The people watching this team are learning what is safe. And if they see leaders who project confidence, make decisions, and rarely publicly ask for honest pushback, they learn that feedback is not something safe to give upward. So the question you want to ask is not why is this score low? The question is if the people you lead were rating how safe it feels to give you honest feedback, what would they say? And what have you done in the last quarter that produced that answer? Let that sit. Don't rescue it with a follow up question too quickly. The silence after that question is productive. Actively listening for understanding and seeking facts before reacting. These two items belong together. And when both score below the team average, what you're seeing is a group that is operating in reactive mode more than it realizes. Not because they don't value listening, they probably believe they're good listeners. Most leaders do. But there's a difference between waiting for your turn to speak and listening to understand. And when you combine low listening scores with low fact seeking scores, the picture is specific. This team moves fast, trusts its own read of situations, and sometimes makes the decision before the data is fully in. The question that opens this conversation give me a real example, not hypothetical, of a moment in the last six months when this team acted on assumption and paid for it. Real examples, not abstractions, because abstractions allow the group to stay comfortable. Real examples require them to see themselves. Speaking well of others This one tends to generate the most discomfort, because it's not about how people behave in the room, it's about how they talk when the other person isn't there. A score below seven point five on this item for a senior leadership team usually means one of two things. There is a pattern of critical commentary about colleagues in private, the kind of thing said in offices after a difficult meeting, or inside conversations before one. Or there is a pace driven inattention, where the relational affirmations that build connection simply don't happen because the team is always on to the next thing. Either way, the cost is the same. People feel the absence of trust deposits even when they can't name the specific transaction that was missing. The question What is the norm on this team for how we talk about each other when the other person isn't in the room? And if someone asked the people who work for us, what would they say about how this team talks about each other? Now, let's talk about part two. I want to be direct about the agency segment, because there's a facilitation trap that coaches can fall into. When the agency data surfaces, when you show the group that a meaningful portion of them agreed with, I often feel that what happens at work is mostly determined by other people or things outside my control. The instinct is to turn it into a coaching conversation about mindset. Don't. Not here. Not in a group setting. Because agency in a leadership context is not primarily about individual mindset. It's about what this team models. The framing that unlocks this conversation is not here's where some of you have a fixed mindset. The framing is whatever this team models about ownership, your people are watching and learning. So the question is not just whether each of you believes in agency, it's whether the culture you're building makes agency feel possible for the people around you. That shifts the conversation from individual introspection to collective responsibility. And collective responsibility is what you need to be building in this session. The environment segment operates differently. When you show low environment scores, specifically the feedback item, which often surfaces as the lowest single score in the entire data set, you need to name clearly that this is a structural finding before you show it. These items don't measure what you personally need to work on. They measure what the organization is currently providing. A low score here is a call to leadership action, not a personal development assignment. So as you look at these numbers, the question I want you holding is what are we going to build? Then show the data. Then wait. Because what happens in the room after a group sees that their own feedback score is below five out of seven, that reaction tells you more about the team's culture than the score itself. And then you close the diagnostic triangle. Three questions, not as slides, as a conversation. Who are we behaviorally measured against the standard we say we want to build? What does our environment communicate to our people about whether full engagement is safe? And how are we showing up as agents, as people who own our direction? Or are we absorbing circumstances rather than changing them? The gap between the honest answers to those three questions is the culture this team actually has right now. Your job is to make sure they feel that gap. Not to close it for them. Not to reassure them that they're almost there. To make sure they feel it. Clearly, honestly, without the comfort of explanation. Because the discomfort of that gap is the fuel for everything that comes next. One final thing. Don't let the session end in diagnosis. This is the most common mistake in a group PID brief. The data lands. The conversation goes deep. People feel the gap. And then the session ends. And nobody has named a single specific thing they're going to do differently. Diagnosis without commitment is just sophisticated self-awareness. Before you close, you ask, based on everything we've looked at today, what is one specific behavior each of you is going to practice differently before our next session? Not a resolution, a behavior, something observable, something someone else could see. It doesn't have to be big, it has to be specific. That specificity is the beginning of the culture change, not the data, not the conversation about the data. What they decide to do with what they saw. Let me spend a moment on something that doesn't get enough attention in facilitation training. The silence. There are three or four moments in a group P I debrief where the right move, the most powerful coaching move available to you, is to say nothing. The first is right after you show the growth areas. After the table is up, after you've named the pattern, you stop. You don't pivot to a question. You don't fill the air. You let the data sit in the room. Because the first thirty seconds of silence after a difficult data presentation are doing work. The group is integrating what they're seeing. They're comparing it against their own experience. They're deciding whether to acknowledge it or explain it. If you fill that silence too quickly, you make it easier for the group to skip the integration and go straight to the explanation. Hold it. The second silence that matters is after you ask a real question, not a rhetorical question, a real one. Like if someone who recently left this organization were rating this team, would they score it the same way? That question is designed to create discomfort. Let the discomfort breathe. The instinct, especially for coaches who want to be supportive, is to soften the question after they ask it. To add a qualifier or to nod encouragingly or to provide the answer they're looking for. Don't. The discomfort is the point. The discomfort is where the honest conversation starts. Let me talk about what I call explanation creep, because it's the primary obstacle in a group P I debrief. Explanation creep is when a team gradually replaces honest self-assessment with contextual justification. It starts with one person offering a reasonable explanation for a low score. The feedback score is low because we went through a leadership transition last year. Things have been unsettled. That explanation is probably true. And because it's true, it creates space for the next explanation. The listening score is low because we're under so much pressure. Everyone's moving fast. Also probably true. And then the speaking well of others score honestly, some of that is just how we're wired. We're a direct team. We say what we think. By this point, the data has been fully contextualized. Every low score has an explanation, and the team has successfully managed its way around the actual signal. The antidote to explanation creep is not arguing with the explanations. Every single one of them might be accurate. The antidote is returning to the question that context cannot answer. All of those things may be true. Here's what I want to ask. Given all of that, given the transition, the pressure, the pace, what does it tell us that this team lands here right now on these specific behaviors? What does that signal about what this team needs to build? Context explains the score. It doesn't change the gap. Keep that distinction live in the room. There's a version of the group P I debrief that I want you to be able to imagine clearly, because it's the version you're building toward. It's the version where twenty minutes into the growth area's conversation, someone in the room says something like this. I think we all know that we don't actually have the hard conversations with each other. We're good with our people. We take care of each other. But when it comes to calling each other out on the team's own standards, we don't do it. When that happens, when someone in the group names the real pattern in their own words, without you having to name it for them, that is the moment the session turns. Because now the diagnosis doesn't belong to the data. It belongs to the team. And a team that owns its own diagnosis is a team that can build a strategy for changing it. Your whole job in the first forty minutes is to create the conditions for that moment. Everything you do, the framing, the anchoring on strengths, the patient navigation of explanation creep, the willingness to hold silence, is in service of that one sentence from someone in the room. When it comes, your job is to reflect it back, name it clearly, and ask, what are you going to do about it? Not someday. Not in the strategy document. Before the next session. There's a question I get fairly often about group PI facilitation, and I want to address it directly. The question is what do you do when someone in the room clearly has much lower scores than the rest of the group? And they know that you know it? First, the participant facing group PI report contains no individual scores. The group doesn't know who scored what. They only know the group averages. But the individual in question knows their own scores. And if they completed the PI honestly, they have a rough sense of where they stand relative to the group, even without seeing the comparison. As the facilitator, you're carrying that knowledge too. But you're not using it publicly. Your job is to hold it as context for how you read the room, not as data to deploy in the session. Here's what that looks like in practice. If someone with notably lower scores is quiet during the growth area's conversation, if they seem disengaged or withdrawn when the group is examining the behaviors where they scored lowest, you don't draw them out by asking about their experience specifically. You draw out the group by asking a question that anyone could answer. Who in this room has experienced a moment where a team member's feedback landed harder than intended? Where the directness was real, but the care wasn't visible. What did that cost the relationship? That question creates an opening for anyone to contribute, including the person who may be most feeling the gap in that moment. The most effective thing you can do for the individual with lower scores is create a session where honest self-assessment is safe for the whole group. Not a session where they feel singled out. That's the art of it. In the next episode, we shift from the personal inventory to work styles, specifically how to read a group work style composition report, what the type distribution tells you about a team's natural strengths and structural vulnerabilities, and how to use that portrait to anticipate exactly where this team's culture strategy is most likely to succeed and most likely to fail. Thanks for being here.