Most performance conversations fail for the same reason: they are status updates dressed up as development. The manager asks how things are going, the employee says fine, and both leave having learned nothing.
This guide covers how to run the conversation properly — the structure, the questions, and what to do when it gets difficult.
What is a performance conversation?
A performance conversation is a structured discussion between a manager and an employee about progress, obstacles, feedback and development. Unlike an annual review, which looks backwards and assigns a rating, a performance conversation happens regularly — usually monthly — and is designed to change what happens next.
The three most common formats are the one-to-one (regular, forward-looking), the feedback conversation (specific, timely, behavioural) and the periodic review (structured, documented, covering a defined period).
Why regular beats annual
The annual review is a poor instrument for a simple reason: twelve months is too long to wait to hear that something is not working. By the time an annual review surfaces a problem, the employee has been doing it wrong for a year and has usually formed a view about whether they want to stay.
In frontline industries where turnover regularly exceeds 30%, the maths is worse. A meaningful proportion of your workforce will leave before they ever reach their first annual review. Monthly conversations catch disengagement while it is still recoverable.
This does not mean abandoning periodic reviews. It means the review becomes a summary of conversations that already happened, rather than the only conversation of the year. Our guide to performance management software covers how organisations structure both.
The one-to-one structure that works
Keep it simple enough that a stretched venue manager can run it in fifteen minutes without preparation.
1. What went well since we last spoke? Start with what is working. It sets the tone and it surfaces things worth recognising that you might otherwise miss.
2. What got in the way? This is the most valuable question in the conversation. It shifts the frame from performance to obstacles, which makes it safe to be honest. Most of what you learn about how your operation actually works will come from this question.
3. What feedback do you have for me? Asking this consistently is what separates managers people trust from managers people manage around. Expect nothing useful for the first few months. Keep asking.
4. What do you want to learn next? The development question. Without it, the conversation is operational. With it, the conversation is about a career.
Write down what was said. Not for compliance, but so the next conversation starts where this one finished. Conversations that build on each other are worth ten times conversations that restart from nothing.
Give every manager the same framework
Prosper provides one-to-one templates, saved notes and goal tracking so conversations build over time — and leadership can see they are actually happening.
Book a consultationHow to give feedback that lands
Feedback fails when it is vague, late or about the person rather than the behaviour.
Be specific about the behaviour. "You need to be more professional" is not feedback. "When you took that call in front of the customer, they overheard the whole conversation" is feedback, because it describes something observable.
Be timely. Feedback delivered three weeks later has almost no effect on behaviour. Deliver it within a day or two while both people remember the specifics.
Describe the impact. People change behaviour when they understand the consequence. "The customer looked uncomfortable and left without ordering" does more work than "it was unprofessional."
Agree what changes. End with something concrete. Feedback without an agreed next step is just criticism with better manners.
Setting goals people can actually use
Goals fail in frontline environments when they are copied from a corporate template. A bartender does not have quarterly OKRs. They have things they are working on.
Keep goals to three at a time. Make at least one about capability rather than output — something the person is learning, not just producing. Write them somewhere both people can see, and open the next one-to-one by reviewing them rather than by asking how things are going.
Review quarterly at minimum. A goal that has not been discussed in three months is not a goal, it is a note.
Difficult conversations
Most managers avoid difficult conversations until they become disciplinary ones. The gap between "I have noticed a problem" and "we are now in a formal process" is where the conversation should have happened.
Have it early. The conversation is easier at the first instance than the fifth, and the employee has a genuine chance to change.
Separate the behaviour from the person. "This has happened three times" is about a pattern. "You are unreliable" is about identity, and people defend identity.
Ask before you tell. There is frequently a reason you do not know about. Ask what is going on before you explain what needs to change.
Be clear about what happens next. Ambiguity at the end of a difficult conversation guarantees you will be having it again.
Document it. Not as a threat, but because if the pattern continues you will need a record of the support that was offered.
Common mistakes
Turning the one-to-one into a status update. If the conversation only covers what happened operationally, cancel it and read the report instead.
Cancelling when things get busy. The one-to-one is the first thing to go in a busy week, which means it disappears exactly when it is most needed.
Only talking to the people who need attention. Solid performers who never cause a problem often receive the least attention and are frequently the first to leave.
Saving feedback for the review. Nothing in a review should be a surprise. If it is, the manager has failed, not the employee.
No record between conversations. Without notes, every conversation starts from zero and the review becomes an exercise in what both people can remember.
Making it happen consistently
The difference between organisations where one-to-ones happen and organisations where they do not is rarely manager intent. It is whether there is a shared framework, whether notes are saved somewhere useful, and whether anyone can see the cadence is being kept.
For multi-site frontline operations, this is a visibility problem. A regional manager cannot know whether monthly conversations are happening across 30 venues without a system that shows it. Our article on performance management for frontline teams covers how organisations solve this at scale.
Frequently asked questions
A structured discussion between a manager and employee about progress, obstacles, feedback and development. Unlike an annual review it happens regularly — usually monthly — and is designed to change what happens next.
Monthly is the practical minimum for frontline teams. Weekly works well for new starters during their first 90 days. What matters more than frequency is that the cadence is kept consistently.
Four questions cover most of it: what went well, what got in the way, what feedback do you have for me, and what do you want to learn next. Keep the same questions each time so the conversation builds.
Be specific about the observable behaviour rather than the person, deliver it within a day or two, describe the impact it had, and agree a concrete next step.
A one-to-one is regular, informal and forward-looking. A performance review is periodic, documented and covers a defined period. When one-to-ones happen properly, nothing in the review is a surprise.
Have it early rather than letting the pattern build, separate the behaviour from the person, ask what is going on before explaining what needs to change, be explicit about what happens next, and document it.