Cooperation

Cooperation: Partnership

From proudly invented here to proudly co-created with others. Contracting, communication, consequence management — the three skills of cooperation. And the four observable signals that tell you whether you have it.

Sari van PoeljeSari van Poelje
7 min read
ShareLinkedInXFacebook
Partnership and cross-functional cooperation

Partnership is the software of Cooperation — the relational quality that makes genuine collaboration possible. It is the shift from 'proudly invented here' to 'proudly co-created with others'. This shift is harder than it sounds, because most organisations have been built on the assumption that the best ideas come from within, and that sharing credit dilutes it.

The research on open innovation tells a different story. Henry Chesbrough's work at Berkeley showed consistently that organisations that actively seek external ideas and partnerships outperform those that rely solely on internal R&D. The reason is not that external ideas are better — it is that the combination of internal capability and external perspective produces something that neither could produce alone.

Partnership, in the context of the ABI model, operates at three levels: within teams, between teams, and between the organisation and its external partners. Each level requires the same three skills: contracting, communication and consequence management.

Contracting means making explicit agreements about what each party will contribute, what each party will receive, and what will happen if the agreement is not honoured. Most partnerships fail not because of bad intentions but because of unclear contracts — because the parties assumed they understood each other's expectations and discovered too late that they did not. Good contracting is not bureaucratic. It is respectful: it treats the other party as someone whose time and energy deserve clarity.

Communication means maintaining the quality of information flow that the partnership requires. This is harder than it sounds in complex organisations, where information gets filtered, delayed and distorted as it travels across boundaries. Partnership communication requires active investment: regular check-ins, honest updates, early warning of problems, and the willingness to have difficult conversations before they become crises.

Consequence management means following through on the agreements that were made — and addressing it directly when they are not honoured. This is the skill that most organisations are weakest at. When a partner fails to deliver, the path of least resistance is to absorb the impact and say nothing. The result is a partnership that continues to function on the surface while the underlying trust erodes. Consequence management is not punitive — it is the discipline of taking agreements seriously enough to address them when they are broken.

There are four observable signals that tell you whether genuine partnership exists in an organisation. The first is whether people speak well of their colleagues in other teams when those colleagues are not in the room. The second is whether people proactively share information that would be useful to others, even when sharing it is not required. The third is whether people raise problems early, before they become crises. The fourth is whether people take collective accountability for outcomes, rather than attributing failure to others.

Partnership is not a natural state. It is a cultivated one. It requires consistent investment in the relationships that make it possible — and consistent leadership behaviour that models the quality of cooperation the organisation is trying to build.

Sari van Poelje

Sari van Poelje

Author of Mastering Agility (Routledge, 2024). Thirty years helping leadership teams build the four abilities of agile business innovation design.

Found this useful?Share on LinkedInShare on X

You might also like

More in Cooperation