Collaboration produces outputs. Collective sensemaking produces understanding. The difference is not a matter of degree. It is a matter of what you are trying to build.
Most tools for working together are designed to produce an output: a document, a decision, an action plan. The question they answer is: what did we agree? Collective sensemaking asks a different question: what do we understand together?
What collaboration tools do
Collaboration platforms are built to coordinate activity toward a shared deliverable. They track tasks, manage versions, log communication, and enable concurrent work. They are genuinely useful for what they are designed to do — which is produce an output from distributed effort.
What they cannot produce is shared understanding. When two people finish a collaborative task, they have a jointly produced document. They do not necessarily understand the question behind the task in the same way, share a picture of the territory the document describes, or know why the other person made the choices they made. The output exists. The understanding may not.
What collective sensemaking does instead
Collective sensemaking is the process by which a group builds a shared map of how they understand something complex — not what they have decided, but how they are thinking. It preserves the reasoning, the connections between perspectives, the points of convergence and the points where genuine disagreement or uncertainty exists.
A SparkMap is not a document. It is a living structure of how a group's understanding is forming — each contribution carrying its epistemic ground (the type of knowledge behind it: expert fact, research, lived experience, belief, values, gut feel), each connection between contributions preserving the reasoning that links them. What accumulates is not a record of what was said. It is a map of how a group is making sense of something.
Collaboration produces a document that can be read. Collective sensemaking produces a map of understanding that can be continued.
Why the distinction matters for decisions
Organisations make consequential decisions on the basis of understanding — or the absence of it. When the understanding behind a decision is thin, the decision is brittle: it fails to anticipate what it will encounter, it cannot be adapted when circumstances change, and the people expected to implement it were not part of building the reasoning that produced it.
When the understanding is genuine — when it has been built collectively, characterised carefully, and preserved so that the reasoning is visible — the decision is more robust. Not because more people agreed with it, but because the understanding behind it was richer, more diverse, and more honest about where certainty ends and uncertainty begins.
What collective sensemaking is not
It is not brainstorming. Brainstorming generates a volume of inputs; collective sensemaking builds the connections between them and preserves the epistemic diversity that makes those connections meaningful.
It is not consultation. Consultation asks for responses to pre-defined questions; collective sensemaking builds understanding that may question the framing of the question itself.
It is not group decision-making. Group decision-making converges on an output; collective sensemaking maps the understanding that makes good decisions possible, including the understanding of where uncertainty is genuine and resolution would be premature.
Collective sensemaking is the process before the decision — the one that determines whether the decision, when it comes, is built on genuine understanding or the appearance of it.