By Martina Francis · Le Chene
A contract creates an opening, not a partnership
It is easy to call any supplier relationship a partnership. The distinction becomes clear when a problem changes. In a transactional relationship, each party returns to the terms it negotiated. In a productive partnership, both sides understand the outcome, make the constraints visible and work through the decision together. That takes commercial clarity, but it also takes trust, candour and a willingness to invest time in the work beyond a signature.
The first conversation should therefore cover more than scope and price. What does success look like for each side? Who is affected by the work? Which assumptions might fail? Who can make a decision when the original plan no longer fits? These questions make it possible to disagree early, when a change is still inexpensive.
Co-design changes the quality of delivery
When partners design with the people who will implement a solution, the work becomes more useful. A market-entry strategy needs local knowledge. A digital product needs operational owners who can sustain it. A capability programme needs managers who can make space for people to practise. No single organisation has every perspective. Effective partnerships bring those perspectives into one working process.
Co-design is not a series of endless workshops. It is an agreed way to surface evidence and make decisions. Put a small cross-functional group around a shared problem; give it a clear owner, a timeline and a way to test what it produces. Bring disagreement into the room instead of allowing it to reappear during implementation.
Mutual accountability is the differentiator
A good partner can say where its own approach needs to change. It can challenge a client's assumption respectfully and receive the same challenge in return. That openness has practical consequences: fewer handovers, faster resolution of exceptions and a clearer view of who will do what next. Shared measures should track the outcome both parties care about, not only the volume of activity completed.
A partnership should also create capability on both sides. If the client depends indefinitely on the partner to make routine decisions, the model has not matured. Document how knowledge will move between teams and what the client should be able to own when the engagement ends.
The test is what happens under pressure
When timelines tighten or market conditions shift, a partnership is tested in the quality of the conversation. Do the teams raise a difficult issue quickly? Can they reallocate expertise without losing accountability? Are customer and employee effects considered alongside the commercial case? Those behaviours matter more than a label on a slide.
For Le Chene, partnerships are a way to assemble the right people around a client's challenge and stay connected from design through delivery. The aim is to build something useful together, with each party stronger because of the work.
If an opportunity needs more than a supplier, start by defining the outcome both sides are prepared to own.