Collaboration Is Not the Same as Co-Creation
Ask most leadership teams what makes a team good at collaboration and you will get an answer about communication, or attitude, or people simply getting on with each other. Few will mention structure, and almost none will mention friction, yet both explain far more about whether collaboration actually produces anything.
In brief
Collaboration is the visible activity: people talking, sharing documents, sitting in the same meetings. Co-creation is what happens underneath it, when people with different expertise, incentives and blind spots actually build something together that none of them could have built alone. Behavioural psychologist, keynote speaker and author Duncan Stevens treats co-creation as the fifth pillar of Duncan Stevens’ MAGIC Wheel of High Performance™, the framework behind his book Everything You Need to Win: 23 Principles of High Performance Psychology for Business and Life. Most organisations have plenty of collaboration and very little co-creation, and the gap between the two is where good ideas quietly go to die.
What collaboration actually means in a performance context
Collaboration, in the sense most organisations use the word, describes proximity. People are collaborating if they are in the same project, on the same call, or copied into the same thread. It is a description of contact, not a description of outcome.
Co-creation asks a harder question: did anything actually change because these people worked together, or did they simply divide the task, defend their own piece of it, and stitch the results together at the end. That second pattern is extremely common and looks identical to collaboration from the outside. The meeting happened. The document has everyone’s initials on it. Nothing was genuinely built jointly.
Research on persuasion and social influence by Robert Cialdini points to something relevant here: people are far more likely to commit to an idea, defend it under pressure and follow through on it when they have had a genuine hand in shaping it, rather than simply being consulted on someone else’s version. That distinction between shaping and being consulted is close to the whole difference between co-creation and collaboration. Consultation produces agreement. Co-creation produces ownership, and ownership is what survives contact with a difficult quarter.
This is why so many organisations describe themselves as highly collaborative while quietly producing work that feels compromised rather than sharp. The word has been stretched to cover almost any interaction between two or more people, which makes it useless as a diagnostic. Asking whether a team collaborates well is rarely the useful question. Asking whether they co-create is much harder to answer honestly, which is exactly why it is worth asking.
What collaboration is not
Collaboration is not the same as consensus. Consensus often means the idea has been sanded down until nobody objects to it, which is a different achievement to nobody actually wanting it.
Collaboration is not the same as being nice to each other. Warmth makes meetings pleasant. It does not, on its own, make the thinking any better, and plenty of warm, agreeable teams produce mediocre work because nobody is willing to be the person who disagrees.
Collaboration is not a meeting cadence. Adding more touchpoints to a project does not increase the amount of genuine co-creation happening inside it. It usually just increases the amount of updating.
And collaboration is not the absence of conflict. Some of the most productive co-creation Duncan Stevens has seen inside senior teams has involved real disagreement, handled well, rather than the appearance of harmony covering for a lack of honest input.
Collaboration as a team and organisational issue
Co-creation is rarely an individual failing. It is usually a structural one. Teams end up with collaboration instead of co-creation because the system around them makes genuine joint thinking expensive and the appearance of collaboration cheap.
Consider how most cross-functional projects are actually run. Each function is asked for input, usually separately, usually late, usually after the direction has already been set by whoever convened the project. What gets called collaboration is really a sequence of one-way contributions into a plan that was substantially fixed before anyone else was consulted. People show up, their input is noted, and the plan proceeds largely unchanged.
There is also an incentive problem sitting underneath the structural one. Most performance reviews still measure individual output, even inside teams that are told their success depends on working jointly. When the reward system quietly favours protecting your own contribution over strengthening someone else’s, people behave accordingly, whatever the team charter says about collaboration. Co-creation asks people to spend effort improving work they will not get individual credit for. Few systems make that an easy trade to keep making.
Genuine co-creation requires the opposite sequencing. It requires bringing the relevant people in before the direction is fixed, when their expertise can actually change the shape of the thing, not afterwards when their role has quietly narrowed to approval. That is a harder meeting to run and a slower one to start. It is also the only version that produces work better than any single contributor would have produced alone.
Why pressure exposes the difference
Pressure is where the difference between collaboration and co-creation becomes visible, because pressure removes the time that collaboration relies on to look convincing. When a deadline tightens, the organisation defaults to whatever pattern is actually built into it, not the pattern it would prefer to claim.
Under pressure, teams that only ever had collaboration tend to fragment fast. Each function retreats to its own piece of the problem, defends its own territory, and stops checking whether the pieces still fit together. The meetings continue. The joint thinking stops.
Teams with genuine co-creation behave differently under the same pressure, not because they are calmer people, but because the habit of building things together was already load-bearing before the deadline arrived. The muscle exists, so it gets used automatically rather than abandoned under strain. This is the pattern Duncan Stevens looks for when working with senior teams: not whether collaboration exists when things are calm, but whether it survives the first genuinely difficult week.
The Handoff Audit
One practical way to surface the gap between collaboration and co-creation is what Duncan Stevens calls the Handoff Audit.
Take any project currently in progress and map the points where work passes from one person or function to another. At each handoff, ask two questions. First, did the person receiving the work have any influence over how it was shaped before it reached them, or did they simply inherit a finished decision. Second, did the person handing it over understand the constraints the next person is now working under, or were those constraints invisible to them at the time.
Most projects reveal the same pattern once mapped this way. The early handoffs look like collaboration and function like sequential delivery. The people upstream rarely know what the people downstream actually need, and the people downstream rarely get a say early enough to change anything meaningful.
The audit works because it produces something concrete rather than another abstract conversation about culture. A leader cannot easily act on the observation that the team should collaborate more. A leader can act on the observation that the finance function is only seeing a proposal after the commercial team has already committed to a number, and can move that handoff two weeks earlier next time.
Fixing this does not require a new tool or a longer meeting schedule. It requires moving one or two of those handoffs earlier, so the people affected by a decision are in the room while it is still a decision rather than a document. Even a single relocated handoff, done consistently, tends to expose how much of what a team calls collaboration was actually just well organised sequencing.
Frequently Asked Questions About Collaboration in High Performance
The best definition of collaboration in a workplace context is joint contribution to a decision or piece of work before it is finalised, not simply consultation on a decision someone else has already made. Genuine collaboration means the people involved could have changed the outcome, not just commented on it. Where that influence is missing, what looks like collaboration is usually just sequential delivery with extra meetings attached.
Collaboration in teams generally falls into a small number of recognisable patterns, ranging from simple information sharing between functions through to genuine joint problem solving where the end result belongs to no single contributor. Most organisational collaboration sits at the lower end of that range, involving updates and sign-off rather than shared authorship. Moving collaboration further up that range usually depends on when people are brought into a decision, not how often they meet.
Effective collaboration depends less on a fixed set of rules and more on the timing and honesty of the input people are given. The most consistent factor is bringing relevant people into a decision while it can still be changed, rather than after the direction has been set. A close second is tolerating enough disagreement in the room that problems surface early, since teams that optimise for harmony over honesty tend to discover their real problems much later and at a higher cost.
Where this lands for leaders and event organisers
For leadership conferences, cross-functional programmes and senior team events, this is where Duncan Stevens’ work is most relevant. As a collaboration keynote speaker, he helps audiences understand why teams that look collaborative on paper still fail to produce genuinely joint thinking, and what changes when the sequencing of a project is redesigned around it.
The MAGIC Wheel of High Performance™ provides the broader framework. Everything You Need to Win expands the thinking. The keynote brings the ideas into the room in a way people can feel, remember and apply.
Collaboration describes who was in the room. Co-creation describes whether the room actually changed anything.
If you are exploring a speaker for a leadership event, corporate conference or podcast where these ideas would fit, get in touch.
A Bit More About Duncan Stevens - Behavioural Psychologist and Keynote Speaker
Duncan Stevens is a behavioural psychologist, international keynote speaker and author of Everything You Need to Win: 23 Principles of High Performance Psychology for Business and Life. He is the creator of the MAGIC Wheel of High Performance™ and has delivered more than 1,000 presentations across 30+ countries, working with organisations including Shell, Microsoft, KPMG and Deloitte.
