Stop Reviewing Results. Start Reviewing Behaviour.

Traditional sales reviews create fear, and fear creates hidden problems and inflated numbers. Reviewing behaviour instead of results changes the questions — and the answers you get.

Most sales reviews follow a predictable shape. The manager reads out a number. The number is below target. The manager asks why. The caller offers a reason. The manager either accepts it wearily or rejects it sharply. Everyone leaves feeling slightly worse.

Run that daily and you do not get a high-performance team. You get a team that has learned to manage the review rather than the work.

What a results-only review teaches people

Every recurring meeting trains behaviour, whether or not that was the intention. A review focused purely on results teaches three lessons, and none of them is the one you wanted.

Hide problems. If admitting a difficulty produces criticism, difficulties stop being admitted. The caller who is struggling with a specific objection will not raise it — so it never gets solved, and it goes on costing you deals silently for months.

Protect the number. When only outcomes are examined, people optimise the outcome directly. Leads get marked "not interested" so they leave the list. Calls get logged that were barely calls. Nothing dramatic — just a slow drift towards numbers that look better than the reality behind them.

Perform, don't improve. The energy goes into having a good answer ready, not into working out what actually went wrong yesterday.

If your review makes people defensive, you are no longer receiving accurate information about your own business. You are receiving a presentation.

The same meeting, run on behaviour

Now hold the review with yesterday's activity data in front of both people. The questions change completely — not because the manager has become gentler, but because there is something specific to talk about.

Read those again and notice what they share. Every one of them is about something the caller can change tomorrow morning. None of them is about a number that has already been produced and cannot be altered.

Why this is not softness

It would be easy to read the above as a gentler, lower-standards approach. It is the opposite, and it is worth being clear about why.

A results-only review is actually the easy option for a manager. It requires no preparation and no knowledge of the work. You read a number and express disappointment. Anyone can do it.

A behaviour review demands that the manager knows what happened yesterday, in detail, before walking in. It demands specific feedback tied to specific evidence. It sets a clearer standard, not a lower one — "make 60 quality calls a day" is far harder to dodge than "hit your target", because it is checkable tomorrow.

It is not micromanaging. It is setting up micro-processes — small, defined, repeatable behaviours that add up to a system which eventually runs itself.

That distinction is worth defending when someone raises it, and someone will. Micromanagement is watching a person constantly because you do not trust them. Micro-process is agreeing on what good work looks like at the level of daily activity, measuring it automatically, and then leaving people alone to do it.

The second one actually requires less supervision, not more — because once the process is defined and visible, the caller can self-correct without waiting for a manager to tell them.

A practical shape for the daily review

Fifteen minutes. Same time every day. Data on screen, visible to both people.

1. Yesterday's inputs — dials, talk time, callbacks completed. Read them out, no commentary.
2. One thing that went well — name it specifically. "Your afternoon call with the Kochi lead ran nine minutes."
3. One thing to change — one, not five. The largest gap.
4. What support is needed — asked as a genuine question, and answered.
5. Today's input target — an activity number, not a revenue number.

Notice what is missing: any discussion of the monthly target. That number is a consequence. It does not need managing, because it is not a thing anyone can do — it is a thing that happens when the inputs are right for long enough.

The test

Ask your team, privately, whether they look forward to the daily review or dread it.

If they dread it, the review is costing you more than it produces — in hidden problems, in inflated numbers, and eventually in the people who leave because of it.

The fix is not to stop reviewing. It is to review the things people can still change.