Before the Room Fills: A Pre-Kick-Off Risk Note for UK Client Work

The first client workshop has a habit of becoming a performance of agreement. Everyone arrives with good intentions, a printed agenda and a reasonable desire to get on. The room is usually warm, the coffee is usually adequate, and the difficult questions are usually deferred. That is not because clients are dishonest or delivery teams are naive. It is because early-stage workshops reward momentum. A short note sent two working days before the room fills can interrupt that pattern without turning the kick-off into an inquest.

The case for asking early

Most project disappointments are not caused by a single dramatic error. They accumulate from small misalignments: a decision that arrives later than everyone assumed, a stakeholder who was never really convinced, a reporting line that looks clear on paper but is ambiguous in practice. By the time these issues appear in a risk log, they have often acquired a history. People know something is wrong, but nobody wants to be the first to say it plainly.

The pre-kick-off note is a modest attempt to change the sequence. It asks the client, in writing and before the first workshop, what would make the project a disappointment six months from now, and which early warning signs would matter. The phrasing should be careful. It is not a request for a confession, still less a test of commitment. It is an invitation to share the private risk intelligence that clients often hold but do not volunteer in a group setting.

Four prompts, five minutes

The note should be short enough to answer in five minutes and structured enough to produce a useful reply. Four questions are usually sufficient.

First: if this project is judged a disappointment six months from now, what is the most likely reason? Second: which early warning sign would you want us to bring to your attention immediately? Third: what decision or input is most at risk of arriving late? Fourth: what would make you quietly lose confidence, even if the milestones were being met?

Those questions do different work. The first invites the client to think in outcomes rather than tasks. The second creates a route for escalation before a problem becomes a complaint. The third exposes dependencies that are often hidden in governance diagrams. The fourth is the most useful of all, because it reaches the concerns that do not appear in status reports: tone, responsiveness, the sense that a supplier is present but not really listening.

Own the first answer

A pre-mortem note that asks the client to go first can feel like a trap. It is better to model the behaviour. Send your own likely failure modes alongside the questions. Keep them specific and non-defensive. For example: we may underestimate the time needed for sign-off from a dispersed stakeholder group; we may produce too much detail for the steering group and too little for the operational team; we may treat a polite silence as agreement.

This matters for tone. The exercise is not a ceremony of mutual suspicion. It is a joint acknowledgement that projects are exposed to human behaviour as well as technical complexity. When the supplier answers first, the client is more likely to reply in kind. The note also gives the client something concrete to react to, which is often easier than composing a risk list from a blank page.

Turn replies into shared language

A good reply should not disappear into a folder. At the start of the first workshop, pick up two or three themes from the note and put them on the wall, the flip chart or the shared document. Give them plain labels: late decisions, quiet disengagement, evidence gaps, approval drag. These labels become a shared vocabulary for the life of the project. They allow a delivery lead to say, without accusation, that a pattern is beginning to look like the risk the client identified at kick-off.

The note should also feed the project record. Add the agreed warning signs to the risk log, assign an owner to each, and review them at the first steering group rather than waiting for the first exception report. This is not bureaucracy for its own sake. It is how a five-minute ritual becomes a practical control. The portfolio page, when it is eventually updated, can then reflect not only what was delivered but how the work was governed.

Boundaries and tone

The note is not a contract, a risk register or a substitute for proper due diligence. It should not be sent to every client on every small piece of work. It is most useful at the start of a new engagement, a complex programme or a fixed-deadline project where several parties need to align quickly. The subject line should be plain: something like a short risk note before Monday. Avoid jargon in the client-facing version. Pre-mortem is a useful internal term; the client does not need it.

Nor should the exercise become theatrical. If the note invites catastrophe, it will receive either silence or a defensive reply. The aim is honest friction, not alarm. A measured question about disappointment is usually better received than a dramatic request to imagine failure.

Why it earns trust

Clients tend to remember how a supplier behaves when difficulty is first mentioned. A team that can ask about risk without panic, and can listen to the answer without becoming defensive, signals that it will be steady when the work gets harder. That is a commercial asset. It is also a quiet differentiator in a UK market where politeness can too easily be mistaken for alignment.

The ritual does not remove risk. It simply gives both sides a written starting point for discussing it. In a portfolio business, that benefit compounds. Each engagement begins with a record of what the client feared and what both sides agreed to watch. Six months later, when the work is busy and memories have softened, that record is often the most useful document in the file.