Coaching and feedback systems that actually compound

A coaching and feedback system is not a review cycle. It is a cadence that keeps evidence fresh and turns it into small, frequent adjustments: weekly in the 1-1, monthly across the team, quarterly at calibration. The review cycle is the one visible artefact of that cadence, not the system itself. Companies that treat the cycle as the system get exactly what the cycle can produce on its own, which is a rating, a letter, and six weeks later nobody able to name a single thing that changed. Companies that run the cadence get a team that adjusts continuously and a calibration that is a formality because the evidence already agrees.

Watch the loop most teams are stuck in. Review season arrives. Reports write self-assessments under duress. Managers spend a weekend writing reviews that say roughly what they would have said three months earlier. The calibration meeting argues about ratings. Letters go out. Nothing moves. The problem is not effort or intent. Everyone in that loop is working hard. The problem is that the whole system fires once a quarter, and by then the specific moments that mattered have decayed into a general feeling.

What makes a coaching and feedback system compound

Compounding needs three things the annual cycle structurally cannot give you: frequency, fresh evidence, and small commitments that carry into the next loop. Frequency, because a signal you act on within days changes behaviour, and a signal you act on in three months changes a rating. Fresh evidence, because feedback has a half-life measured in days, not quarters. Small commitments, because the point of a coaching conversation is not the verdict, it is the one thing both sides do differently before you meet again.

A working system runs three cadences at once, each doing a different job:

The mistake almost everyone makes is to invest in the bottom row and ignore the top one. Calibration is the easiest cadence to get right and the least useful in isolation. Without the weekly and monthly cadences feeding it, calibration is a room full of managers defending narratives they wrote the night before. With them, it takes twenty minutes, because the evidence has been visible for a quarter and there is very little left to argue about. The compounding happens in the top row. The bottom row just reads the result.

The weekly 1-1 is where the system actually lives

Most of the real feedback in a good system never appears in a review document. It happens in the 1-1, in the week the thing happened, while both people still remember the detail. So the 1-1 is the load-bearing cadence, and getting it right is most of the work.

The shape is light. Both sides bring two or three pieces of recent evidence: a shipped artefact, a decision made, a customer interaction, a moment of friction. Then the manager does three things with each piece, in the same order every week.

Three moves, same template every week. That repetition is the point, not a limitation. When the structure is fixed, both sides prepare the same way, the conversation gets faster, and the commitments start stacking. Eight weeks of this shifts a team further than any review cycle, because eight weeks is eight commitments carried forward, each one building on the last. A quarterly review is one commitment, made once, about work nobody remembers clearly.

Evidence-led beats impression-led, every time

The single biggest quality lever in a 1-1 is where the conversation starts. Start from evidence and you get specific, actionable feedback. Start from feeling and you get a conversation about vibes that neither side can act on. The difference is not a matter of style. It changes what the meeting can produce.

Evidence-led sounds heavier than impression-led. In practice it is lighter, because the preparation is trivial once it is habit. Both sides note two or three things during the week as they happen, and arrive with them. No weekend spent reconstructing a quarter. The stronger the evidence, the shorter the conversation, because you are not spending twenty minutes trying to work out what you are actually talking about.

Where AI belongs, and where it must not

There are three honest places for AI in a coaching system, and all of them sit upstream of the conversation. None of them is delivering the feedback.

The first is capturing evidence. AI drafts, summaries and transcripts mean the manager spends the meeting on judgement rather than note-taking. The 1-1 notes write themselves, the manager reads, edits and signs, and the time that used to go into paperwork goes back into thinking about the person. The second is pattern detection. Across a whole team or a quarter, a model surfaces themes a single manager cannot see: the same kind of slippage in three different reports, a thread in stakeholder feedback that no one person clocked. The output is a prompt to investigate, never a verdict. The third is practice. Managers still building the craft of feedback need reps, and a model can generate realistic scenarios from the team's own work patterns: the report who is over-committing, the senior engineer drifting from the role, the pair stuck in a disagreement. Rehearsing the hard conversation before having it raises the quality of the real one.

What AI must not do is generate the feedback itself. The moment a manager is rubber-stamping a model's verdict, the relationship has changed, and the person on the other side knows. Run every proposed use through one filter before you wire it in.

That filter is not anti-AI. I run my own operation on the same tools, and I would not give up the evidence capture or the pattern detection. It draws the line at the one thing that has to stay human: the judgement, delivered by the person who owns the relationship. Everything around that moment is fair game. The moment itself is not.

The failure modes nobody warns you about

Three ways these systems die, all of them quiet, all of them common enough to plan for.

The first is starting at the wrong end. Teams build the calibration process first, because it is the visible one with the ratings attached, and never get the 1-1 right underneath it. Then calibration has nothing to stand on and reverts to narrative. The second is single-point dependency. A coaching system that lives entirely in one exceptional manager's head compounds beautifully until that manager moves teams, and then it goes with them. If the cadence is not written down and running the same way across the function, it is a personality, not a system. The third is the one that comes with AI, and it is the one I watch for hardest.

Each of these fails silently. Nobody sends an email saying the coaching system has decayed. It just stops producing change, the 1-1s drift back to mood check-ins, and a quarter later you are back in the review-season loop wondering why nothing moved. The way you catch it early is by watching the interpretation part of the 1-1: in a healthy system it gets shorter over time, because both sides start reading the same evidence the same way. When it starts getting longer and vaguer again, the cadence is slipping.

The smallest version that works

If your team has nothing structured today, do not build the whole three-cadence system. Build one thing: the 1-1 template. Three sections, same order every week.

• Evidence. The two or three concrete things that happened this week, on each side.
• Interpretation. What they mean, offered as a read the other side can correct.
• Commitment. The one thing each of you does differently before next week.

Run it for eight weeks and add nothing else. No monthly retro yet, no calibration redesign, no tooling. Most feedback systems fail because they start with the calibration meeting instead of the 1-1, and the calibration has nowhere to stand. Get the 1-1 right first and the rest of the system has a foundation. When the interpretation section starts shrinking on its own, that is your signal the base is holding, and you can add the monthly retro on top. If you would rather have one process mapped and rebuilt properly before you scale it across the function, that is exactly the shape of a Grain Audit: one workflow, end to end, with a plan you keep.

This is craft, and craft is a leadership discipline, not an HR process. The wider case for treating coaching this way sits in the operating leadership pillar, which is where feedback belongs: a thing managers own, not a thing the People team runs on their behalf.

Why this decides whether AI capability sticks

Here is the connection most People teams miss. Coaching and feedback are the two systems that decide whether AI capability actually spreads across a function, or stays locked in the two or three people who taught themselves. A team running weekly evidence-led 1-1s will surface AI experiments, share the patterns, and standardise the good ones without needing a separate programme, because AI craft shows up as evidence alongside every other craft. A team without that cadence gets isolated power users and no compounding, which is the same failure the four dysfunction patterns describe: the builders left, the capability went with them.

The tell is in the 1-1 itself. If AI use never appears as evidence, a draft it sped up, a pattern it caught, a scenario it helped a manager rehearse, then AI is not part of the system yet. It is still a side project someone does after hours. Once it shows up as evidence like anything else, standardisation has already started, quietly, without a launch.

This is why the work on designing the AI-native People team and the AI enablement operating model both rest on a working coaching system underneath. It is the same reason the champion model spreads capability rather than concentrating it, and the same discipline that keeps production agents for People Ops owned by the team rather than by whoever built them. You do not need a separate AI-skills track. You need the coaching cadence to be good enough that AI craft develops inside it, like everything else a manager coaches.