Calibrated Praise: A Manager’s Guide to Feedback That Carries Weight

Few managers arrive at work intending to offer hollow praise or to remain silent when standards slip. Yet feedback is often the task that gets postponed in favour of delivery. In many UK workplaces, politeness is prized, directness can feel risky, and the result is a familiar pattern: good work goes unremarked while weak work is tolerated until it becomes a performance issue. The answer is not to become more effusive or more severe. It is to become more precise.

The cost of avoiding the awkward

When praise is vague, employees cannot tell what to repeat. When correction is absent, they cannot tell what to change. A comment such as 'good job' may be kindly meant, but it gives the recipient little to work with. At the other extreme, a general remark that standards need to improve can feel like a verdict without a route forward. Over time, both patterns erode trust. People begin to suspect that feedback is political, inconsistent or reserved for favourites.

Calibrated feedback avoids both traps. It treats recognition and correction as two forms of the same managerial task: helping someone understand the effect of their work and what to do next. At Achievers Coaching, we find that managers who adopt this view tend to sound less like judges and more like coaches. They are neither stingy with credit nor reluctant to name a gap.

Four tests of feedback that carries weight

Before speaking, a manager can apply four simple tests. They take less than a minute and prevent most cringe.

First, be specific. Name the action, the context and the effect. 'You handled that well' is pleasant but forgettable. 'You flagged the supplier delay in Thursday’s update, which allowed the team to resequence the launch' tells the person what to repeat.

Second, be timely. Feedback loses force when it arrives weeks later in an appraisal. A short comment close to the event is more useful than a polished speech months afterwards. This does not mean reacting instantly to every issue. It means not saving routine observations for a formal occasion where they will feel like ambush.

Third, be proportionate. Strong praise for a minor task can sound patronising; heavy criticism for a small slip can sound threatening. Match the weight of the words to the weight of the behaviour. Save the strongest recognition for work that genuinely changed an outcome.

Fourth, focus on behaviour rather than character. 'You are brilliant' is a label. 'Your summary gave the client a clear choice between two options' is evidence. Likewise, 'you are careless' invites defensiveness, while 'the figures were sent without the checking step we agreed' describes a behaviour that can be changed.

Scripts for everyday settings

Managers often know the principles but freeze when the moment arrives. A few reliable sentence structures help.

In one-to-ones

For recognition: 'In Tuesday’s client review, you summarised the three risks before the discussion moved on. That gave the team a clear basis for the decision. Please keep doing that in future reviews.'

For correction: 'In the same review, the cost estimate was presented without the caveat we agreed. The client therefore left with a different expectation. Next time, please state the assumption before the figure.'

Notice that neither script relies on flattery or blame. Each names an observable action, its effect and a future expectation.

In project debriefs

A debrief can easily become either a victory lap or a post-mortem. Keep it balanced by asking three questions: what worked, what would you repeat, and what would you change? The manager’s contribution should be evidence, not mood. For example: 'The daily stand-up was shorter than the previous project, and the blockers surfaced earlier. That was a useful change. The handover to operations was less clear, and two actions were duplicated. Let us agree a single owner next time.'

In team meetings

Public praise should be brief, earned and connected to the work. Avoid turning recognition into a performance. A useful line is: 'I want to note one thing the support team did well this week. They logged the recurring issue and gave us the pattern, not just the individual tickets. That changed how we prioritised the fix.' This recognises achievement without flattery and gives others a model to follow.

Correcting underperformance without draining morale

Correction is hardest when a manager fears damaging the relationship. Three habits help. First, speak privately unless the issue is already public and requires immediate action. Public correction rarely improves performance; it usually improves compliance in the room and resentment afterwards.

Second, separate intent from impact. Most people do not set out to underperform. A manager can say: 'I do not think you intended to leave the client without an answer, but that was the effect.' This lowers defensiveness while keeping responsibility clear.

Third, agree one observable change and a review point. 'For the next two reports, please send me the draft by Wednesday noon so I can check the figures before it goes out. We will review how that works on Friday.' Specific follow-up turns a difficult conversation into a workable plan.

A short weekly discipline

Feedback improves when it is not left to memory. Once a week, note three observations for each team member: one strength, one gap and one question. The note need not be formal. Its purpose is to ensure that recognition is not reserved for the loudest successes and that small problems are addressed before they become large ones.

Praise need not be theatrical. Correction need not be harsh. The manager’s task is calibration: saying enough, at the right moment, with enough evidence that the message can be understood and used. That is feedback that lands.