37. Staging a Client Review So Feedback Stays on One Thread

Client feedback becomes expensive when it lives in five places. A designer receives a WhatsApp voice note, an email from a second director, a comment on an old PDF, and a paragraph in a group that includes someone's uncle. None of these people are wrong to care. The project is wrong to have no stage on which care is collected. Staging a review means choosing a moment, a file, and a thread, then refusing to treat side comments as decisions.

Malaysian SME projects often involve a founder who is on the shop floor and a relative who handles the bank. Both need a say. They do not need parallel negotiations. One thread, with one current version of the work, keeps the say in the open. It also gives you a record when the invoice later asks for a fourth round of changes that nobody remembers approving.

<>

Set the review before you send the work

Tell the client how you will review before the first design or the first draft goes out. Name the date, the person who collects comments, and the tool. A shared document, a board, or a single email thread can all work. A chat can work if you paste a summary back into the thread and ask them to confirm it there. What does not work is accepting decisions that only exist inside a voice note you cannot search next month.

Send one link to the current version. Kill old links, or mark them clearly as old. People comment on the file they can find, which is often the first one. Put a version number and a date in the filename. Homepage v3, 12 March is boring and perfect. Ask for comments by a stated time so your team can plan the next day. An open-ended review is how a five-day task becomes a five-week mood.

Keep every decision on the same thread

When a comment arrives elsewhere, move it. Reply briefly. Thank you. I have copied this onto the review thread so everyone sees the same list. Then actually copy it. Do this even when the side message is from the person who pays you. You are not being difficult. You are protecting them from a second approver who never saw the change. If they insist on a call, send a short note afterwards listing what you heard and ask them to correct it on the thread.

• One current file, with a version and a date.
• One person on the client side who gathers comments.
• A deadline for the round.
• Comments written on that file or that thread.
• A recap of what will change before you do the work.

Separate preference from contradiction. If one comment says the button should be green and another says it must stay blue, do not average them in private. Ask the named approver to choose on the thread. Your job is to make the conflict visible while it is still cheap. Fixing a contradiction after development is how small sites blow their budgets.

<>

Close the round in writing

At the end of the window, post a recap. We will change the hours, we will not add a new page in this round, and we are waiting on a logo file from you. Ask for a yes. Silence is not a yes unless your agreement says that a passed deadline means proceed, and even then a recap is kinder. Start the work from the recap, not from your memory of the chat. Attach the recap to the invoice later if the scope is questioned.

A review is finished when the decisions are written down, not when everyone feels they have spoken.

Limit the number of rounds in the proposal so the thread has a horizon. Two rounds of consolidated comments is a common shape for a small site. A round is not a single message. It is a collected set. Explain that distinction at kickoff so nobody thinks a typo fix consumed a round, and nobody thinks an entirely new section is a tiny comment. The thread stays calmer when the shape was agreed early.

<>

Teach the habit without a lecture

The first time you redirect a side message, some clients will feel rebuffed. Keep the tone warm and repeat the reason. Everyone, including you, needs one place to look. After one successful round they usually prefer it, because they can see that their sister's comment was not lost. If a client cannot work this way at all, decide whether you will price the chaos or decline it. Do not pretend a scattered review is free.

Store the thread or export it when the project ends. Handover should include the approved version and the recap, not a zip of every stray screenshot. The next person who edits the site, whether that is your staff or the client's nephew, deserves to know which comments won. One thread is how a small project remembers itself.

If a round produces more comments than you can answer in one sitting, group them before you reply. Typos in one cluster, layout in another, new requests in a third. Answer the cluster, not the panic. Clients relax when they see their notes organised instead of argued with one by one in the order they were typed late at night.