What Good Coaching Feedback Actually Looks Like

After a game, most coaches give feedback that sounds something like this: "You need to be more aggressive in the tackle." Or "Your decision-making wasn't great today." Or the classic: "You weren't at the races in the second half."

None of these are wrong, exactly. But none of them are useful, either. By Tuesday, the player has filed them away alongside every other vague thing they've been told since they were 14, and nothing changes.

Why vague feedback doesn't work

The problem with vague feedback isn't that it's too harsh or too soft — it's that it doesn't give the player anything to act on.

"Be more aggressive" lands differently for every player on your squad. The 19-year-old who's still finding his feet hears it as a character critique. The experienced player who's been around forever nods along and wonders what you actually want from him next week. Neither of them knows what to do differently on Saturday.

The other thing that happens with vague feedback: players push back. Not always out loud, but internally. "You weren't aggressive enough" is an opinion. Players know it's an opinion. And the ones who disagree — or who felt they did give everything — quietly dismiss it and move on.

The structure that actually sticks

The feedback that changes behaviour follows a simple structure:
Specific → Contextual → Forward-looking.

That's the same message — tackle technique needs to improve — but now the player knows exactly what happened, when it happened, and what to do differently. That's something they can actually work on.

Here's what each part is doing:

• Specific— A real moment, not a generalisation. "62 minutes, two tackles in a row." Not "a few times today."
• Contextual— Why it matters. "The ball carrier was able to offload." "We've seen this a few times this season." Connect the action to the outcome.
• Forward-looking— Something to do differently. "Get your hips lower before contact." One clear change, not a list.

A lineout example

Let's say you want to give feedback to your hooker on lineout throwing. The vague version: "Your lineout throwing wasn't consistent today."

The structured version: "We lost the throw at 34 minutes and 71 minutes — both were off the back of the lineout, both went slightly short. That cost us field position both times. This week at training, let's spend 10 minutes on your back-of-the-line throws specifically. I want to see you release slightly higher on those."

Same message. Completely different impact.

How data changes the conversation

One reason coaches default to vague feedback is that they don't have the numbers in front of them. When you're working from memory two days after the game, "you weren't aggressive enough" is about all you can offer.

When you have actual data — tackle percentage, missed tackle count, involvement numbers — the conversation changes. You're not telling a player how it felt. You're showing them what happened. "You made 4 tackles and missed 2 — that's a 67% success rate. Your season average is 84%. Two of the misses were in the second half, both in open play."

Players push back less on numbers than they do on opinions. Not because numbers are always right, but because they give the conversation a concrete starting point. You can have a real discussion about what happened instead of arguing about whether the coach's perception matches the player's.

One thing to change this week

Before your next debrief, pick two players. For each one, find one specific moment from the game — something you actually remember, or can find quickly on the video. Then structure your feedback:

• Specific: what happened, when
• Contextual: why it mattered
• Forward-looking: one thing to do differently

That's it. Two players. One specific moment each. You don't have to overhaul your whole debrief process in one week. Just try the structure with two players and see whether it lands differently.

The coaches who do this consistently — who show up with specific, evidenced feedback instead of general impressions — are the ones players actually remember. Not because they were the loudest or the most experienced, but because they made the player feel seen.