Overthinking Client Feedback? Separate the Words from What You Added

By Thomi Sechehaye

You send the work. The client replies: “Looks fine.”

You read it again. Fine. Not excellent. Not even good. By the third reading, you are preparing your defense before a committee that has yet to be formed.

If you are overthinking client feedback, begin with the exact words and separate them from the meaning you supplied. Then check whether anything important remains unclear.

You may need a practical clarification, a fuller conversation, or simply permission to stop interpreting a sentence that has already done its job.

The first reading is a place to begin. It is not always enough to act on.

What the message actually establishes

“Looks fine” tells you that the sender wrote those words about something you sent. Depending on the surrounding conversation, it might indicate approval, mild satisfaction, limited attention, or something else.

It does not automatically establish disappointment.

It also does not automatically establish permission to publish. If the project requires explicit approval, that is a separate question to resolve.

This distinction matters because reassurance and practical clarity are different needs. You may feel better after deciding the client is probably pleased while still lacking the authorization required for the next stage.

Ask what you need to know to proceed responsibly. That gives your attention somewhere useful to go.

Why tone deserves some caution

In five experiments reported in their 2005 paper, Justin Kruger, Nicholas Epley, Jason Parker, and Zhi-Wen Ngexamined communication over email and found evidence that people overestimate their ability to communicate tone successfully.

That research gives a reason to be cautious about assumed tone. It cannot tell you what your particular client meant, and it does not establish that a negative interpretation is always wrong.

For this exercise, treat tone as something that may need checking when the consequence matters. A warm interpretation can be an assumption too.

The aim is to understand the feedback well enough to respond, without turning uncertainty into a story about the relationship or the quality of your work.

Put the interpretation where you can see it

Here is an exercise to try with one message. Make three columns:

What they wrote	What I added	What needs checking
“Looks fine.”	They are disappointed but avoiding saying so.	Does this approve the current version for the next stage?
“Can we revisit the opening?”	The whole piece has failed.	Which part of the opening is not doing its job?
“Let’s discuss tomorrow.”	Something serious is wrong.	Is there anything I should prepare for the discussion?

The second column makes your interpretation visible. It may contain a reasonable concern. Once written down, you can examine what supports it and what else could explain the words.

Keep the third column narrow.

“Do they still respect me?” is a difficult question to resolve through a project email. “Which part needs revising?” gives both of you something specific to work with.

Responding to “looks fine”

Imagine you have sent a revised homepage draft and asked whether it is ready for the developer.

The client replies, “Looks fine.” You notice that you have interpreted the reply as reluctance.

Before responding, return to the thread.

Have they answered the question you asked? Is this how they usually approve work? Are there unresolved comments? Does the project require a clearer sign-off?

If approval remains uncertain, you could write:

“Thanks. Just confirming: is this version approved to send to the developer, or are there changes you would like first?”

That question resolves the practical ambiguity without asking the client to manage your interpretation of their enthusiasm.

If approval is already clear under the agreed process, another message may add little. Record the approval and take the next step.

You do not need every short reply to arrive with a small bouquet.

Use context without treating it as proof

The words are part of a conversation. Previous messages, agreed criteria, the project stage, and the sender’s usual communication all matter.

You might have a history of vague approval followed by extensive changes. In that case, your concern has context. A clearer review process may be needed.

You might also be reading a brief reply after a long day when the work feels unusually personal. That possibility deserves attention too.

Neither observation settles the client’s meaning on its own.

Write the relevant context beside the message. Separate what has happened before from what you predict will happen this time. Then decide which uncertainty warrants a question.

This keeps a genuine pattern available for discussion without making every new message evidence for it.

When the feedback is genuinely critical

Sometimes the client is dissatisfied. A careful reading should leave room for that.

If the reply says the opening misses the brief, identify the mismatch. Ask which requirement is not met, what the reader needs to understand, or what example would make the requested direction clearer.

You can take criticism seriously without expanding it into a verdict on your competence. A useful response connects the comment to the work and the next revision.

If feedback repeatedly remains too vague to use, propose more specific review questions for the next round.

For example:

“Does this explain the offer accurately?”

“Which claim needs stronger support?”

Clear questions give the reviewer a clearer task.

Try it on one message today

Copy the exact feedback. Write the meaning you added. Name one alternative explanation and any evidence that favors one reading over another.

Then choose: proceed, ask one focused question, or arrange a fuller conversation. Make the action proportionate to what is at stake.

Have a message you are still turning over?

Try The Blind Spot, the free Self Check from Force For Good. Bring that one situation. The questions help you separate what you know from what you have assumed, consider what needs checking, and choose a useful next step.

START THE FREE SELF CHECK →

Developed by Thomi Sechehaye, with ChatGPT assisting in drafting and editing for clarity and readability.