TEAM TREK — COACH TRAINING PODCAST Episode 37:Facilitating the WorkStyle Composition Conversation

EP37 — Facilitating the WorkStyle Composition Conversation in Session 5

The WorkStyle composition conversation is the last piece of the Profile before the team moves into the Plan. Done well, the group leaves with a specific answer to one question: given who we are as a system, where are we most likely to fail? This episode covers how to open the lens correctly — establishing a team composition frame before a single data point is shown — and why that framing move determines everything that follows. You'll get the exact language for naming the gaps directly (including the Healthy Conflict conversation that most coaches soften), how to read the room when the numbers land, how to manage the moment a minority-type participant starts naming something they've never been able to name before, and how to close the conversation with a specific team commitment rather than a general intention. Also covers the individual coaching bridge — how to plant the seed for the one-on-one sessions that follow Session 8 without derailing the group conversation.

Keywords: workstyle facilitation, team composition, healthy conflict, culture by design, session 5, group coaching, workstyle types, HPT principles, individual coaching

Transcript

SPEAKER_00 0:00

Team Trek Coach Training Podcast Episode thirty seven Facilitating the Workstyle Composition Conversation The previous episode was about reading a group work style composition before you walk into the room. This one is about what happens when you walk in. The work style composition conversation is the last piece of the profile before the team moves into the plan. Done well, the group leaves with a specific, honest answer to one question. Given who we are as a system, where are we most likely to fail? Done poorly, it becomes a group personality exercise, interesting in the moment and forgotten by the next session. The difference is entirely in how you open. Before you show the composition data, before you show anything, you have to establish what this lens is for. Work style type is one of the most misused tools in organizational development. Because when people see their type, their instinct is to explain themselves. I'm a stabilizer. That's why I need more notice before a big decision. I'm an improviser. That's why I don't love long planning meetings. That's not wrong, but in a group session, that conversation goes nowhere useful. It becomes a round of type based self-justification, and it takes the focus from the team as a system to the individuals within it. So before you show anything, you say something like this. What you're about to see is a team composition portrait. We're not asking who you are as a person. We're asking what this group collectively brings, and where this group is collectively likely to struggle. The unit of analysis is the team, not the individual. Hold that frame as we look at the data. That one framing move changes everything that follows. It gives the stabilizers permission to look at their majority pattern honestly, rather than defending it. It gives the minority type members permission to see their position in the distribution as a team level data point, rather than a personal vulnerability. And it creates the conditions for a strategic conversation rather than a personal one. When you show the type distribution, let the numbers land before you interpret them. Put up the composition summary. Whatever form it takes, a table, a simple count, six stabilizers, one connector, one strategist, one improviser, one pending, and then stop. Before you say a word about what that means, watch the room. Because the first reaction is data. If people look unsurprised, if the response is yep, that makes sense, you're working with a team that has some self awareness about its composition. If people look surprised, especially the non stabilizers, who may have suspected they were different, but perhaps didn't know the team was this homogeneous. That reaction is important. It's the moment of recognition you need to be ready for. If the stabilizers look comfortable and the connector, strategist, and improviser go quiet, that itself tells you something about how those voices operate in this room. You don't name what you're noticing. You hold it. And then you ask the opening question. Before I tell you what this distribution means, what does it mean to you? What does this picture explain about how this team operates? That question almost always produces one of two things. Either the group recognizes a specific pattern immediately. That explains why our meetings always feel so consensus driven. That explains why we resist changing things that aren't working. That explains why we're so good at execution and so slow at strategy. When that happens, when the group generates its own insight from the data, your job is to amplify it and make it specific. Give me an example, a real one from the last six months, where that pattern showed up. Concrete examples are the difference between insight and noise. Keep pushing for specifics. Or the group stays politely puzzled. The numbers don't immediately map to anything they recognize. When that happens, don't panic. Move to the type profiles, walk through what each type brings at a team level, what each type's predictable HPT risk is, and then ask the recognition question again. Now that you've seen the profiles, where do you see this in your own team? The second time, you almost always get traction. Here is the most important conversation in this session. Not the strengths, not the type profiles, the gaps. When you get to the point of naming what's structurally missing or underrepresented in this team's composition, that is the conversation that connects everything. And here's how to enter it. I want to name something that the data shows clearly. This team has one confirmed connector, in a group of eleven. That means the natural instinct to monitor the relational health of this team, to hold cohesion as a strategic priority, to notice when something is fraying before it breaks. That instinct is not something this group has in abundance. It's something this group has to build deliberately. Stop there. Let it land. Don't immediately offer the solution. Don't pivot to here's what you can do about it. Let the team sit with the structural reality for a moment. Then ask, what specific structures would this team need to build to compensate for what its composition doesn't naturally provide? Structures, not intentions, because intentions without structures don't survive the first difficult quarter. Soon now the healthy conflict conversation This is the one I want you to prepare for specifically, because it is the most important and the most likely to get softened in the room. When you have a stabilizer dominant team, artificial harmony is not a risk, it is a prediction. And naming it directly, naming it as a structural tendency that this team, because of its composition, is likely to default to under pressure, is the single most valuable thing you can do in this segment. Here is how you might say it. There is one HPT principle that this team's composition makes structurally vulnerable. Not because of any individual's failings, because of what happens when the majority types' natural instincts compound each other in a room. That principle is healthy conflict. Stabilizers, and this team is sixty seven percent stabilizer, have a natural pull toward harmony maintenance. When six people in a room share that pull, the pressure toward artificial consensus is enormous. It doesn't look like cowardice. It looks like everyone getting along, and it costs the team the productive conflict that generates the best decisions. Then ask, what decisions has this team made in the last year that felt like consensus? But where, if you're honest, the real disagreement never surfaced? That is a hard question. Let it be hard. There's a watch for I want to name for this conversation, the group moving from we need to get better at conflict to general agreement, without anything specific attached. This is the most common failure mode in the work styles facilitation. The team acknowledges the gap. Everyone nods. There's a moment of collective recognition. And then the session ends with a general sense that we should address this. That is not a commitment. That is an intention wearing a commitment's clothes. Your job is to push through the general agreement to the specific. Getting better at conflict is not a discipline. A discipline is something observable, something someone could see you doing differently in the next meeting. What specifically are you going to do? In what context, with what frequency, and who is going to hold you accountable to it? Push until you get a real answer. Because the culture strategy this team builds in sessions seven and eight will only be as honest as the conversations they had in sessions three through five. If the work style conversation ends in comfortable generalities, the culture strategy will too. Before you close the work style segment, there's one more thing to do. Plant the seed for the individual coaching session. The CBD guide calls for a sixty minute individual coaching session after session eight for each participant. That session uses both the work style profile and the personal inventory data together. The group session is not the place for that depth, but it is the place to name what's coming. Something like this. What you've looked at today is the team picture. There's also an individual picture, how your specific type and subtype shows up in this team's composition, and where your personal development work connects to the team's strategic gaps. That conversation happens in your individual coaching session. For now, I want you to carry one question into that session. Given what you know about this team's composition and where it's most likely to struggle, what is your specific role in either reinforcing the problem or being part of the solution? That question bridges the group work to the individual work in a way that makes the individual coaching session feel necessary, not supplemental. Every part of this conversation, the composition overview, the type profiles, the gaps, the HPT mapping, the closing commitment, is in service of one question. Given who this team is, what is it going to have to build deliberately to become who it needs to be? Let that question be your anchor. When the conversation drifts toward personality discussion or type trivia, return to it. That question, given who we are, what do we have to build deliberately? That is the bridge from the profile to the plan. The group PI told the team who they are behaviorally. The group work style composition told the team what their natural strengths and structural vulnerabilities look like as a system. The next phase of culture by design, the HPT self-assessment, the culture strategy, the standard, takes everything this team now knows about itself and turns it into specific, accountable commitments. That is the arc. And the quality of what the team builds in sessions six through eight depends almost entirely on whether they came out of sessions three through five having genuinely seen themselves, not the version they preferred. The honest one. Your job in the group PI debrief, in the work style composition session, in every conversation in this arc, is to hold the standard for honest self assessment long enough for it to become the team's own standard. That's the work. And it matters more than any framework, any report, any data point. The data is the door. What they decide to do with what they saw, that's what changes the culture. I want to talk about the energy dynamic in a mixed type room because it's something most facilitation guides don't address directly. When you have a stabilizer dominant team, or any majority type team, there's a natural social gravity in the room. The majority types norms become the default. The pace the majority prefers becomes the meeting pace. The decision making style the majority favors becomes the group decision making style. The kind of conversation the majority finds comfortable becomes the kind of conversation the team has. This is not malicious. It's not even intentional. It's what happens when six out of nine people share similar processing styles and nobody has named the pattern explicitly. What it means for you as the facilitator is this. In a stabilizer majority room, the connector will tend to get heard least when the conversation is fast moving and task focused. The strategist will tend to get heard least when the group wants to preserve harmony. The improviser will tend to get heard least when the group is in careful, process oriented deliberation. You can't fix the team's social gravity in a single session, but you can name it. When you're in the gaps conversation, when you're talking about what the composition is missing or underrepresenting, you can make a direct observation. The research on team composition tells us that in majority type environments, minority perspectives tend to be heard less frequently. Not because they're less valued, but because the social norms of the majority create a default channel that minority types have to work harder to break into. That's not a statement about any individual. It's a structural observation about how group norms form. So the question for this team is what norms do you want to deliberately build to compensate for that? That framing keeps the conversation at the team level. It creates shared responsibility, and it gives the minority type participants something to point to when they need it. A structural observation, not a personal complaint. Let me talk about the moment the facilitation is most likely to go sideways. It's not when you present the healthy conflict gap. That conversation, if you frame it well, usually generates genuine recognition. The moment most likely to go sideways is when the strategist or improviser in the room, the person who has been sitting in a stabilizer dominant environment, possibly for years, possibly experiencing the exact dynamics you're describing, starts to use the session as an opportunity to name something they've never been able to name before. This is not a problem. It's actually a sign the session is working, but it requires careful management. Because if the work style composition conversation becomes a vehicle for one person's legitimate grievance about being unheard in this team, it stops being a group composition conversation and starts being a conflict resolution conversation. Both are important. They're not the same session. So when that energy surfaces and you'll feel it, it comes with a particular quality of intensity, you acknowledge it, you name it as relevant to the structural conversation, and you redirect. That's important. And it's exactly the kind of thing the individual coaching session is designed to go deep on. For right now, I want to stay with the team level question. What does this group need to build to make sure that experience is the exception rather than the norm? That move acknowledges without amplifying. It holds the team level frame, and it creates a legitimate container, the individual coaching session for what needs more depth. There's a coaching principle I want to leave you with as we close this arc. It applies to group PI facilitation, to work style composition facilitation, and to every session in culture by design. The data is not the intervention. The data is what makes the intervention possible. When a team looks at a group PI and sees that seeking feedback scored six point nine one, that number, on its own, does nothing. It might generate a moment of recognition. It will probably generate some explanation, and then it will fade. What doesn't fade is the conversation that number opens. The conversation where someone in the room says I think we've been avoiding the honest feedback conversations because we don't want to damage the relationships. And I think that's actually damaging the culture. That sentence, that moment of honest self assessment spoken out loud in front of the team, that is the intervention. Your job is to create the conditions for that sentence to be said. Every framing decision, every silence you hold, every explanation you gently decline to let replace the signal. Every question you ask that requires specificity instead of abstraction. All of it is in service of that moment. And when it happens, when someone in the room says the honest thing that the data was pointing toward, your job is to receive it without drama. Not to celebrate it. Not to turn it into a breakthrough moment that becomes its own kind of performance. Just to say, that's it, that's the thing. Now, what are you going to do about it? That's the work, and it matters. I want to close this arc with something I think is easy to miss when you're deep in the methodology. The group reports, the personal inventory aggregate, the work style composition, are extraordinarily powerful instruments. The data they produce is specific, honest, and often surprising even to teams that thought they knew themselves well. But those instruments are only as powerful as the facilitation that holds them. Data without a skilled facilitator is just a document. What makes a group PI debrief transformational rather than informational is not the quality of the report. It's the coach's ability to hold the standard for honest self-assessment long enough, through the explanations, the defenses, the polite agreements, for the team to arrive at a genuine reckoning with what the data is actually saying. And what makes a work style composition conversation transformational is not the type distribution. It's the coach's ability to keep the conversation at the level of the team as a system, not the individuals within it, while making the structural vulnerabilities feel personal enough to demand a response. That balance, specific enough to matter, systemic enough not to single out, is the skill this arc has been building toward. You're not walking into these sessions to deliver reports. You're walking in to have the conversations that the reports make possible. And those conversations, when they go to the right depth, change how a team sees itself. A team that has genuinely seen its own gap in two independent instruments from two different angles, and has decided to do something specific about it. That team is not the same team it was before it walked into the room. That's the work. Do it well. In the next episode, we open the culture by design arc, starting with what the full program sequence looks like from the coach's seat, how the diagnostic data from the first three sessions builds toward the culture strategy, and what it means to hold the full picture of an SLT's behavioral, compositional, and environmental data simultaneously as a coach. Thanks for being here.