How to Have a Performance Conversation:Keep It Small

How to have a performance conversation: one specific moment, what you saw, what you concluded, then ask. Short, written down, followed up. Do it this week.

CATEGORYGrowth
READ TIME7 min
PUBLISHEDOct 27, 2026
AUTHORLuis Goncalves
How to Have a Performance Conversation: Keep It Small

To have a performance conversation, pick one recent, specific moment, say what you saw, say what you took from it, then ask whether you got it right. Keep it short, write down what you agreed, and follow up. Do it this week, not at some future review.

How to have a performance conversation without it becoming an event

You've sat on the wrong side of this for fifteen years. The vague review. The surprise. The feedback that landed months after it would have helped.

Now you have a first contractor, a freelancer, maybe a first proper hire. And you're about to repeat all of it, because nobody ever showed you another way.

Here's the way. A performance conversation is not a meeting you schedule once a year and dread for a month. It's thirty seconds of honesty about one thing, said while you both still remember it. That's the whole idea. Everything else is detail.

Most advice makes this sound like a delicate negotiation. It isn't. It's a habit. The hard version only exists because the easy version was skipped.

Before you open your mouth

Preparation is two minutes, not two hours. You need three things.

One specific observation. Not "your updates are weak". A moment. Something you both saw. If you can't point at a moment, you don't have feedback yet. You have a mood.

A recent example. Recent enough that you both remember it. Last Tuesday works. Last quarter does not. The longer you wait, the less it's an observation and the more it's a verdict.

Something that's going well. Specific, and real. Not a cushion to make the criticism go down. Information of exactly the same kind. People often don't know which part of their work you value most, so they optimise the wrong thing. Tell them.

Then separate two things in your head. What did you actually observe? And what did you conclude from it? The first is a fact. The second is a guess. You'll say both out loud, and you'll label them.

Free guide · 21 pagesAmbiguity is the cruelty.The Performance Conversation Playbook: how to tell someone the truth about their work.Get the free guide →

In the room: the order that works

Start with a question. "How do you think that went?" Don't skip it. Often they say the thing you were about to say, and it lands far better coming from them. Even when they don't, you learn what they think, which is the most important gap in the conversation.

Then give your observation. Behaviour, not character. "In the call on Tuesday, when the client asked about timelines, you gave three different answers in five minutes" is something you can discuss. "You're disorganised" is a verdict, and nobody can do anything with a verdict.

Then offer your interpretation as a hypothesis. "I think they left confused. Is that right?" Now they can add what you don't know. The client had been told something different. The deadline moved. You never passed on a piece of context. You're working alone most of the day, so your view is partial. Act like it.

Then listen. Properly. Before you restate your view, hear the context you lacked.

Here's the whole sequence in one place.

StepWhat you doWhat goes wrong if you skip it
Ask first"How do you think that went?"You tell them what they already knew, and miss the context you lack.
ObserveDescribe one moment, in behaviour you could film.They hear a judgement of who they are.
Interpret"Here is what I took from it. Is that right?"Your guess is delivered as a fact, and you are confidently wrong.
ListenHear their context before you restate anything.You argue with a version of events that never happened.
AgreeSettle what happens next, roughly when.Nothing changes, and they learn it was a ritual.
Write it downA few lines: discussed, agreed, next.You both remember different conversations.

Six steps. It sounds like a lot. Said out loud, it's a short conversation, and sometimes it's thirty seconds at a screen.

Say the good stuff, and mean it

If your only feedback is critical, you've trained them. Every time you ask for a chat, their stomach drops. Soon they stop bringing you problems, because bringing a problem means a chat.

Specific recognition fixes that. "The way you handled that refund was exactly right, and here's why" does two jobs. It tells them what to repeat. And it makes feedback ordinary, a normal part of working together rather than a siren.

Don't sandwich. The old trick of wrapping criticism in praise teaches people to flinch at praise. Give the good news on its own merits, when it's true, and give the hard news plainly when that's true.

What a performance conversation sounds like

Say you've hired a freelancer to run your customer replies. A reply went out on Wednesday that was warm but never answered the question. Here's the whole thing.

"How did you feel about Wednesday's reply to that customer?" They think it went fine. Fine. Now you know where they stand.

"Here's what I saw. The customer asked whether the refund would arrive this week, and the reply never said. Here's what I took from it: you weren't sure, so you went around it. Is that right?"

Maybe it is. Maybe they didn't know the refund policy, which is your gap, not theirs. Either answer is useful. Either way you leave with something to change.

"The tone was exactly right, by the way. Keep that." Then three lines in a note. Done.

That's an archetype, not a case study. But notice there's no drama in it. That's the point. Small and early looks like nothing happened.

Open the channel the other way

Ask what you should be doing differently. Then do the hard bit: respond well, at least once, where they can see it.

If you ask and then bristle, the channel closes for good. They learn the question was rhetorical. And you lose your only source. Nobody else will tell you how it feels to work for you. You run this alone, and nobody is going to volunteer it.

So when they say something you can act on, act on it. Visibly. Say "you told me the briefs arrive too late, so from Monday they arrive on Friday". That one move is worth more than a year of asking.

Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →

What to do straight after

Write it down. Three lines. What we discussed. What we agreed. What happens next. It isn't surveillance. It's memory. Without it, patterns stay invisible, and a conversation six months from now has no history to stand on.

It also protects them. If a hard decision ever comes, a written trail of feedback given and support offered is what makes it fair instead of a shock.

Then put a date on the follow-up. Not a big one. Just a moment where you ask, "has that got easier?" That's the part everybody skips, and it's the part that turns a chat into improvement. There's more on that in how to follow up on feedback.

What not to do on the day

  • Don't save things up. If you've been holding three observations for a "proper" conversation, you've already made it harder.
  • Don't mix in money. The moment pay appears, everything you said becomes justification for a number. Keep it separate. Feedback, development and pay are different conversations.
  • Don't bring up goals. What they hit or missed is a different document and a different rhythm. Say that out loud, early, and hold it the first time it would be convenient to break.
  • Don't dress up an interpretation as a fact. That's how feedback becomes an accusation. See observation versus interpretation.

That list is short because the failures are few. Nearly all of them come down to timing and specificity, not a lack of kindness. Both are habits. Habits are available this week.

Free guide · 21 pagesAmbiguity is the cruelty.The Performance Conversation Playbook: how to tell someone the truth about their work.Get the free guide →

Do you need a formal setting?

No. You're running a one-person operation with perhaps one other person in it. A formal review with a form and a rating adds bureaucracy and nothing else. You already know how it's going.

What you do need is a slot that exists, so you never have to decide to start a hard talk when you're tired. That decision is exactly the one that gets postponed. A fixed, short, regular slot removes it. If you haven't set one, start with how to set a one to one cadence.

And do this before the pressure arrives. The first conversation should not be about a problem. Have an ordinary one early, about something small, so that the second one, the hard one, has somewhere to land.

Free assessmentHow trapped are you, really?Take the Corporate Suffocation Index, the free solopreneur readiness assessment.Take the assessment →

Frequently asked questions

How long should a performance conversation take?

As short as the point allows. A small observation can take thirty seconds. A larger one rarely needs more than a short sit-down. If it needs an hour of preparation, you waited too long.

Should I start with the positive or the negative?

Start with a question about how they think it went. Then share what you saw, good or bad, on its own merits. Don't wrap criticism in praise as a softener. Praise is information, not packaging.

What if they disagree with me?

Treat it as information, not resistance. They were there for things you weren't. Listen to the substance first. If you still disagree afterwards, say so plainly and say what you'd need to see.

Do I need to write anything down?

Yes, a few lines each time: what was discussed, what was agreed, what happens next. It's memory, not surveillance, and it's what makes any later decision fair.

The full method for any performance conversation, with the checklists, is in The Performance Conversation Playbook, a free 21-page playbook.

How trapped are you, really?

Take the Corporate Suffocation Index, the free solopreneur readiness assessment.

Start the assessment →