Feedback on client-facing work carries real stakes, because a genuine miss can cost the relationship, which makes it tempting to either soften the critique into uselessness or deliver it bluntly enough that it lands as a judgment on the person rather than the work.
Good feedback here does two things at once: it's specific enough to actually improve the work, and it's delivered in a way that keeps the person willing to ship the next thing without dread.
Feedback has to be honest and survivable at the same time
Feedback that's too soft to matter wastes everyone's time; feedback delivered so bluntly it feels personal makes people defensive instead of receptive. The goal isn't finding a middle ground between honest and kind, it's being both at once, specific and respectful in the same note.
Critique the work specifically, not the person generally
"This paragraph doesn't land because it buries the ask" is about the work. "You need to communicate more clearly" is about the person, and it lands very differently even when the underlying observation is the same. Keep feedback anchored to the specific piece of work in front of you.
In Stelaah, feedback can attach directly to the specific file, deliverable, or task it's about, keeping the critique tied to the work itself rather than becoming a general conversation. See how tasks works.
Name what's actually working, not just what isn't
Feedback that's entirely corrections reads as a verdict on the whole piece, even when most of it was fine. Naming what's genuinely working, specifically, not as a courtesy, gives an accurate picture and makes the corrections easier to hear as targeted rather than global.
Explain why a change matters, not just that it's needed
"Change this" without a reason reads as arbitrary preference. "Change this because the client has flagged this exact pattern before" gives the person real information they can apply to the next piece of work, not just this one.
Give feedback before client delivery, not as a postmortem
Feedback given after a client has already seen something wrong doubles as a report of a real failure, which raises the emotional stakes considerably. Catching it before it ships keeps the same feedback focused on improvement rather than damage control.
A simple checklist
If you do nothing else, do these five things:
- Critique the specific work, not the person in general terms.
- Name what's genuinely working alongside what needs to change.
- Explain why a change matters, not just that it's required.
- Give feedback before client delivery whenever possible.
- Keep the tone respectful even when the critique is direct.
Do that, and feedback becomes something that improves the work without making the next person hesitant to show you theirs.
Run your client work in one place. Stelaah keeps projects, clients, contracts, and invoices together, with Aria for the busywork.
Start freeWe build Stelaah, the workspace for client work. We write about running teams, agencies, and venues without the busywork.
