Conflict Styles · COLLABORATING
The Bridge-Builder
Collaborating is your default conflict mode — high on both axes at once, pushing for what you need while staying genuinely curious about what the other person needs too. You treat conflict as a shared problem to solve, not a contest to win or a threat to dodge.
Signature traits
The Thomas-Kilmann Conflict Mode Instrument maps conflict behavior along two independent axes — assertiveness (how much you push for your own concerns) and cooperativeness (how much you accommodate the other party's). Collaborating is the one mode that scores high on both at once, and it's the hardest combination to actually pull off. Competing asserts without listening. Accommodating listens without asserting. Collaborating requires holding both at the same time, under the pressure of an active disagreement — which is a genuinely harder skill than either half alone.
In practice, this looks like asking what someone actually needs before proposing a fix, rather than opening with your own position and negotiating down from there. You hold your own interests clearly, but you let new information about the other side's interests actually move you — not as a concession, but because you're solving for something bigger than 'who wins this exchange.' The conversations you run tend to surface a real interest underneath a stated position, and the solution that comes out the other end is often one neither party had in mind at the start.
This mode earns its place in the model for a specific reason: some conflicts are genuinely complex, involve several stakeholders with real and different needs, and require a resolution durable enough that nobody quietly reneges on it later. Thomas and Kilmann were explicit that collaborating is expensive — it takes more time and more emotional presence from everyone at the table than any other mode — and that expense is worth paying exactly when the problem is complex enough, and the relationship durable enough, to make the investment pay off.
The failure mode is treating collaboration as free, when it isn't. Full collaborative process on a decision that didn't need it burns time a faster mode would have saved, and it's easy to walk out of a beautifully collaborative conversation having quietly given up more than you meant to — because the process itself felt so good that you didn't notice your own interests thinning out along the way. You can run a collaborative conversation so well that you leave with less than you came in wanting, and feel entirely fine about it, which is precisely what makes the pattern hard to catch.
There's a subtler risk specific to this style: it only works when both sides show up for it. A collaborator paired with someone who simply states a position and holds it will do the emotional labor of the whole exchange alone — asking the good questions, staying curious, absorbing the friction — while the other party contributes nothing but their original ask. Collaboration extended to someone unwilling to reciprocate isn't generosity, it's a pattern that gets quietly exploited.
None of this argues against reaching for collaboration as your default — in situations that are actually complex and actually matter, nothing else produces outcomes this good. The growth edge is triage: deciding, in the first minute of a disagreement, whether it genuinely calls for the full process or whether a faster mode would serve everyone better, and reserving the expensive version of yourself for the conflicts that are actually worth it.
- Holds a position while staying open to being changed
Advocates clearly for what you need without shutting down new information that might actually change your mind — a rarer combination than it sounds.
- Surfaces the real interest under the stated position
Asks what someone actually needs rather than negotiating against what they first said they wanted, which frequently reveals a solution neither side had considered.
- Builds trust that compounds
People who've been through a real collaborative process with you come away trusting your good faith even when the outcome wasn't exactly what they'd hoped for.
- Produces genuinely novel solutions
The outcome of a full collaborative conversation is often something neither party would have proposed alone — the process itself generates the answer.
- Runs the expensive process on cheap problems
Full collaboration takes time and emotional presence that a quick call or a fast compromise would have covered just as well on lower-stakes disagreements.
- Own interests thin out during the process
The collaborative conversation can go so well that your own needs get quietly deprioritized without you noticing — you leave satisfied with the process but short on the outcome.
- Vulnerable to one-sided exchanges
Collaborating with someone who won't reciprocate the curiosity means you absorb the whole cost of the conversation while they contribute only their original position.
- Uses process to delay a decision that's already yours
Opening up 'let's explore this together' can occasionally be a way of avoiding a call you actually have the standing and information to make right now.
At work, the Collaborating style is the one who asks what a stakeholder actually needs before proposing a roadmap change, who runs the cross-functional meeting that leaves everyone feeling heard AND produces a decision, and who is trusted to hold competing priorities without anyone feeling steamrolled. This is a strong fit for roles with real complexity and multiple stakeholders — product management, mediation, organizational development, or any seat where buy-in matters as much as the decision itself. It creates friction in fast-moving, high-stakes situations that need a quick unilateral call, where the instinct to explore and include can cost more time than the moment allows.
In close relationships, Collaborating shows up as someone who wants to actually understand what's going on for their partner, not just to be heard themselves — a hard conversation with you tends to end with both people knowing more about each other's real position than they did at the start. The risk is one-sidedness: you can end up doing the emotional work of processing conflict for both people, staying curious and open while your partner simply states what they want and waits. What tends to help is naming that expectation explicitly — that you have needs of your own in the conversation, and that the other person needs to bring real conflict capacity too, rather than letting your collaborative instinct absorb what should be shared work.
Collaborating energy is put to its best use in roles with real complexity and multiple stakeholders whose buy-in matters, and creates the most friction in roles that reward speed and a fast, unilateral decision over full inclusion.
- Product manager
- Mediator or facilitator
- Strategic consultant
- UX designer
- Organizational development lead
- Program manager
- Professional negotiator
- Team lead in a cross-functional org
Take the Conflict Styles test
Discover how you map to Conflict Styles in a few minutes. Free, private, no sign-up required to start.
Start the Conflict Styles test →Other Conflict Styles types
- COMPETINGThe Contender
You go straight at the goal — assertive, direct, and fine with a little heat.
- COMPROMISINGThe Negotiator
You find the middle fast — pragmatic, fair, and quick to split the difference.
- AVOIDINGThe Deflector
You step back from the heat — patience and timing over confrontation.
- ACCOMMODATINGThe Peacekeeper
You keep the relationship whole — even when it costs you something first.
Frequently asked
Is Collaborating always the best conflict style?
No — it's the most expensive mode in time and emotional energy, and the TKI model treats it as the right tool for complex, high-stakes, multi-stakeholder situations, not a universal default. Simpler conflicts are often better served by a faster mode.
Is Collaborating just a nicer way of being a pushover?
No — it's defined by scoring high on assertiveness AND cooperativeness. Accommodating is the mode that yields without asserting; Collaborating holds its own position while staying genuinely open to the other side's.
What happens when I collaborate with someone who won't reciprocate?
You end up doing the full emotional labor of the exchange alone. Collaborating works as a two-way process — when only one side brings curiosity and flexibility, it stops being collaboration and starts being a one-sided concession.
Can I build faster conflict modes if Collaborating dominates?
Yes — the TKI framework treats conflict-mode use as a skill set, and deliberately practicing Competing or Compromising in situations that call for speed is a documented way to build range without losing your collaborative strength.