The Performance Conversation Playbook Ambiguity is the cruelty. Say it early. Say it small.
The day you bring in a first person, you inherit a job you have never done. This guide shows how to give feedback that is specific, timely and short, so hard conversations are rarely needed.
You will avoid it. They want it anyway.
It is a small operation, the relationship is personal, and raising something critical feels out of proportion. So it waits. The observation from week three becomes a pattern by month two and a serious conversation by month five. Meanwhile they are not asking for harshness. They are asking where they stand. Someone told nothing builds their own explanation, and it is usually worse than the truth.
None of them is "give feedback".
People guess where they stand, and guess badly in both directions. Withholding feels like kindness. It is comfort, and they pay for it in uncertainty.
Said on the day, it is a small observation. Said months later, it is a judgment about a pattern. The content did not change. The cost multiplied because of the delay.
Everything you know about how this should be done lives in your head. Each specific piece of feedback moves a standard into theirs. That is how one person's judgment scales.
People improve at things they know need improving. A weakness nobody has named does not get fixed, because nobody knows it is there.
Most problems at this size are alignment, not capability. Raised in month one, nearly all of it is recoverable. Raised in month six, almost none.
Anyone strong notices what is tolerated. An unaddressed problem quietly lowers what everyone else believes is expected.
Timing and specificity, not courage.
Not a review system. A set of habits for telling someone the truth about their work: decide the structure first, be specific in the room, and make sure it leads somewhere.
Five parts, in order.
Six mechanisms, each a specific thing that fails without them, and the honest limit: these are not goal conversations, and the two must stay separate.
Four separate conversations, a cadence, what good looks like written down, where the feedback comes from, why you likely do not need ratings, and the boundary with goals.
Be specific, separate what you saw from what you concluded, recognise good work, ask before you tell, write it down, and open the channel in the other direction.
One thing at a time, follow up, disagreement as information, being clear when it is not working, money on its own schedule, and consistent standards.
Set it up, the conversation, and making it lead somewhere. Each line is a box you either can or cannot tick.
Nine ways a practice people want becomes one they dread. All of them are failures of timing and specificity, not of empathy.
Pick one recent, specific observation. Say what you saw, then what you took from it, then ask whether you got it right. Thirty seconds. No formality.
A short regular conversation, weekly or fortnightly. The slot is what prevents the drift from week three to month five, because feedback no longer depends on you deciding to start one when you are tired.
Not a job description. A short statement of what they produce and how they work, specific enough that either of you can point at it. Check they agree it is fair.
- You have a first contractor or hire, or you are about to, and you have never given feedback from this side.
- You want a habit, not a review system.
- You are willing to say small things early, even when it feels out of proportion.
- You want your standards to hold when you are not in the room.
- You want a rating scale or a performance form. The guide says you almost certainly do not need ratings at this size.
- You want to fold feedback, development, pay and goals into one tidy meeting. The guide says never.
- You want a script for dismissing someone.
- You expect hard conversations to disappear. The aim is to need them rarely.
Nobody should be surprised by where they stand with you.
You have been on the wrong end of this for fifteen years. You can name every conversation that was handled badly. If they are ever surprised, the failure happened months earlier, in every conversation you decided not to have.
Luis Gonçalves
Twenty years in digital product development. Led the agile transformation at Nokia. Teaches at Porto Business School. Has spent the last decade working with founders across Saudi Arabia, Portugal, Brazil, and the broader emerging-market startup ecosystem.
He calls himself the Dark Entrepreneur because he believes the founder world is allergic to honesty. No success theater. No highlight reels. Just the real work that has to happen.