Client and supplier, one team

The relationship between client and supplier is often described as a match between two teams: on one side the people who pay and demand, on the other the people who work and defend themselves. As long as it is lived that way, every project is an endless negotiation, and the result suffers.

The best projects happen when the two sides behave as one team, with a shared goal. That doesn’t mean being friends: it means being allies, within clear boundaries.

“They didn’t understand the brief”

It is the most common client complaint, and the fault almost never lies with one side only. Behind it there is usually a vague or incomplete brief, a superficial knowledge of the sector or the audience, little room to discuss and clarify, sometimes simply words used differently.

The most effective solution is also the rarest: writing the brief together, or at least discussing it together before handing it over. A shared brief aligns expectations from the start, leaves less room for interpretation and, when priorities change, allows faster adaptation, because both sides know the reasons behind the choices. In a pitch it isn’t always possible; in a direct assignment, it almost always is.

The first project as a watershed

A collaboration can begin with all the esteem in the world, but the real test is the first project together. Until then, on both sides, there is a veil of doubt.

The client wonders whether the team will be up to it, whether they will really understand the vision, whether they will keep to time and budget. The team feels the pressure to prove its worth, has to learn the client’s way of working and calibrate expectations without disappointing them.

To get through the baptism of fire:

• The client makes expectations explicit, with concrete objectives; shares doubts as they arise, not at the end; gives trust, avoiding micromanaging every step.
• The team listens and asks questions, especially at the start; shows progress regularly and involves the client in the choices; is flexible when needed, and clear when something isn’t possible.
• Both share a plan and keep it up to date. And when the project goes well, they celebrate together: it is the best way to start the next one.

Trust is cultivated

Trust is like a plant: it needs care every day, and without care it withers. It is built from a few things, repeated over time.

• Open communication. Sharing problems and worries, not just successes.
• Respect for each other’s expertise. The client knows their market better than anyone; the supplier knows their craft.
• Reliability. Keeping promises, small and large. One deadline met is worth more than ten reassurances.
• Constructive feedback, in both directions.

Transparency, even when it costs

With the client, transparency means giving the real status of the project, flagging problems as soon as you see them, explaining the reasons for choices, putting decisions and changes in writing. Good documentation is not there to defend yourself: it is there to remember, and to settle disagreements before they become disputes.

Inside the team, it means sharing the information people need to work, explaining how decisions are made, creating a climate where doubts and concerns can be voiced without fear of consequences.

And it also means something uncomfortable: accepting everything in silence is not transparency. Whoever takes on every change without saying what it costs doesn’t buy client satisfaction: they postpone it, and meanwhile run up a bill that will arrive sooner or later.

Knowing how to say no

Saying no is one of the most important skills for anyone running a project, and one of the hardest. It protects the project from requests that don’t fit its objectives, budget and timing; it protects resources, which are always limited; it protects the team, and yourself.

How to say it:

• Listen all the way through, even if you already know the answer will be no. The request deserves respect, and sometimes it hides a need that can be met another way.
• Be clear. No beating about the bush, no “we’ll see” that really means no.
• Explain why, briefly, and make sure the reasons are understood, even if not shared.
• Offer an alternative. The most useful no is a “yes, if…”: yes, with an agreed extra; yes, moving the delivery date; yes, dropping something else. Or a “not like that, but like this”.
• Own your no. Don’t hide behind “the company won’t allow it”.
• If they insist, repeat calmly. “I understand, but I can’t accept this request” doesn’t become truer by raising your voice.

Guilt almost always shows up. It is worth remembering that a no said well, at the right time, protects the relationship far more than a yes said to avoid discomfort and then not kept.

The same goes for the team: saying no to an exciting creative idea that is out of scope is hard. Explaining why, and perhaps keeping it for the right project, is how you avoid killing the enthusiasm.

More than one contact

Finally, a practical rule: a solid alliance needs more than one point of contact. If your only contact changes job, falls ill or simply disappears, the project can’t stop with them.