Talking a Client Through Work That Looks Unfinished
A woodworker I coached through a client presentation once showed up to a midpoint review with a chair that had no seat, no finish, and joints still held with clamps instead of glue. He was mortified.

A woodworker I coached through a client presentation once showed up to a midpoint review with a chair that had no seat, no finish, and joints still held with clamps instead of glue. He was mortified. The client, walking in cold, would see something that looked broken rather than something that was exactly on schedule. We spent twenty minutes before the meeting building three sentences that changed how the whole review went.
Anyone whose work is visibly built in stages runs into this same problem, and it has almost nothing to do with the quality of the work itself. A half-finished piece looks alarming to someone who has never watched the process before, and the maker's silence about that gap is what turns a normal checkpoint into a moment of client panic. The fix is not better work. It is a better thirty seconds of talking before anyone looks too closely.
Why unfinished work reads as a warning sign
A client without craft experience has almost no reference point for what stage six of eleven is supposed to look like. They know what a finished product looks like, because that is what they were shown in a portfolio or a proposal, and anything short of that gets measured against the wrong benchmark. Raw joinery reads as a mistake. Unsanded wood reads as carelessness. A dress with visible basting stitches reads as unraveling rather than as a deliberate, temporary structure doing exactly its job.
None of that reaction is unreasonable on the client's part. They are pattern-matching against the only image they have, the finished one, and the maker is the only person in the room who can supply the missing context. Skip that step and the client fills the gap with their own worst guess, usually that something has gone wrong and nobody has told them yet.
What actually needs to be said out loud
The useful sequence runs in three parts: name the stage, name what happens next, and name why it looks the way it does right now. Skipping straight to reassurance, don't worry, it will look great when it's done, tends to backfire, because it asks for trust without giving the client anything to hang that trust on. Naming the stage first gives them a landmark. This is the joinery stage, before sanding and finish is a sentence a client can actually hold onto for the rest of the walkthrough.
I have watched this play out with instructors who teach this instinct explicitly, framing every checkpoint around what a client can see rather than what the maker already understands intuitively. A community built around exactly that kind of process narration is Art of the Craft, where makers walk through visible stages of handwork in a way that treats the in-progress look as worth explaining rather than something to apologize for or rush past. That reframing, from apology to explanation, is the entire trick.
Where the usual advice falls short
Standard client-communication advice says to keep progress updates brief and positive, on the theory that clients want reassurance, not detail. That guidance works for a status update sent by text. It works badly the moment a client is standing in front of the actual unfinished object, because a short positive line cannot compete with what their eyes are already telling them. A client looking at bare wood and hearing everything's on track will trust their eyes over the sentence, and reasonably so.
What works better in person is the opposite of brief: enough specific detail that the gap between what they see and what they expected gets closed by information rather than by a general assurance. This is not the same as over-explaining every technical step, a habit covered from the coaching side in how a good coach cues a rep without overexplaining. The difference is target. A coaching cue during a rep should be short because the athlete needs to keep moving. A client review of unfinished work should be specific because the client needs to keep trusting, and trust needs more than a headline to rebuild once the visual mismatch has already triggered doubt.
| What the client sees | What they assume | What to say instead |
|---|---|---|
| Raw, unsanded surface | The finish was forgotten or rushed | Sanding happens last, after joints are checked under full light |
| Visible clamps or basting stitches | Something is being held together improperly | This is temporary, it comes off once the glue cures and the fit is confirmed |
| Mismatched or dull color | The final piece will look like this | Color evens out after the final coat, this stage is about structure, not tone |
Building the habit before the meeting starts
The chair-building example resolved the same way this always resolves, with three prepared sentences said before the client had a chance to react on their own. Stage, next step, reason for the current look, in that order, delivered in the first thirty seconds of the walkthrough rather than as damage control after a worried question. Preparing those sentences takes less time than most people assume, usually under five minutes, and it prevents a much longer conversation spent walking back an assumption the client should never have had to form.
This is really the same discipline behind any brief that gets read correctly the first time, discussed more broadly in how to brief a team without writing a novel. Say the thing the audience most needs before they have to ask for it, and most of the anxious follow-up questions never get asked in the first place. The wider category of client and team communication this sits inside is covered further in workplace communication, where the same pattern shows up again and again in settings that have nothing to do with sawdust or thread.
Before the next client checkpoint on any visibly unfinished piece, write the three sentences first, on a card if needed, and say them before the client has a chance to react to the raw materials alone. It feels unnecessary when the work is going well. It is exactly the habit that keeps a normal stage of production from being mistaken for a problem that was never actually there.
More in Workplace Communication
Workplace Communication
How to Announce a Change to Your Team Without Pushback
You need to announce a change to your team, and you already know how it will land: a few people will go quiet, one will push...
Workplace Communication
How to Write a Project Handoff Note Nobody Has to Chase
You are leaving a project for two weeks, or for good, and the person taking over will spend their first three days messaging...
Workplace Communication
How to Write Meeting Notes Your Team Will Actually Read
You spend an hour in a meeting, someone sends round three pages of notes, and two weeks later nobody can say who agreed to...