What Your Clients Wish You’d Asked Them

Most project reviews in architecture and engineering follow a familiar pattern. Was the project delivered on time? Did we meet the brief? Were there any major issues? The answers are usually reassuring. The project team leaves with the impression that the project was a success, the client appears satisfied, and everyone moves on to the next commission.

On paper, this seems perfectly reasonable. After all, if a project was delivered successfully and the client is not complaining, what more is there to discuss?

Quite a lot, as it turns out.

Over the years, I have conducted hundreds of independent interviews with clients of architecture and engineering firms. These conversations often take place after a project has been completed or at key stages in an ongoing relationship. What I hear in these interviews is frequently very different from what appears in formal project reviews.

Not because clients are dishonest. Quite the opposite.

Most clients are thoughtful, reasonable people who genuinely value their professional relationships. That is precisely why they often choose not to raise concerns during a project.

Many clients worry that raising issues will create tension, damage working relationships, or be interpreted as criticism of individuals. Others simply decide that a concern is not significant enough to justify an awkward conversation.

So they say nothing. Yet that does not mean the concern disappears.

Perhaps communication became less proactive as the project progressed. Perhaps meetings became increasingly focused on technical matters while broader business objectives were forgotten. Perhaps decisions were made without sufficient consultation. Perhaps emails took too long to answer, or responsibilities became unclear.

Individually, these issues may seem minor. Collectively, they shape the client’s experience of working with your organisation.

The challenge is that many project reviews focus almost exclusively on project delivery rather than relationship quality.

Technical performance matters enormously. Clients expect competence, expertise and professional delivery. But technical competence alone is rarely what determines whether a client returns with future work.

Long-term client loyalty is often built on entirely different factors:

How easy was the team to work with?

Did the client feel listened to?

Did people take ownership when problems arose?

These are often the factors clients remember long after technical details have been forgotten. Unfortunately, they are also the factors most likely to be overlooked during formal project reviews.

When project teams conduct debriefs, they often ask questions that confirm what they already know.

Were the deliverables satisfactory?

Was the programme achieved?

Did we meet expectations?

While these questions are important, they rarely uncover the insights that matter most. Clients can answer “yes” to all of them and still decide not to appoint the same team again.

The reason is simple: clients answer the questions they are asked, not the questions they wish had been asked. The gap between what clients say and what they actually feel can therefore be surprisingly large. This is where better questions become incredibly valuable.

A more effective project debrief moves beyond project performance and explores the client’s experience of the relationship itself.

For example:

Was there anything during the project that frustrated you but never felt important enough to raise?

This question often unlocks insights that have been sitting below the surface for months. Small frustrations rarely appear in project reviews, yet they frequently influence future appointment decisions.

Were there moments when communication could have been better?

Communication is one of the most common sources of client dissatisfaction, yet it is rarely discussed in sufficient detail. Asking this question creates an opportunity for clients to be specific without feeling confrontational.

Did you always know who to contact when issues arose?

Clients often assume firms understand how confusing internal structures can appear from the outside. What feels obvious internally may feel fragmented to a client managing multiple stakeholders.

What could we have done differently to make your experience easier?

This shifts the conversation away from project outcomes and towards client experience. It encourages practical suggestions that can improve future relationships.

If you were appointing a team again tomorrow, what would you want them to know?

This is one of the most revealing questions of all. It invites reflection and often uncovers expectations that were never explicitly discussed during the project.

What makes these questions powerful is that they focus on experience rather than performance.

Most clients are willing to discuss what happened during a project. Far fewer are routinely asked how it felt to work with the team. Yet this is often where the most valuable insight resides. In many cases, the most important feedback is not about what went wrong. It is about missed opportunities.

Opportunities to strengthen trust.

Opportunities to demonstrate greater understanding of the client’s priorities.

These are the insights that can transform a satisfactory client relationship into a lasting one.

The irony is that many firms invest heavily in winning new clients while overlooking the information that could help them retain and grow existing relationships.

The cost of acquiring a new client is often significantly higher than the cost of retaining an existing one. Yet relatively few organisations invest time in understanding how their current clients truly experience working with them.