Insights
What the evidence tells us. What we have learned designing collaboration in the real world. And what becomes possible when people, organisations and systems learn to work better together.
Start here
Four articles that set out how we think about collaboration — as a design discipline, a system, and a measurable return.
Why the quality of the connections matters as much as the quality of the people.
02Trust matters. So do purpose, information flow, governance, coordination and the way the whole system fits together.
03A practical way to think about Return on Collaboration — the value created that could not have been created alone.
04Psychological safety helps information surface. Collaboration becomes powerful when safe voice is paired with productive challenge, accountability and the ability to turn truth into action.

What the evidence says about how groups actually perform together.

Turning intent into conditions, structures and practice.

Coordination problems that no single organisation can solve alone.
All insights
30 insights
Collaboration often begins with energy and goodwill. It becomes durable when purpose, decision rights, roles, information flows and accountability are deliberately designed.
Sociocracy can distribute authority, widen voice and speed some decisions. The stronger question is not whether every organisation should adopt it, but which principles improve the collaboration problem in front of us.
Psychological safety helps information surface. Collaboration becomes powerful when safe voice is paired with productive challenge, accountability and the ability to turn truth into action.
Positive emotion, meaning, relationships, strengths and agency are usually discussed at the individual level. Collaboration design asks what happens when we treat them as resources for collective capability.
Collaboration problems are often blamed on attitude when they are rational responses to organisational design. Culture changes when the system sends different signals about information, incentives, power and recognition.
The most interesting use of AI in workshops is not replacing facilitation. It is helping groups hear themselves - synthesising patterns across conversations and feeding them back into human sensemaking.
The workshop is only one intervention in a collaboration system. The next generation of facilitation designs stakeholder composition, governance, information flows, technology and follow-through around the room as well as inside it.
Groups often equate harmony with collaboration. But premature consensus can suppress information. Strong collaboration preserves difference long enough to improve the decision, then uses clear rules to move.
A seat at the table is not the same as influence. Collaboration design has to account for differences in authority, resources, status, dependency and the ability to absorb risk.
Collaboration consumes time, money and attention, yet organisations rarely measure its additional value. Return on Collaboration makes the counterfactual visible: what happened because we worked together?
Scope 3 turns decarbonisation into a collaboration problem. Emissions sit across independent organisations, so progress depends on influence, data, procurement, financing, capability and shared innovation.
Supplier climate programmes often stall at data collection. The next step is designing a maturity pathway that helps suppliers measure, build capability, access incentives and change operations.
Procurement is often treated as a transactional function. Used strategically, it can aggregate demand, reduce market uncertainty and create collaboration between buyers, suppliers and innovators.
A shared dashboard cannot fix a relationship in which participants have good reasons to withhold information. Collaboration design has to make data sharing purposeful, safe and mutually valuable.
The 17 SDGs are usually treated as a list of outcomes. Their deeper value may be as a shared language for coordinating governments, business, finance, academia and communities across interdependent challenges.
Climate, biodiversity, water, food, pandemics and AI governance are not owned by any single actor. Their difficulty comes partly from fragmented authority, incentives, knowledge and time horizons.
A multinational's impact is not contained by its legal boundary. Procurement, standards, investment, product design and partnerships can cascade through thousands of organisations and regions.
GDP is valuable for measuring economic production, but it was never designed as a complete measure of social progress. Collaboration needs the same discipline: measure outcomes and capabilities, not only activity.
Competitive advantage is increasingly shaped not only by assets inside the firm but by the quality of the networks, partnerships and ecosystems the firm can mobilise.
Partnerships connect two organisations. Systems collaboration asks how many independent actors can share enough purpose, information, governance and infrastructure to become collectively capable.
Why the quality of the connections matters as much as the quality of the people.
Trust matters. So do purpose, information flow, governance, coordination and the way the whole system fits together.
A practical way to think about Return on Collaboration — the value created that could not have been created alone.
A room full of aligned people is only potential. Collaboration creates value when alignment becomes coordinated action.
The most powerful ecosystems know where to compete, where to cooperate and how to design the boundary between the two.
Different perspectives create possibility. Good collaboration design turns that difference into better thinking.
Complex challenges cross organisational boundaries. Collaboration design makes the interfaces visible and workable.
AI can help groups hear more, synthesise faster and see patterns they would otherwise miss — while humans retain context, judgement and responsibility.
The strongest value-chain transformations are built with suppliers, not merely pushed through procurement.
Finding an idea is not the same as getting it adopted. The hard part is coordinating the boundaries between discovery, testing, procurement and scale.
If you are working on a challenge where the outcome depends on people, organisations or systems working differently together, we should probably talk.