The second time it happened you told yourself it was a bad week.
The fourth time you started routing the work around them instead, giving the important jobs to someone else and telling yourself you were being fair by not making a fuss.
By the time you finally sit down and say something, you're not raising an issue any more. You're delivering a verdict, built out of six months of things you never mentioned, and the person on the other side of the desk is hearing all of it for the first time.
They'll be shocked, then they'll be angry, and they'll be entitled to both, because as far as they knew everything was fine...
Most building company owners think the alternative to a hard conversation is a neutral one. It isn't. The alternative is a message, and the message is worse than the one you were avoiding.
When you say nothing about work that isn't good enough, the person doesn't hear nothing. They hear that it was acceptable. Do that a few times and you haven't protected anyone's feelings, you've moved the company's standard down to whatever you last tolerated in silence.
Watering down feedback creates confusion, lowers standards, and produces a team that stops improving. Sugar-coating looks like the considerate option and behaves like the opposite, because it trades a short uncomfortable conversation for a long slow decline that everyone can see and nobody names.
There's a second cost that you underestimate. A team watching you avoid a conversation learns what you'll tolerate. If the person who cuts corners is never pulled up, the people doing it properly work out that doing it properly is optional, and the good ones start looking around. That's how retaining good staff turns into a problem that looks like a market problem and isn't.
Being direct isn't the same as being harsh, and the two get confused often enough that plenty of business owners pick avoidance rather than risk it.
Criticism describes what's wrong. Candour describes what's missing and what's possible. Criticism is reactive and tends to drift onto the person. Candour is specific, is about the work, and takes it as given that the person can fix it.
Put them side by side. Criticism sounds like: "another invoice has been approved without being checked against the budget, it's careless and sloppy and it shows me you've got no attention to detail." Candour sounds like: "I noticed you approved that invoice without checking it against the budget. It's the second time, and it isn't acceptable. Can you walk me through your process and how it happened?"
The second one is harder to argue with, because there's nothing in it to argue with. It states an observed fact, it states the standard, and then it hands the floor over. It's also the only one of the two that can produce information, and the reason it happened twice is information you need.
The rule underneath the wording is that you go after the result, never the person. The results aren't acceptable is a statement someone can act on. You're careless is a statement someone can only defend against.
Kim Scott's Radical Candour gives the cleanest frame for this. Effective leadership sits on two dimensions at once: care personally, and challenge directly.
Challenge without care and you're just difficult to work for. People comply, they don't improve, and they tell you nothing they don't have to.
Care without challenge and you're a pushover. Well liked, and presiding over a standard that slips a little every quarter without anybody deciding to lower it.
Do neither and you're irrelevant, which raises a fair question about what you're doing in the company at all.
Both together sounds like this: "I know you've got a lot on at the moment and I do value the effort you've been putting in. That said, the last two client update reports were rushed, missing key information, and not to our standard. We need to get back on track. Can we sit down tomorrow and go through a better process together?"
Care, challenge, and a next step, in about twenty seconds. Nothing in it is soft and nothing in it is personal.
Feedback given close to the event is a correction. The same feedback six months later is an ambush.
Feedback belongs in the same day or the same week as the behaviour, positive or negative. Saving it for the six-monthly performance review is where most of the damage comes from. A performance review should confirm things the person already knows.
Here are two rules you can follow with regards to this conversation:
Praise in public. It costs nothing, it sets the standard visibly, and it's more useful when it's specific. "Thanks for taking the call with the engineer yourself, that saved us a full day" tells the whole team what good looks like. "Good job today" tells them nothing.
Correct in private. Embarrassing someone in front of the team doesn't build authority, it builds fear, and fear is expensive in a business that depends on people telling you about problems early.
There's one exception worth knowing, because the private rule gets over-applied. If a problem surfaces in a group setting, in a project debrief or a team meeting, deal with it in the room. Ask the clarifying questions there, and say so plainly if the answers don't stack up. Skipping past it in front of everyone and picking it up privately later teaches the team that you'll avoid anything awkward. Address it in the room, then go deeper privately afterwards.
Sometimes the honest answer is that you shouldn't be having it yet.
When your heart rate is up, your tone is sharpening and part of you wants to win, your judgement has already gone. You'll say the version you've been rehearsing in the ute rather than the version that works. It's the conversational equivalent of sending the email you were still drafting.
Run three questions before you open your mouth. They only work once you've cooled off.
What are the facts? Strip out the interpretation. Not what you felt or what you think they meant. "The report was three days late and no update was given" is a fact. "He doesn't respect deadlines" is not.
What meaning am I attaching, and is it true? You've almost certainly built a story already. That they're lazy, that they're taking liberties, that this is aimed at you. Ask whether the evidence actually supports it.
What else could this be? Overwhelmed and unwilling to admit it looks identical from the outside to doesn't care. So does out of their depth, and so does waiting on something from someone else.
Buying yourself the time is a sentence, not a strategy. "Let's take a break and come back to this once we've both had a chance to think" or "I want to respond to that properly rather than react to it" both work, and neither concedes anything.
You don't have to match their energy. Your job is to bring the temperature down, and you do it by being the steady one rather than the right one.
Acknowledge what you're seeing without judging it. "I can see this has really rattled you." Then stop talking. Don't defend, don't explain, don't start fixing. Let the silence sit long enough for them to keep going, because they usually will, and the second thing they say is normally the real one.
Then offer a calm next step rather than a resolution. "I want to sort this out properly. Let's take ten minutes and come back to it."
Underneath all of it is one shift: replace defensiveness with curiosity. Instead of how dare they say that, ask what's going on for them that made them say it. Then ask, out loud. What would a better outcome look like for you. What do you need from me to move forward. You don't have to agree with the answers. But people who feel heard stop shouting, and people who feel accused don't hear anything at all.
Someone who feels cornered will protect, deflect or attack, and none of those states involve listening. Restoring safety isn't softness, it's the precondition for the conversation you wanted to have. Say you value their input even when you disagree. Say you're not trying to pin it on them, you're trying to find a way forward. Then get back to the point.
Reduce the lag between noticing something and addressing it.
You usually know. You feel the tension, you see the mistake, you sense the resentment, and you decide to see whether it settles down on its own. It rarely does, and every week you wait adds weight to a conversation that was light when you first noticed it.
Raise it while it's still small enough to be a comment rather than a confrontation. A thirty second exchange in the first week does the work of an hour-long meeting in the sixth month, and nobody has to be shocked.
Most of what builders call a people problem is a stack of conversations that were never had. If you're carrying two or three of those right now, and you can already name them, book a 15-minute chat with our team and we'll work through how to open them without blowing up the relationship.