Coaching conversations that replace the annual review

Key takeaways

• A good coaching conversation is regular, forward-looking, and made up of more questions than answers. It isn't a status update and it isn't a lecture.
• A simple, repeatable structure removes the biggest barrier to managers doing this consistently: not knowing what to say.
• Frequent, prompted conversations beat a once-a-year sit-down because they catch problems while they're still small and feedback stays close to the moment it applies to.
• You don't need every conversation to be deep. You need most of them to happen.
• The manager's job in these conversations is to ask better questions, not to have all the answers.

I sat in on a manager's first attempt at a coaching conversation once. He opened with, "So, how's it going?" His employee said "fine," and that was the whole conversation. Ninety seconds, then back to email.

It wasn't that he didn't care. He genuinely did. He just had no idea what a coaching conversation was actually meant to look like, so he defaulted to small talk. Here's what a good one looks like instead, and a structure that makes it repeatable.

What a good coaching conversation actually looks like

A coaching conversation is not a status update. "What did you get done this week" is a project check-in, useful in its place, but it won't replace what an annual review was meant to do.

A good coaching conversation has three qualities.

It's regular. Not an occasional deep chat when something goes wrong, but a rhythm the person can count on. Regularity is what makes it safe to raise something small before it becomes something big, because the person knows there'll be another conversation soon either way.

It's forward-looking. The point isn't to relitigate what already happened. It's to work out what to do next. Past events matter as evidence, not as the main event.

It has more questions than answers. This is where managers get it wrong most often, because telling someone the answer feels efficient. It's efficient in the moment and useless over time, because the person never builds the muscle to work it out themselves. Asking "what do you think is driving that" instead of "here's what you should do" is the slower, better version of the job.

Get those three right and the rest is just showing up consistently.

A simple structure managers can actually use

The manager I mentioned earlier didn't need more good intentions. He needed a script he could rely on. Here's one that works for most regular check-ins.

1. Open with something real, not small talk. "What's been the highlight and the low point of the last couple of weeks" gets you further than "how's it going", because it asks for something specific.

2. Ask about progress against what matters, not everything. Pick the one or two things that are actually the priority, and ask honestly how they're tracking. Not a status report, a genuine check on whether the person feels on track and why.

3. Ask what's getting in the way. Often the most useful question in the conversation, and the one most likely to get skipped. What's slowing them down, what are they avoiding, what do they need that they don't have?

4. Ask, don't tell, when they raise a problem. "What have you tried" and "what do you think would help", before you offer your own view. Offer it after they've had a real go at their own answer, not instead of it.

5. Agree on one or two things before you end. Not a long list. One or two concrete things, who owns each, and when you'll next talk about how it went. That's what makes the next conversation easy to open.

That's it. Fifteen to twenty minutes, most weeks, is enough to run this properly. It doesn't need to be longer to be good.

Why prompted, frequent conversations beat a once-a-year sit-down

The annual review had one structural flaw that no amount of good writing could fix: it happened once, long after most of what it was discussing.

Frequent conversations solve that in a way an annual review structurally can't.

• Feedback stays close to the moment. Something that happened last week is still specific and actionable. Something from eight months ago is a vague impression by the time anyone discusses it.
• Small problems get caught small. A person quietly disengaging, or a goal that's drifted from what matters, shows up in week three of a regular rhythm. In an annual system, it shows up in the exit interview.
• Nothing needs to wait for the "right moment". Once a conversation is scheduled and expected, it comes up naturally, in a low-stakes setting, instead of building until it needs a formal one.
• The relationship carries more trust. A manager and employee who talk regularly and honestly, without a rating attached, trust each other more than two people whose main interaction is a once-a-year assessment.

"Prompted" matters as much as "frequent". Left to memory, even well-intentioned managers let these conversations slip when things get busy, exactly when they're needed most. A simple, regular nudge is what turns a good intention into something that actually happens most weeks, the difference between a system and a New Year's resolution.

This is the rhythm we've built into Whyser Work's performance module: a light structure for these conversations, a prompt so they don't quietly disappear under a busy week, and a record of what was agreed, so nothing depends on anyone's memory come review time. For the fuller picture of how this replaces the annual cycle altogether, see continuous performance: beyond the annual review. If you're due to run a more formal check-in, 360 feedback done well covers how to make that count too.

What tends to go wrong

A few things reliably derail this, worth watching for.

Letting it become a status meeting. If every conversation is "what did you finish," you've quietly turned coaching into project management. Keep at least one question genuinely about the person, not just the task list.

Filling every silence. The instinct to jump in when someone pauses is strong. Some of the most useful moments come right after a pause, when someone's actually thinking rather than reciting a rehearsed answer.

Skipping it when things are calm. It's tempting to let the conversation slide when nothing's obviously wrong. That's usually a mistake. The conversations that happen when things are fine build the trust that makes the harder ones, when they come, easier.

Frequently asked questions

How long should a regular coaching conversation take?

Fifteen to twenty minutes is usually enough for a weekly or fortnightly check-in, provided the manager comes with a simple structure rather than starting from a blank page. Longer, less frequent conversations tend to happen less reliably, which defeats the purpose.

What if the employee doesn't have anything to raise?

That's normal, and it doesn't mean skip the conversation. Ask about what's coming up, not just what's already happened, and ask what would make the next few weeks easier. A quiet week is still worth fifteen minutes of genuine attention.

Should these conversations replace formal performance discussions entirely?

Not necessarily, but they should carry most of the weight. A lighter, less frequent formal moment can still exist for decisions like pay, built on a year of real, regular conversations rather than a manager's memory from November. What they should replace is treating the annual moment as the only place performance gets discussed.

What if a manager isn't naturally good at asking questions instead of giving answers?

Almost nobody starts out naturally good at this. It's a skill built through practice, and a simple structure to lean on makes the biggest difference early on. Managers who stick with it usually find it gets easier within a few conversations, once the habit of pausing before answering starts to take hold.

If your team could only remember your last conversation about how they're going, would it be one that happened this month, or one they had to wait a year for?