Quick answer
To improve collaboration at work, identify how people are currently working together, decide what the work requires and address what is preventing them from working that way. The 6 Cs provides a practical framework for making that diagnosis.
The six Cs of collaboration are:
- Coercion: Securing compliance through pressure or control.
- Confrontation: Pursuing competing interests in opposition to one another.
- Coexistence: Working separately with limited involvement or interference.
- Cooperation: Helping one another achieve largely separate objectives.
- Collaboration: Jointly shaping work towards a shared outcome.
- Co-ownership: Accepting shared responsibility for the overall result.
The aim is not to move every relationship towards co-ownership, but to develop the way of working that the task actually requires.
The central question: Are we working together in the way that the work actually requires?
Many attempts to improve collaboration at work begin with the wrong question: how can we get people to collaborate more?
That assumes more collaboration is always the answer. It is not. Some work requires people to operate independently. Some requires coordination and mutual support. Other work depends on joint problem-solving or shared responsibility for the result. The important question is whether people are working together in the way that the work actually requires.
We use the word collaboration remarkably loosely in organisations. Sharing information is described as collaboration. Attending a cross-functional meeting is collaboration. Helping another department complete a task is collaboration. Even agreeing not to interfere with one another can be presented as evidence of effective collaboration. These ways of working may all be useful, but they are not the same.
I first encountered a framework for making these distinctions in 1994, when I moved from outdoor instructing and guiding at Plas y Brenin, the UK’s national outdoor centre, into a role with General Motors Europe. I became involved in a major transformation programme called The D!fference, which reached more than 50,000 employees and members of the franchise network.
One of the models used during the programme was the 6 Cs of collaboration. My understanding is that it originated with an internal consulting team at Saturn Corporation, General Motors’ US subsidiary, although I have not been able to verify the original authorship.
The model describes six ways in which people and groups can relate and work together, ranging from coercion at one end to co-ownership at the other. More than three decades later, I still find it useful, particularly when work crosses teams, functions and reporting lines.
Rather than labelling people as collaborative or uncollaborative, the 6 Cs helps us examine the pattern developing around a particular task, decision or outcome. This article explores what each of the six Cs looks like, what may help people change how they work together, and how leaders can use the framework to understand conflict, strengthen working relationships and improve collaboration across organisational boundaries.
The 6 Cs: Six ways of relating and working together
The six Cs are arranged from coercion through to co-ownership. Moving rightwards represents increasing potential for constructive interdependence, where people recognise how their work connects and become more involved in shaping shared outcomes.
That distinction matters, but it needs qualification.
- First, the continuum is not a measure of relationship maturity. Moving rightwards changes the nature of the interaction; it does not make the people involved intrinsically better leaders or contributors.
- Second, it describes the work between people, not the relationship in the abstract. We will return to the implications of that distinction.
- Third, relationships do not progress in a predetermined sequence. A new priority, change in authority or breakdown in trust can alter how people work together.
These qualifications make the model more useful because they move the discussion beyond whether people are good at collaboration towards a more interesting question: What is happening between these people, around this piece of work, that makes a particular way of working more or less likely?
Coercion: When compliance replaces contribution
Coercion is the use of pressure, threats, intimidation or power to compel another person to act. The person applying pressure seeks compliance, often with limited regard for whether the other party understands, supports or agrees with what is being demanded.
In organisational settings, coercion is not always expressed through overt threats. It may involve the selective use of information, the withdrawal of support, repeated escalation to senior managers or the implication that questioning a decision will have negative consequences.
A programme leader struggling to secure resources might repeatedly appeal to a functional manager’s boss, making it clear that failure to release people will be interpreted as a lack of commitment. The resources may eventually be provided, but the functional manager has little reason to become more supportive of the programme.
The immediate problem has been solved through pressure. The underlying relationship may have deteriorated.
There is an important distinction here between coercion and legitimate authority. Organisations need people with the authority to make decisions, establish priorities and enforce appropriate standards. A leader setting a clear safety requirement or making a necessary operational decision is not automatically behaving coercively.
The distinction lies in whether authority is exercised responsibly or used to suppress legitimate concerns and secure compliance through fear.
How to recognise coercion
People may comply publicly while expressing doubts privately. Decisions are imposed with little opportunity for meaningful challenge. Information or resources become instruments of control. Concerns are dismissed or treated as disloyalty, and considerable attention is devoted to avoiding negative consequences. One consequence is that leaders can become increasingly detached from what others actually think. People learn which concerns are safe to raise and which are better left unspoken. This can create an appearance of agreement precisely when the organisation most needs challenge.
Moving rightwards: Making disagreement possible
The immediate objective is not necessarily to create collaboration. Where coercion has shaped a relationship, the first task may be to make it possible for different views and interests to be expressed. This connects with Edmondson’s (1999) research on psychological safety, which found an association between a team’s shared sense that interpersonal risks were safe and its learning behaviour. Her findings do not suggest that disagreement automatically produces collaboration, but they help explain why speaking up matters before people can productively challenge assumptions.
This means explaining the reasons behind decisions, distinguishing genuine constraints from negotiable matters and creating opportunities for people to raise concerns without being punished for doing so. It also requires those holding power to examine their own behaviour. Inviting challenge achieves little if the response to an uncomfortable question is defensiveness, ridicule or retaliation.
A leader might begin by acknowledging that previous decisions have left little room for discussion and asking what concerns have not been addressed. They then need to demonstrate, through their response and subsequent actions, that the invitation was genuine.
The relationship may become less comfortable before it becomes more constructive. People who previously remained silent may begin to challenge decisions openly. This does not mean that confrontation is the desired destination. It means that visible disagreement may be a necessary improvement on enforced silence.
Where coercion involves bullying, harassment or serious intimidation, the priority is protection and appropriate intervention, not persuading the affected person to engage in a more collaborative conversation.
Confrontation: When differences become opposition
Disagreement is a normal feature of organisational life. People have different responsibilities, access to different information and legitimate reasons for seeing the same problem differently. A finance leader may be concerned about costs and risk, while a commercial leader concentrates on growth and customer responsiveness. Neither perspective is inherently wrong, and their differences may improve the quality of a decision.
Confrontation develops when these differences become organised around opposition. The emphasis shifts from understanding and resolving a problem towards defending positions, defeating arguments or preventing the other party from prevailing. The relationship becomes increasingly adversarial. Meetings may repeatedly return to previous disputes. People question motives rather than examine evidence. Information is selected to strengthen a position rather than improve collective understanding. Problems that might have been addressed directly become opportunities to demonstrate where the other party has failed. In extreme cases, people begin defining success partly through the failure of the other person or group.
How to recognise confrontation
The most revealing indicator is often what happens when an issue arises. Do people begin by examining the problem, or by preparing a defence? Are different perspectives treated as useful information or evidence that the other party cannot be trusted? Does the discussion move towards possible solutions, or repeatedly return to who is responsible?
Confrontation can also be concealed beneath professional language. A relationship may appear civil while individuals use governance processes, reporting requirements or senior stakeholders to obstruct one another. This is why visible disagreement alone is an unreliable measure of conflict. Two people can argue vigorously while collaborating effectively. Equally, two departments may be locked in an adversarial relationship without ever having an openly hostile meeting.
Moving rightwards: Creating workable boundaries
When confrontation is entrenched, insisting on immediate collaboration can make matters worse. People who distrust one another may interpret invitations to collaborate as another attempt to gain influence or control. An initial improvement may be to establish more predictable interactions. This involves clarifying responsibilities, agreeing how disagreements will be handled and identifying behaviours that are making the situation worse. It may mean separating activities that do not genuinely require joint involvement, while establishing clear arrangements for those that do. For example, two managers repeatedly arguing over operational decisions may benefit from clarifying which decisions each can make independently, which require consultation and which need escalation to an agreed decision-maker.
The aim is not to remove every disagreement. It is to reduce the extent to which disagreement disrupts unrelated work. This may lead to coexistence rather than collaboration. That can still represent progress, particularly when the immediate need is to stabilise a difficult relationship.
Coexistence: When people work alongside one another
Coexistence is perhaps the most easily misunderstood of the six Cs because it often resembles a perfectly healthy working relationship. People are polite. They respect organisational boundaries. Meetings are generally uneventful, and there may be few complaints about colleagues in other departments. Each person or team concentrates on their own responsibilities, intervening in the work of others only when necessary.
Where activities are genuinely independent, coexistence may be entirely appropriate. There is little value in creating additional coordination simply because collaboration is considered desirable. Problems arise when activities are interdependent but the people responsible continue to behave as though they are separate.
Consider two teams responsible for consecutive stages of a customer process. Both achieve their departmental targets. Neither has much visibility of what happens beyond its own responsibilities. Problems at the handover are handled through formal requests, delays and occasional escalation. Each team may be performing well according to its own measures, while the overall customer experience remains poor. The difficulty is not necessarily hostility or unwillingness. It may be that the teams have organised their work around boundaries that do not reflect the way value is actually created.
How to recognise coexistence
Communication tends to be limited to what is formally required. People may know little about the pressures facing other teams, even when their decisions affect those teams directly. Requests for assistance are handled through established channels, but there is limited curiosity about whether the wider process could be improved. People may avoid difficult conversations because they do not wish to interfere or because previous attempts to raise issues have been unproductive.
The relationship is stable, but its potential remains largely unexplored.
Moving rightwards: Recognising practical dependencies
The transition towards cooperation begins when people recognise how their work affects one another and identify ways to provide practical support. This does not require a new shared purpose or an elaborate collaboration initiative. It may begin with a conversation about handovers, information needs or recurring problems.
A useful starting point is to examine where work crosses boundaries. What does one team need from another? Where are delays created? Which decisions have consequences that are not visible to the person making them?
Small changes can have significant effects. Sharing information earlier, changing a handover process or involving a colleague before a decision is finalised may remove a recurring source of frustration. Okhuysen and Bechky (2009) identify accountability, predictability and common understanding as important conditions for coordinating interdependent work. Their analysis helps explain why better handovers and clearer expectations may be more useful than adding another collaborative meeting.
The shift is from concentrating exclusively on one’s own responsibilities towards recognising that helping someone else perform their work may also improve one’s own results.
Cooperation: Helping one another succeed
Cooperation is a substantial step beyond coexistence because people begin actively supporting one another. They share information, coordinate activities, offer expertise and make adjustments that help colleagues achieve their objectives. There is recognition that separate areas of work intersect and that mutual assistance can improve performance.
Much of organisational life depends on effective cooperation. A project manager coordinates with functional teams to secure resources. Sales keeps Operations informed about changing customer requirements. Finance provides information that helps another department evaluate its decisions. These interactions may be valuable without requiring joint ownership of the work.
The defining characteristic is that people remain primarily responsible for their own objectives while helping others achieve theirs. Such cooperation can be reliable and productive. Its limit becomes visible when separate objectives and decisions cannot resolve a problem that crosses functional boundaries.
Problems emerge when achieving the overall result requires more than coordinating those separate contributions.
How to recognise cooperation
People generally respond to reasonable requests, share relevant information and seek practical solutions when dependencies create difficulties. They are willing to help, but their commitments are usually bounded by their own responsibilities and priorities. When objectives conflict, discussions may return to what each function can reasonably be expected to contribute. This is not necessarily a weakness. It is a reflection of the way responsibility has been organised. However, it becomes a limitation when the problem itself cannot be divided into separate functional tasks.
Moving rightwards: From supporting plans to shaping them together
The transition towards collaboration requires people to begin jointly defining and addressing a shared problem. Instead of developing separate plans and then coordinating their delivery, they bring their different perspectives into the process earlier. A commercial team and an operations team might cooperate effectively when implementing a customer solution that has already been agreed. Collaboration would involve both functions shaping the solution from the outset, examining commercial opportunities alongside operational constraints. This changes the quality of the conversation.
The question is no longer simply what one party needs from another. It becomes what the parties are trying to accomplish together and how their different contributions might produce a better outcome. Practical progress may begin by involving colleagues before a preferred solution has been developed, agreeing what problem they are jointly addressing and examining the trade-offs that separate planning would otherwise leave unresolved.
Collaboration: Jointly shaping a shared outcome
Collaboration involves people combining their knowledge, capabilities and perspectives to work on a common problem or outcome. Its distinctive feature is joint influence over the work itself, rather than the frequency of meetings or the warmth of the relationship. This is particularly valuable when the work is complex, uncertain or dependent on knowledge that no single person or function possesses.
Collaboration can produce better outcomes because people bring different information and assumptions into the same conversation. Problems that appear straightforward from one perspective may prove more complicated when examined through others. However, this benefit depends on the quality of interaction.
Collaboration is not achieved simply by bringing people into the same room. Groups can meet frequently while avoiding difficult issues, accepting dominant opinions or dividing tasks without genuinely integrating their thinking. Nor does collaboration require consensus on every decision. Different perspectives, disagreement and challenge can improve the work, provided people remain oriented towards understanding the problem and finding an effective way forward.
How to recognise collaboration
People participate in defining the problem rather than simply responding to proposed solutions. They examine assumptions, share relevant expertise and adapt their thinking in response to what others contribute. Different responsibilities remain, but decisions are informed by a wider view of the work. The group considers the consequences of choices across functions rather than assuming that each area can optimise its own contribution independently. There is also greater willingness to revisit an approach when new information emerges.
Moving rightwards: From shared work to shared responsibility
People can collaborate closely without necessarily accepting responsibility for the overall result. They may contribute expertise, participate in decisions and deliver their agreed work while still regarding the final outcome as belonging to the project leader or sponsoring function.
Co-ownership requires a different commitment. Rather than seeing themselves as contributors to someone else’s objective, people begin to accept responsibility for the success of the wider endeavour. This transition depends on more than encouraging a stronger sense of ownership. People need clarity about the intended outcome, sufficient influence over the decisions affecting it and an understanding of how individual responsibilities contribute to collective success.
Leaders can support this by establishing shared success measures, involving people in significant trade-offs and reviewing progress in terms of the overall result rather than simply collecting separate functional updates.
There is also an important organisational consideration. If people are encouraged to take shared responsibility but rewarded entirely for individual or departmental performance, the intended shift may remain superficial.
Co-ownership: Taking responsibility for the whole
Co-ownership represents the strongest form of constructive interdependence in the model. People recognise that success depends on their combined contribution and accept responsibility for the overall outcome, even though their roles, authority and expertise remain different.
A group of leaders responsible for a major transformation might demonstrate co-ownership when they make difficult decisions about resources, priorities or implementation based on the success of the programme rather than the immediate interests of their individual functions. When something goes wrong, their first response is to understand how the problem can be resolved rather than establish which department is responsible for the failure.
This does not mean that everyone is accountable for everything. Formal responsibilities remain essential. Someone must have authority to approve expenditure, make employment decisions, manage risks and determine priorities when agreement cannot be reached.
Co-ownership becomes problematic when shared responsibility is used to obscure those distinctions. Work on shared leadership, including Pearce and Conger (2003), similarly treats the distribution of leadership as contingent rather than universally appropriate. Shared influence does not remove the need to establish who makes particular decisions.
The stronger version combines clear individual accountability with a genuine commitment to collective success.
How to recognise co-ownership
People take initiative beyond their immediate assignments when the wider outcome requires it. They raise problems early, including problems that could reflect badly on their own contribution. They are prepared to examine difficult trade-offs and recognise that a decision benefiting the whole may create disadvantages for their own area.
There is also an important difference in how success and failure are discussed. Rather than treating delivery as the sum of completed functional responsibilities, people examine whether the overall outcome has been achieved and what their combined efforts contributed to it.
Sustaining co-ownership
Co-ownership is not a permanent achievement. It can weaken as circumstances change. A new senior leader may introduce different priorities. Budget pressures may encourage functional leaders to protect their resources. Changes in personnel may affect trust and commitment.
Sustaining co-ownership therefore requires continued attention to shared purpose, decision rights, organisational incentives and the quality of working relationships. It also requires leaders to examine when the arrangements themselves are no longer appropriate. A group that needed close co-ownership during the design and implementation of a major change may require less intensive collaboration once the work becomes stable and routine.
The question is not how to preserve co-ownership at all costs, but whether the current way of working continues to serve the outcome.
What actually changes across the six Cs?
The differences between the six Cs are not simply differences in how friendly, supportive or cooperative people appear. Several underlying features of the relationship change.
| Dimension | What to look for |
|---|---|
| Power and voice | Who can influence the work, whose concerns are taken seriously and how authority is exercised? |
| Orientation towards others | Are others treated as obstacles, independent actors, sources of assistance or partners in achieving an outcome? |
| Information | Is information controlled, withheld, exchanged when needed or jointly examined to improve understanding? |
| Decision-making | Are decisions imposed, contested, made separately, coordinated or shaped through joint discussion? |
| Responsibility | Is the emphasis on compliance, individual delivery, mutual assistance or success of the wider outcome? |
These dimensions help explain why apparently similar behaviours can reflect different ways of working. For example, a manager might consult widely before making a decision. That consultation may represent genuine collaboration if the views expressed influence the outcome. Alternatively, it may be little more than a way of communicating a decision that has effectively already been made. Similarly, colleagues may share information regularly without ever engaging in joint problem-solving.
The point is not to establish rigid criteria for each C. These dimensions provide questions through which people can explore the relationship in greater depth. They also help avoid reducing collaboration to a matter of interpersonal goodwill.
One relationship, several ways of working
An important feature of the model is that the same two people can operate at different points on the continuum depending on what they are doing together. Consider a functional manager and a programme leader. They may collaborate effectively when designing a new service, cooperate when coordinating resources and coexist when carrying out unrelated responsibilities. However, when annual budget allocations are discussed, the relationship may become confrontational because each is accountable for different priorities and neither has the authority to resolve the competing demands alone. Describing their overall relationship as collaborative or confrontational would conceal these differences.
The more useful question is how they are working together in relation to a particular task, decision or outcome. This suggests a different starting point for a leadership conversation: Name the activity before evaluating the relationship.
How much collaboration does the work actually require?
Many organisations treat collaboration as an unquestioned good. Leaders are encouraged to break down silos, involve stakeholders, increase cross-functional working and build shared ownership. Joint discussions require time. More people involved in decisions can slow progress. Shared responsibilities can create ambiguity when decision rights are unclear. Extensive collaboration may reduce the autonomy of specialists who could otherwise complete their work efficiently.
The test is whether involving people more closely would improve the quality, speed or sustainability of the outcome enough to justify those costs.
| Nature of the work | Potentially appropriate C | What matters most |
|---|---|---|
| Independent activities with few dependencies | Coexistence | Clear boundaries and reliable individual delivery |
| Separate activities requiring coordination | Cooperation | Information sharing, handovers and mutual support |
| Complex problems requiring integrated perspectives | Collaboration | Joint problem definition, decisions and adaptation |
| Outcomes requiring sustained collective commitment | Co-ownership | Shared success measures, commitments and accountability |
Coercion and confrontation are not presented as desirable targets in this table. They may describe current relationships that require attention, rather than chosen approaches to productive work.
The costly mismatch can run in either direction. A team may execute well-defined tasks together through lengthy joint meetings when simple coordination would be faster. Another may deliver every individual workstream while failing to solve a cross-functional problem nobody owns.
Why people do not always work together as we expect
When collaboration breaks down, the tendency is often to focus on individual behaviour. People are described as territorial, defensive, unhelpful or unwilling to cooperate. Leaders respond by encouraging openness, improving communication or attempting to build trust. These interventions may be worthwhile, but they can miss the conditions that are maintaining the existing pattern.
Consider two departments competing for a limited pool of technical specialists. Both have legitimate priorities. Both have committed to delivery targets. Both know that releasing resources to the other will make their own objectives harder to achieve. Their confrontation may be unpleasant, but it is not difficult to understand.
Asking the departmental leaders to collaborate more effectively will accomplish little if nobody addresses the underlying resource conflict or decides how competing priorities should be balanced. The problem is not necessarily unwillingness to collaborate. It may be that the organisational arrangements make a different way of working difficult. Several factors are worth examining:
Interdependence determines how far people genuinely need one another. Where the work is independent, coexistence may be efficient. Where the work is tightly connected, separate decision-making may create repeated problems.
Objectives and incentives influence what people protect. When departments are rewarded for achieving local targets, cooperation may be conditional on whether it threatens those targets. Collaboration may be encouraged in principle while being discouraged in practice.
Power and decision rights shape who can make commitments and whose preferences carry weight. A person may be expected to take shared ownership of an outcome while lacking authority over resources or decisions that determine its success.
Trust and previous experience affect people’s willingness to share information, challenge assumptions or expose difficulties. A history of broken commitments can influence behaviour long after the original dispute has faded.
Organisational processes and boundaries determine how easily information, decisions and resources move. Even willing colleagues may struggle to collaborate when systems, governance arrangements or reporting requirements reinforce separation.
These conditions interact. Limited trust may encourage people to seek more formal controls. Those controls may reduce autonomy and increase defensiveness. Competing targets may intensify resource disputes, which then damage relationships and reinforce departmental boundaries.
The resulting behaviour can become self-sustaining. This is why improving collaboration sometimes requires changing organisational arrangements rather than concentrating solely on interpersonal skills.
How the 6 Cs connects to matrix leadership
The relevance of the model becomes particularly clear in matrix organisations. A matrix creates formal interdependence across functions, products, programmes, geographies or business units. People are required to contribute to outcomes that extend beyond their reporting lines, often with different leaders influencing their work and competing demands on their time. However, the structure does not determine how those relationships operate.
A programme leader may depend on a functional manager for resources. They might negotiate those resources through cooperation, work together to redesign the programme through collaboration or accept shared responsibility for the outcome through co-ownership. Alternatively, the same relationship may be dominated by confrontation or repeated attempts to use senior authority to secure compliance. The reporting lines have not changed. The way people are working together has.
This distinction helps explain why reorganising reporting structures does not automatically improve collaboration. A new matrix may create additional points of dependency without resolving the incentives, authority arrangements or working practices that make those dependencies difficult to manage.
It also connects with the challenge of building influence without authority. Matrix leaders frequently need support from people they cannot direct. They have to understand competing interests, build credibility and create conditions in which colleagues are willing to make commitments.
The 6 Cs provides a way of examining what kind of relationship those efforts are creating and whether it is sufficient for the outcome. There is a further connection with accountability without authority. A group may cooperate effectively, with each function completing its own responsibilities, while nobody takes responsibility for the dependencies between them. Moving towards collaboration may improve how the work is integrated. Moving towards co-ownership may strengthen commitment to the result as a whole.
Neither transition removes the need for clear decision rights and individual accountability. This is one of the central challenges of matrix leadership: creating enough collective commitment to achieve outcomes that no single function controls, without assuming that every decision needs to be shared or that influence can replace formal authority entirely. The 6 Cs helps make those distinctions more visible.
Using the 6 Cs to understand conflict
Conflict is one of the most useful applications of the model, but not because confrontation represents the only point at which conflict occurs. People can disagree while cooperating, collaborating or sharing ownership. In fact, the closer their work becomes, the more opportunities they may have to encounter different assumptions, priorities and expectations. The important distinction is how those differences are handled.
Deutsch’s (1949) work on cooperation and competition helps illuminate this. His theory distinguishes between situations in which people perceive their goals as positively linked, so that one person’s success supports another’s, and situations where goals are perceived as negatively linked, so that one person’s success threatens the other’s. These perceptions influence how people communicate, interpret behaviour and respond to disagreement.
The 6 Cs is not derived directly from Deutsch’s theory, but there is a useful connection. Confrontation can emerge when people see their interests as incompatible. Cooperation becomes easier when they recognise opportunities for mutual benefit, while collaboration and co-ownership require deeper engagement with shared outcomes. However, this should not be reduced to a simple matter of changing perceptions. Sometimes interests genuinely conflict, and no amount of positive communication will remove the need for difficult choices. A practical approach involves six steps.
Step 1: Identify the specific issue
Avoid beginning with a broad judgement about the relationship. Saying that two departments do not collaborate is considerably less useful than identifying that they repeatedly confront one another over resource allocation, while cooperating successfully on operational delivery. The more precisely the issue is defined, the easier it becomes to understand what is maintaining the difficulty.
Step 2: Identify how people are currently working together
Examine behaviour rather than personality. Who makes the decisions? How are differences handled? What information is shared? What happens when commitments become difficult? Are people seeking to understand one another’s concerns or primarily defending their own positions? Use the six Cs to form an initial assessment.
Step 3: Decide what the situation requires
Define what a workable resolution would look like before choosing an intervention. Two groups in persistent confrontation may need clearer boundaries and decision rights. Colleagues who coexist comfortably may need better cooperation around a particular handover. A project team may need collaboration to solve an integrated problem that separate functions have been unable to address.
Step 4: Examine what is maintaining the current pattern
A useful diagnostic is to ask whether the difficulty is primarily behavioural, relational or structural.
| What may be maintaining the problem? | Questions to explore |
|---|---|
| Behaviour | Which actions are creating friction, and what needs to change? |
| Assumptions | What are people assuming about one another’s motives or intentions? |
| Relationships | What previous experiences are affecting trust and willingness to engage? |
| Competing interests | Which legitimate priorities or needs are in tension? |
| Organisational arrangements | Are unclear authority, conflicting targets or processes reinforcing the problem? |
These explanations are not mutually exclusive. A structural difficulty may contribute to repeated conflict, which then damages trust and makes future cooperation more difficult. This matters because different causes require different interventions. Communication training may help people manage a difficult conversation, but it will not resolve incompatible objectives. Clearer decision rights may reduce recurring disputes, but they will not automatically rebuild trust after repeated breaches of agreement.
Step 5: Choose the next useful move
Rather than attempting to transform the relationship, identify a practical change that addresses the immediate barrier.
| Current C | Potential next move | Conversation to begin |
|---|---|---|
| Coercion | Make genuine disagreement possible, with appropriate safeguards | What concerns have not been possible to raise openly? |
| Confrontation | Reduce destructive friction and clarify boundaries | What do we need to agree so that our differences stop obstructing the work? |
| Coexistence | Identify dependencies where mutual support would help | Where does my work affect yours, and what could we improve? |
| Cooperation | Jointly define an important shared problem | What do we need to solve together rather than through separate contributions? |
| Collaboration | Strengthen commitment to the overall outcome | What would change if we accepted shared responsibility for the result? |
| Co-ownership | Sustain collective commitment as circumstances change | Which pressures might cause us to retreat into protecting our own interests? |
These are possible interventions, not compulsory transitions. It may be appropriate to move directly from coexistence to collaboration when the work demands it. Equally, the best solution to a confrontational relationship may involve separating responsibilities rather than increasing interdependence. Where intimidation or serious misconduct is involved, formal intervention may be necessary before constructive dialogue is realistic.
Step 6: Review what has changed
The final step is to examine whether the intervention improved how people work together. A conversation may have felt positive without producing any meaningful change. People may express a willingness to collaborate while continuing to make decisions separately, withhold information or protect conflicting priorities. Look instead for observable evidence: Are concerns raised earlier? Are handovers more reliable? Do people explore differences without immediately defending their positions? Are decisions informed by the perspectives of those affected? Are commitments being honoured, and are problems between responsibilities being addressed rather than passed along?
The most revealing question is often: What can we now achieve together that was previously difficult or impossible? That keeps attention on the purpose of the relationship rather than the appearance of harmony.
When the two parties see the relationship differently
There is an additional issue worth exploring when using the model in coaching or team discussions. The two parties may place their relationship at different points on the continuum. A leader may believe they are collaborating because they involve colleagues in discussions. Those colleagues may experience cooperation because they are asked to contribute information but have little influence over decisions. A project manager may describe a functional relationship as confrontational, while the functional manager believes they are simply defending legitimate priorities. Neither assessment should automatically be accepted as an objective description.
People see the relationship through different responsibilities, expectations, experiences and degrees of power. One practical approach is to ask the parties to assess the same piece of work independently, identify the evidence behind their choice and then compare their interpretations. This can reveal important differences. Perhaps they disagree about whether a decision is open to influence. Perhaps one expects shared ownership while the other believes their responsibility is limited to delivering a specialist contribution.
Sometimes the disagreement is not about how well people are collaborating. It is about what they understand the relationship to require. Making those expectations explicit can be an important step towards improving the work.
When closer working would be inappropriate
The question of how much involvement is useful is different from the question of whether closer involvement is appropriate at all. Some boundaries are there for good reasons. A professional may need independence to make a judgement without undue influence. Conflicts of interest may require responsibilities to be separated. A leader may need to make a decision personally because the authority, legal obligation or accountability cannot be delegated.
There are also situations in which calls for collaboration can conceal an unfair distribution of power. Asking someone to share ownership of an outcome while denying them meaningful influence over the decisions or resources that determine it risks transferring responsibility without authority.
Where there is intimidation, harassment or abuse, the response should prioritise safety, fair processes and appropriate intervention. Greater closeness is not the measure of a successful resolution.
These are not exceptions to be overcome through better relationship skills. They are reasons to clarify rights, boundaries and responsibilities before deciding whether closer working would help.
A practical exercise: Mapping your working relationships
The 6 Cs can be used as a short individual reflection, a coaching exercise or a facilitated discussion with a leadership team. Begin by selecting a particular project, task or recurring issue. Avoid assessing a relationship in general, because the way people work together may differ significantly across activities. Then consider six questions.
| Question | What to consider |
|---|---|
| 1. Where are we now? | Which C best describes how we currently work together on this issue? What observable behaviour supports that assessment? |
| 2. Where do we need to be? | What degree of cooperation, collaboration or shared ownership does the work require? |
| 3. How might others see it? | Would the other people involved assess the relationship differently, and why? |
| 4. What is keeping us here? | Which behaviours, relationships, assumptions or organisational arrangements sustain the current pattern? |
| 5. What could we change? | What specific action, agreement or change in working arrangements would make a meaningful difference? |
| 6. How will we know? | What would we expect to observe if the change were effective? |
For a more extensive discussion, identify several important working relationships around the same initiative and compare current and required ways of working.
| Relationship | Current C | Required C | Most important change |
|---|---|---|---|
| Programme lead and Finance | Cooperation | Cooperation | Maintain reliable reporting and decision processes |
| Programme lead and Operations | Confrontation | Collaboration | Resolve priority conflicts and agree joint planning arrangements |
| Programme lead and HR | Coexistence | Cooperation | Improve early information sharing around workforce implications |
| Programme lead and IT | Cooperation | Collaboration | Involve technical specialists in solution design |
| Programme lead and Country leadership | Collaboration | Co-ownership | Establish shared success measures and explicit commitments |
This is an illustrative example, not an assessment of an actual organisation. Notice that the Finance relationship does not need to move rightwards. Its current approach may be entirely appropriate. The more important gaps lie elsewhere. Nor should the leader automatically concentrate on the relationship furthest to the left. The greatest risk may come from a relationship that appears positive but falls short of the level of joint working required for a critical outcome.
That distinction makes the exercise useful for prioritising leadership attention. The six Cs is a reflective framework, not a validated psychometric instrument. Its value lies in helping people examine what they observe, challenge assumptions and agree practical changes, rather than generating a score.
Wrapping up
The word collaboration often hides more than it reveals. It can refer to exchanging information, helping a colleague, designing a solution together or accepting shared responsibility for its success. Those activities place different demands on people, and treating them as interchangeable creates confusion.
The 6 Cs gives leaders a language for examining those differences without labelling people. Its value is greatest when applied to specific work: who depends on whom, where the difficulties occur and which conditions are influencing the way people respond. It also changes the nature of the intervention. A strained relationship may call for clearer decision rights, a joint problem-solving process, more reliable coordination or a change to conflicting objectives. Choosing between these requires more than a general appeal to collaborate.
Before asking people to collaborate more, perhaps we should ask what they need to accomplish together and what way of working would give them the best chance of doing it.
Origins and attribution
As mentioned at the start, my understanding is that Saturn Corporation’s internal consulting team originated it, although I have not been able to verify the original authorship. The interpretation, distinctions and practical applications in this article reflect my subsequent experience working with leaders and organisations using the 6Cs. The visual in the header was created by the late Paul Richardson, who was the Graphic Recorder and creator of visuals for the programme.
Want to improve collaboration across teams, functions or organisational boundaries?
For You: Leadership Clinic
Bring one situation where collaboration has become difficult or ineffective. I prepare beforehand, then we spend 90 focused minutes diagnosing how people are currently working together, what the situation requires and the most useful next move.
For You: Executive Coaching
Strengthen your ability to collaborate across boundaries, navigate competing interests and build shared commitment without creating unnecessary meetings or blurred accountability. We work over time on the relationships, judgement and organisational dynamics shaping your effectiveness.
For Your Organisation: Leadership, Teams & Facilitation
Help leaders and teams recognise how they are working together, address the conditions obstructing collaboration and build the level of cooperation, shared problem-solving or ownership their work actually requires.
Choose the level of support that fits the collaboration challenge you are working through.
Sources:
The research below informs particular arguments in this article; it should not be interpreted as evidence of the original authorship or academic validation of the 6 Cs.
- Deutsch, M. (1949) ‘A theory of co-operation and competition’, Human Relations, 2(2), pp. 129–152. Available at: https://doi.org/10.1177/001872674900200204 (Accessed: 20 October 2026).
- Edmondson, A. (1999) ‘Psychological safety and learning behavior in work teams’, Administrative Science Quarterly, 44(2), pp. 350–383. Available at: https://doi.org/10.2307/2666999 (Accessed: 20 October 2026).
- Okhuysen, G.A. and Bechky, B.A. (2009) ‘Coordination in organizations: An integrative perspective’, Academy of Management Annals, 3(1), pp. 463–502. Available at: https://doi.org/10.5465/19416520903047533 (Accessed: 20 October 2026).
- Pearce, C.L. and Conger, J.A. (eds.) (2003) Shared leadership: Reframing the hows and whys of leadership. Thousand Oaks, CA: SAGE Publications. Available at: https://doi.org/10.4135/9781452229539 (Accessed: 20 October 2026).




Leave A Comment