Episode 29: Types in Relationship

Episode 29: Types in Relationship Every coaching engagement involves at least two types in relationship — and some combinations create predictable tension while others create remarkable synergy. This episode maps the cross-type dynamics coaches encounter most often, explains why certain pairings struggle with trust even when both parties have good intentions, and gives coaches the language to name those dynamics and help teams work through them. 

Transcript

SPEAKER_00 0:00

Team Trek Coach Training Podcast Episode twenty nine Types in Relationship twenty eight episodes four types sixteen subtypes At this point in the series you understand what each type brings. You understand their superpowers and their kryptonite. You understand how trust forms and erodes for each one. You know the coaching moves that reach them, but you've been learning about them one at a time. In real organizational life, types don't operate in isolation. They operate alongside each other. In meetings, in teams, in reporting relationships, in partnerships that work brilliantly and partnerships that quietly grind everyone down. And the friction that generates the most coaching work, the tension that shows up in almost every engagement, in almost every team, is usually not about bad intentions. It's about different wiring meeting itself without a common language. This episode is about that friction. We're going to walk through four cross-type pairings, not all possible combinations. There are too many to do justice in a single episode. But four pairings that coaches encounter constantly, that produce predictable and recurring tension, and that become navigable once you understand what's actually happening underneath the surface. Two pairs share common ground that makes the relationship workable, and brings its own specific kind of tension. Two pairs lack that common ground entirely, and produce a specific kind of friction that is often misread as conflict when it's really just difference. Let's start with the pairs that share common ground. The first pairing is the connector and the stabilizer. These two types don't seem obviously similar. The connector is relational, values driven, and oriented toward people and meaning. The stabilizer is process oriented, reliability focused, and oriented toward structure and commitment. Different trust lenses, different core drives, different definitions of a good day. And yet these two types tend to work better together than almost any other cross type combination. Because underneath the surface differences, they share something foundational. They are both collaborative. The connector believes that how work gets done matters, that the relationships and the culture are not peripheral to the mission, they are part of it. The stabilizer believes the same thing, expressed differently. How work gets done matters to a stabilizer too. Whether commitments were honored, whether standards were met, whether the team showed up for each other the way they said they would. Both types are investing in something beyond the immediate deliverable. Both types care about the team as a team. Both types are paying attention to the human beings doing the work, not just the work itself. That shared orientation creates natural common ground. Connectors and stabilizers often find each other trustworthy in ways that feel almost immediate. Not because they understand each other's wiring, but because they recognize something familiar in each other's investment in the people around them. And then the tensions emerge. The first tension is about people versus process. The connector's primary investment is in the relational dimension of the team. When something goes wrong, when a conflict surfaces, when someone is struggling, when the culture starts to feel off, the connector moves toward the human dimension first. What is the relational rupture underneath this situation? How are people experiencing this? What does the team need to feel safe enough to work through it? The stabilizer moves toward the structural dimension first. What was the process that broke down? What was the commitment that wasn't honored? How do we restore the standard and ensure this doesn't happen again? Both of those are right. Both of those are necessary. But in a room where both types are present, they can feel like opposing priorities. The connector experiences the stabilizer's move toward process as emotionally premature. We haven't dealt with how this landed for people yet. Why are we already talking about the documentation? The stabilizer experiences the connector's move toward the relational dimension as structurally incomplete. We've talked about how everyone is feeling. Now how do we make sure this doesn't happen again? Neither of them is wrong about what the situation needs, but the sequence matters to each of them, and the sequence they prefer is different. The coaching move for this tension is straightforward and worth naming explicitly in a team context. These are not competing priorities, they are sequential ones. The relational repair that the connector is attending to is what makes the structural repair the stabilizer is proposing actually hold. You cannot enforce a new process in a team where the relational rupture underneath the breakdown hasn't been addressed, and you cannot leave a relational rupture unstructured indefinitely without it becoming chronic. What the connector and the stabilizer need from each other is sequence acknowledgement, not one giving way to the other, both contributing in the right order. The second tension is about the time horizon of accountability. The connector's relationship with accountability tends to be present oriented and relational. Did the team feel supported through this? Are people growing? Is the culture reflecting our values right now? The stabilizer's relationship with accountability tends to be process oriented and historical. What was committed to? Was it delivered? Did the standard hold? These orientations are not in conflict, but they can produce a recurring disagreement about what accountability actually looks like in practice. A connector leader who holds a team member accountable through a growth conversation, focusing on what this person needs to develop and how the team can support them, may look to a stabilizer colleague, like they are softening the standard. That's not accountability. Accountability is naming what was committed to, naming what wasn't delivered, and being clear about what changes. A stabilizer leader who holds a team member accountable through a clear expectations conversation, naming what was promised, what happened, and what must be different going forward, may look to a connector colleague like they are being punitive. That conversation didn't create safety. They're going to be more defended next time, not more capable. Both of those observations are likely partially correct, and both leaders are missing what the other brings. The connector's growth-oriented accountability tends to build the long-term capability of the person being held accountable, but can leave them unclear on the immediate standard. The stabilizer's commitment-oriented accountability tends to restore the standard immediately, but can leave the person without the developmental support that would help them meet it more consistently. The Connector Stabilizer team that understands this dynamic can divide the work productively. You handle the relational safety. I'll name the commitment clearly. Together we produce an accountability conversation that is both clear and developmental. That is a form of cross-type collaboration that produces something neither type achieves alone. The third tension between connectors and stabilizers is about change. Connectors tend to welcome change when it serves people or values. If a new approach would better support the team's well being, better align the culture with its stated values, or better serve the mission. The connector moves toward it. The human case for change is usually sufficient. Stabilizers tend to require a stronger evidentiary case. Not because they don't care about people, they do, but because their instinct is to protect what works, and the default assumption is that the proven approach is more reliable than the untested one until evidence suggests otherwise. In a change management context, this tension is constant. The connector is ready to move. We've talked about this enough. People are ready. The culture is aligned. Let's go. The stabilizer is not ready. We haven't fully tested this, we don't know what we'll lose. We need more time. And here is the thing about that tension that coaches need to hold clearly. Both of those instincts have organizational value. The connector's willingness to move on a values aligned direction prevents paralysis. The stabilizer's caution prevents the catastrophic implementation failures that happen when organizations change faster than their systems can absorb. The friction between them is not a problem to be resolved. It is a check that produces better decisions. The connector who has a stabilizer asking hard questions about implementation before launch will produce a more durable change. The stabilizer who has a connector maintaining the relational case for change will find the organization more genuinely committed to the new direction. What they need from each other is not consensus. It is patience with the other's contribution to the quality of the outcome. Now let's turn to the second pairing with common ground the strategist and the improviser. These two types also don't seem obviously similar. The strategist is long range, analytical, and precision oriented. The improviser is present focused, action oriented and adaptability driven, different trust lenses, different definitions of rigorous, different tolerances for ambiguity, but they share something that the connector and stabilizer don't share. A fundamentally utilitarian orientation to the work. Both types are oriented toward what works. Both types evaluate options through a results and competence lens. Both types are, at their core, more interested in whether something produces a good outcome than in how it felt to get there. The strategist and the improviser trust each other based on similar signals, demonstrated competence, intellectual honesty, the ability to deliver on what was promised. Where the connector and stabilizer share a collaborative frame, the strategist and improviser share a performance frame. That creates common ground, and it creates a very specific kind of tension. The first tension between strategists and improvisers is about the time horizon of planning. The strategist's natural planning horizon is long. They think in scenarios, in contingencies, in the downstream implications of decisions being made today. They are most comfortable when the path is designed with enough rigor to hold up under pressure. They trust plans that have been stress tested. They are skeptical of plans that were made quickly. The improviser's natural planning horizon is short. They trust their ability to read conditions in real time and adjust accordingly. They are most comfortable when they have the freedom to respond to what is actually happening rather than what was predicted. They are skeptical of plans that lock in a direction before the real conditions are known. In a planning meeting, this tension is immediate and recurring. The strategist wants to design the path before committing to it. We need to think through the failure modes. What happens if the conditions change? What's the contingency? The improviser is ready to move. We have enough information to start, we'll figure out the rest as we go. Both of those are reasonable positions, and both contain a genuine organizational risk. The strategist who insists on complete analysis before moving can delay action past the point where the opportunity still exists. The improviser who moves before the analysis is sufficient can create problems downstream that a little more preparation would have prevented. What the strategist and improviser need from each other in a planning context is explicit. The strategist's scenario planning, communicated at the right level of granularity, gives the improviser enough structural confidence to commit. The improviser's real-time intelligence, their read of what is actually happening on the ground, gives the strategist data that no pre-launch analysis could have produced. The tension is not resolved by one yielding to the other. It is resolved by each contributing what the other can't generate alone. The second tension is about communication and process. The strategist's relationship with process is systemic. Process exists to produce better outcomes, more reliably, over time. It is a design tool, not bureaucracy, but architecture. The strategist tends to document their reasoning, to build systems that others can follow, to leave enough trail that the work is reproducible and the learning is retained. The improviser's relationship with process is instrumental. Process is useful when it produces results faster or better than not having it. When it doesn't, when it slows execution, when it adds steps that don't add value, when it substitutes for the real time judgment that would produce a better outcome. The improviser tends to root around it. This produces a recurring friction that is often misread as disrespect. The strategist who has designed a system sees the improviser bypass it and concludes They don't value the work I've done. They think they know better than the design. The improviser who roots around the process sees the strategist's frustration and concludes they care more about the system than the outcome. They're optimizing for the plan, not the result. Neither of those stories is accurate, but both feel true from inside the experience of not understanding the other's orientation. The coaching insight here is important and often missed. The strategist's process exists to produce reliable outcomes at scale. The improviser's bypass of that process is often based on a real time read that the standard approach won't work in this specific situation. Both of those can be correct simultaneously. The strategist's system is right in general. The improviser's judgment is right in this case. The productive question is not whose approach is correct. It is what the improviser saw in the specific situation that made the standard approach insufficient, and whether that information should update the system. When the strategist asks that question genuinely, two things happen. The improviser feels their in the moment intelligence respected rather than dismissed. And the system gets updated with real world data it wouldn't have captured without the bypass. That is the strategist improviser collaboration at its most valuable. The third tension between strategists and improvisers is trust durability. Both types build trust through competence. Both types extend trust based on demonstrated results. Where they diverge is in how they maintain it over time. The strategists' trust is slow to build and durable once established. They evaluate others carefully, extend trust incrementally, and tend to maintain it as long as the competence signals remain consistent. The improviser's trust is fast to build and cyclical by nature. They extend trust quickly based on in the moment performance, and that trust is refreshed through continued presence and action rather than through a sustained track record. This creates a specific mismatch. The improviser extends trust to the strategist based on their early demonstrations of competence. The strategist is still in the evaluation phase. The improviser moves forward with confidence in the relationship before the strategist has fully established it. Then the improviser's attention redistributes to the next challenge, the next opportunity, the next thing that needs them. The sustained presence the strategist was using to continue evaluating simply isn't there anymore. The strategist draws a conclusion. The improviser's early performance was real, but their reliability across time is not. Trust that was partially forming quietly retreats. The improviser, reengaging with their characteristic enthusiasm, doesn't see what happened. From their perspective, the relationship was solid when they last checked in. They don't understand why the strategist seems more guarded. This cycle, initial trust forming, improviser redistributing attention, strategist recalibrating downward, improviser confused by the shift, is one of the most common recurring patterns in cross type relationships that coaches encounter. The development move for the improviser in this dynamic is specific. Sustained presence between high stakes moments. Not every day. But enough regularity that the strategist's evaluation process has the data it needs to continue moving forward rather than retreating. The development move for the strategist is equally specific, naming what they need explicitly rather than withdrawing and waiting to see if the improviser notices. The improviser can meet the need. They tend to have no idea it exists until someone says so. Now let's turn to the two pairings that carry more fundamental tension. Because the common ground is harder to find. Both are overrepresented in leadership, and they are frequently in the same room, often in senior roles, often working on the most consequential decisions an organization makes. The friction between them is not about bad faith. It is about first filters. When the strategist approaches a decision, the first question they ask is, what is the most logically sound answer? What does the analysis show? What is the most efficient path to the correct outcome? When the connector approaches the same decision, the first question they ask is, how will this land for the people affected by it? What is the human impact? What does this communicate about our values? Both of those are the right questions. They are just asked in a different order. And in a room where a decision needs to be made, the sequence matters. The strategist who has completed the analysis and arrived at the correct answer, experiences the connector's human impact questions as delay. We've done the analysis. We know the right answer. Why are we reopening it? The connector, who is still processing the relational implications, experiences the strategist's impatience as dismissal. We haven't talked about how this affects the team yet. Why are we rushing to close? Neither person is wrong. Both questions are necessary, and both are frustrated by the other for asking the right question at the wrong time. The trust gap here is significant. The strategist trusts the connector's care for people, but may question their analytical rigor. They always make it relational. Sometimes the correct answer isn't the most comfortable one. The connector trusts the strategist's intellect, but questions their investment in people. They've solved the problem on paper. They haven't thought about what it means for the people who live with the decision. Both of those observations are probably partially accurate, and both are missing the other's genuine contribution. The strategist connector team that works well together has usually learned to name the sequence explicitly. The analysis first, the human impact assessment second. Not because one is more important, but because each informs the other. The strategist's analysis tells you what is logically possible. The connector's human impact assessment tells you what is actually sustainable. A decision that is analytically correct, but humanly unsustainable will fail at implementation. A decision that is humanly supportive, but analytically flawed, will fail at outcomes. What the connector and strategist need from each other is not agreement. It is genuine curiosity about what the other's lens reveals that theirs doesn't. The final pairing is the stabilizer and the improviser. This is the most common cross-type pairing in most organizations, and the one that generates the most sustained friction. Because the stabilizer and improviser have different approaches to almost everything that matters in day to day organizational life. How plans are made, how commitments are understood, how change is evaluated, how urgency is defined, how accountability works. The stabilizer's world is structured around commitments honored and standards maintained. When something is agreed to, it is expected to be delivered. When a process exists, it is expected to be followed. Change is evaluated carefully because most things that feel urgent in the moment are not, and the cost of changing direction is often higher than it appears. The improviser's world is structured around real-time conditions and results. When something was agreed to, the underlying goal was agreed to. When a process exists, it should be followed when it serves the outcome and bypassed when it doesn't. Change is embraced because conditions are always changing, and the failure to adapt is more costly than the disruption of changing course. These two worldviews are not just different. They are, in many of their specific applications, directly opposed. The stabilizer who made a plan and committed to it experiences the improviser's midcourse pivot as a betrayal of the agreement, not a strategic adjustment, a broken promise. The improviser who is responding to real conditions experiences the stabilizer's insistence on the original plan as rigidity, not accountability, inability to read what is actually happening. Both of those experiences are real, and both are missing the other's genuine concern. The stabilizer's insistence on honoring the commitment is not rigidity for its own sake. It is the protection of the social contract that makes organizational coordination possible. If commitments are routinely revised when conditions change, the system of agreements that allows teams to function breaks down. Everyone stops trusting that what was promised will be delivered, and the stabilizer is the one who is paying most careful attention to whether that system is holding. The improviser's willingness to adjust mid-course is not recklessness. It is the recognition that the map is not the territory, that the plan was made with information available at a specific moment, and that new information may require a different approach. The team that executes a plan despite clear evidence that the plan is wrong is not being accountable. It is being rigid in a way that will produce a worse outcome. Both of those are right, and that is the hardest thing about stabilizer improviser tension for coaches to hold clearly. Because both parties are making a genuine organizational argument, not just protecting a preference. The coaching work here is not helping them agree. It is helping them develop explicit agreements about when the plan is binding and when it can evolve. And what the communication protocol looks like when conditions require adjustment. The improviser who learns to communicate plan changes proactively. To give the stabilizer the heads up that something is shifting with the reasoning before acting, preserves the social contract that the stabilizer needs while maintaining the adaptability that the improviser needs. The stabilizer who learns to evaluate plan adjustments on their merits, asking, does this change serve the underlying goal? And was it communicated in good faith? Rather than is this a departure from what was agreed? Makes room for the real time intelligence the improviser is tracking without abandoning the accountability structure that makes the team trustworthy. Neither of those is a concession. Both are the development work that translates into genuine cross type collaboration. One last thing before we close. Across all four of these pairings, there is a single underlying principle that coaches should carry into any cross type conversation. The friction is not about who is right. In every one of these dynamics, connector and stabilizer, strategist and improviser, strategist and connector, stabilizer and improviser, both parties are making a legitimate organizational argument. Both are applying a genuine intelligence. Both are attending to something the team actually needs. The question is never whose approach is correct. The question is what each person needs from the other to trust the relationship enough to let the other's contribution do its work. For the connector, what does this person need from me in order to believe that I'm as committed to the outcome as I am to the process of getting there? For the stabilizer, what does this person need from me in order to believe that my investment in the relationship is as real as my investment in the structure? For the strategist, what does this person need from me in order to experience my intelligence as something that serves them, not just as something that evaluates them? For the improviser, what does this person need from me in order to trust that my adaptability is in service of the team's goals, not just my own preference for freedom? Those questions are the beginning of genuine cross type collaboration. Not the end of the friction, but the beginning of working with it, rather than against it. Here is what to carry forward from this episode. The connector and stabilizer share a collaborative frame, both invested in how work gets done, not just what is produced. Their tensions flow from people first versus process first sequencing, different time horizons of accountability, and different tolerances for change. The productive path is sequence acknowledgement, both contributing in the right order. The strategist and improviser share a performance frame, both utilitarian, both oriented toward what works. Their tensions flow from different planning horizons, different relationships with process, and a trust durability mismatch. The productive path is mutual curiosity. The strategist asking what the improviser saw that the system missed, the improviser providing the sustained presence the strategist needs to maintain trust. The strategist and connector lack common ground on first filters. Logic first meets people first. Both questions are right. The sequence is the friction. The productive path is naming the sequence explicitly and building genuine curiosity about what the other lens reveals. The stabilizer and improviser carry the most fundamental tension. Structured commitment meets adaptive response. The productive path is explicit agreements about when plans are binding, and communication protocols that allow real-time adjustment without breaking the social contract. And across all of them, the friction is never about who is right. It is about what each person needs from the other in order to let the other's contribution do its work. In the final episodes of this series, we bring everything together Workstyles and the personal inventory. The type portrait and the behavioral data. The wiring and what the person is currently doing with it. We've spent 29 episodes learning to see people clearly. Episode 30 is about what you do with everything you've seen. Thanks for being here.