The method
What is Structured Collaboration?
Structured Collaboration is a practical method for helping people across a complex organisation work well together. It combines three things:
- the will to collaborate
- the structures that bring interdependent people together
- the agreements those people reach, and keep current, about how their work connects
© Alex McDonnell
The core idea
Collaboration shouldn’t depend on heroics. It should be how the organisation is designed to work.
Traditional structures such as org charts, reporting lines and responsibility matrices are static. They show who reports to whom, not how work moves between people.
Structured Collaboration adds a structure that moves with the work: alignment without micromanagement, and autonomy without fragmentation.
The three elements
Three things, working together.
Each strengthens the others. When collaboration starts to work, the will to collaborate grows.
01 / The will
The will to collaborate
Shared purpose, trust, and respect for what others need, with leaders who model it. It can’t be ordered, but it can be encouraged, and it grows when people see how their work connects to everyone else’s.
02 / The structures
The structures that make it happen
The roles, forums, rhythms and tools that bring interdependent people together at the right moment: someone who owns each end-to-end process, a senior forum where connected decisions are made together, and regular reviews between teams that rely on each other.
03 / The agreements
The agreements they produce
A clear, shared understanding of who depends on whom, for what, to what standard, and what happens when something goes wrong, reviewed as the organisation changes.
“The will to collaborate is necessary. On its own, it’s not enough.”
Goodwill brings people to the table. Structures and agreements turn those conversations into work that flows.
Interfaces
Collaboration happens at the interfaces.
An interface is any point where one team depends on another for an input, a service, a decision or a result.
A project team hands a new system over to customer support at go-live. What does support need to know, by when, and who fixes what in the first month? Leave that open and every issue becomes an argument. Agree it once and the handover becomes routine.
The Structured Collaboration Canvas®
Five questions for every interface
- Who depends on us?
- What do they need from us, and to what standard?
- What do we do to provide it?
- What do we need in order to do that well?
- Who do we depend on for it?
Matching structure to need
Not every interface needs the same weight of structure.
A routine handoff needs a short, clear agreement. A high-stakes decision that crosses several functions needs the right people deciding together. The Continuum of Collaboration helps you judge which is which. Too much structure costs as much as too little.
One logic, three levels
Learn it once, use it everywhere.
01 / Senior teams
Concurrent Management
The people responsible for connected parts of the business make connected decisions together, while those decisions can still be shaped.
02 / Across teams and functions
Designed interfaces
Teams agree what flows between them, what good looks like and how problems are resolved.
03 / The whole business
A shared picture
The Business User Manual and the Agile Business Execution Canvas® show how the organisation creates value and how its parts fit together.
What changes
What leaders notice.
01
Faster decisions
Fewer escalations, and shorter, more decisive meetings.
02
Reliable handoffs
Handoffs that hold up without chasing.
03
Systems that stick
New systems that people actually adopt, because the way of working was agreed first.
04
Less key-person risk
Less dependence on a few key people.
05
Quicker onboarding
New starters who understand how things work sooner.
Common questions
Questions leaders ask.
Isn’t this more bureaucracy?
No. Most friction comes from too few agreements, not too many rules. Structure supports good behaviour so people spend less time chasing and escalating.
How is it different from a RACI chart or process maps?
Those record who does what at a point in time. Structured Collaboration creates the forums and rhythms that produce agreements and keep them current as things change.
Isn’t self-management the answer?
Laloux and others show what teams close to the work can achieve when they’re trusted to decide. But autonomy still needs clear interfaces, or independent teams simply drift apart.
Where do we start?
With the one or two interfaces causing the most pain. Improving those builds the will and the confidence to go further.
Start a conversation