“Good work today” can express appreciation, but it may leave a colleague unsure which part of the work you mean. “Please be more careful” has a similar problem: it communicates dissatisfaction without identifying what needs to change. A useful brief response names the work, the relevant expectation and the observation that supports what you are saying.

Brief feedback does not have to fit a stopwatch. It concerns a small, specific piece of work that can be discussed accurately. Sometimes a few sentences are enough to recognise it. Sometimes the first question reveals that you opened the wrong document, never explained the requirement or need more time to understand the situation. The owner must be willing to change the response when new information corrects their understanding.

1. Know what was expected before judging the result

Consider a wholly fictional administrative exercise. A colleague is preparing an agenda for an internal staff session about finding routine reference documents. It contains no patient information or clinical teaching. The agreed brief is to put the session date and a version label on the first page, save the draft in the agreed location and submit it to the manager for review before circulation. All work, dialogue and observations below are invented for this exercise, not accounts of a real practice.

This brief gives feedback a reference point. “Make a professional agenda” would leave more to guesswork. Date and version on the first page are things the manager can check. Approval before circulation is a separate condition: adding the labels does not establish that the contents have been reviewed or that the document is ready to send.

Before giving feedback, check the actual brief, the file you are viewing and the stage the work has reached. A working draft may contain unfinished parts that were meant to be discussed at review. Compare it with what was required at this stage rather than a finished standard you have introduced silently.

Invite the colleague to explain any uncertainty in the instructions. They can help draft a useful expectation, but their authorship or agreement does not prove that the work will always meet it. Show an example where needed, make the current instruction accessible and check that the work can fit the time available.

2. Recognise the action you actually observed

In the first version of the exercise, the manager opens the submitted draft and finds the date and version label in the agreed place. A brief acknowledgement could be:

“You added the session date and version label to the first page, as we agreed. I could tell which revision I was reviewing. Thank you for making that clear.”

The first sentence names the completed action. The second describes a limited benefit the fictional manager actually observed. The third offers thanks without turning the observation into a prediction. This does not establish that every colleague will use the correct file, that the session will run smoothly or that staff performance has improved.

If you have not checked an effect, say why the action matters rather than claiming it already produced a result. “The version label is there so reviewers can identify the draft” explains the purpose. “You prevented all the confusion” would require evidence the manager does not have. Specific praise need not be elaborate; accuracy matters more than adding a dramatic consequence.

Keep the recognition proportionate to what you saw. If the colleague worked from an example or with help, acknowledge the completed work without claiming they did it unaided. Do not turn “This label is clear” into “You are the only organised person here.” Comparing colleagues adds a judgement about others that the observation cannot support.

Choose a setting that suits the person and the work. A quiet acknowledgement may be preferable to praise in front of a patient or the whole team. Where it is useful, ask how the person prefers contributions to be recognised. Notice routine preparation as well as visible last-minute rescue work, including contributions across different shifts.

Let appreciation stand on its own when that is the purpose. Attaching an unrelated correction to every thank-you can make the actual message difficult to identify. Equally, you do not need to find something to praise before addressing a problem that needs attention.

3. Check your account before asking for a correction

Now use an alternative version of the same fictional exercise. The manager opens a copy with no version label on its first page. That observation is about the file on the screen; it does not yet establish which file the colleague submitted. A short opening could be:

“The copy I opened has no version label. Our brief asked for the date and version on the first page. Is this the draft you sent for review, or am I looking at an earlier copy?”

This names the observation and the previously agreed requirement while leaving room to correct the manager's account. “You ignored the brief again” would add both a motive and a history that have not been established. Keep the question answerable without requiring the employee to defend their character.

Suppose the colleague points to the submitted file, which has both labels, and the manager confirms that they opened an older copy. The response should change:

“You are right. I opened the earlier file. The submitted draft has the labels we agreed. My comment about a missing label was mistaken; I will correct any note I made about that.”

Do not turn this into a criticism of the colleague for failing to anticipate the manager's mistake. If the file-location process needs attention, discuss that as a separate question with the available facts. An employee's correction of your account is not itself evidence of resistance.

In a different branch of the exercise, both people confirm that the submitted draft really lacks the agreed label. The manager can then be direct:

“This review copy is missing the version label. Please add it in the agreed place before we continue the review. Is the format clear, and what working time do you need to make that change?”

Ask what made the requirement difficult to meet and listen to the answer. Missing information, conflicting instructions or insufficient time may need a different response from a simple omission. Checking the context does not make the requirement disappear. It helps you decide what correction and support are actually needed.

A statement such as “I know you will never do it again” cannot establish that the work is corrected. Respect the person while describing the action plainly. You can say what needs to be done without labels such as careless, unreliable or uncommitted, and without making the person agree with your interpretation before they can explain.

4. Separate a missed requirement from a new request

Return to a draft that meets the original date-and-version requirement. The manager now wants a short note stating what changed from the previous version. That may be a useful addition, but the fictional brief did not ask for it. It should be introduced as a new request:

“The first-page labels meet the requirement we agreed. I would now like a short note identifying what changed between versions. I did not include that requirement earlier. Let us agree what it should contain and when it can be added.”

This matters because the same missing element can mean different things depending on the prior agreement. A requirement that was clearly communicated can be reviewed as such. A preference that the manager has just formed needs explanation and a feasible plan. Do not rewrite the history of the brief to make a new request look like an old failure.

Check what the addition involves. The colleague may need the earlier version, time to compare it or a decision about which changes should be described. If those resources are missing, supply them or narrow the request. Asking someone to add a “quick line” does not prove that the underlying comparison is quick.

Keep support specific to the task. Someone experienced in the practice may still be unfamiliar with this version process, while a new colleague may already know it. Offer the instruction or example the actual gap requires. Tenure alone is not a reason to remove checks, intensify praise or assume that detailed guidance is unwelcome.

5. Finish with the right next step, even when it needs longer

For routine feedback, speak while the relevant work can still be identified and acted on, in an appropriate place and during feasible working time. A brief correction deserves privacy; it should not be delivered in a corridor where patients or unrelated colleagues can hear it. If the setting or timing is wrong, arrange a suitable opportunity rather than saving several unrelated examples for a surprise list later.

A short exchange is enough when the point is understood and any necessary next step is clear. In the missing-label branch, agree when the colleague can revise the draft and when the manager will check it. At that check, confirm that the label is present in the intended review copy. That verifies the specific correction, not the quality of every future document.

If the conversation reveals conflicting versions, repeated unclear instructions or a workload problem, set aside the time needed to examine that issue. Do not end it because the minute has elapsed, and do not wait for an arbitrary number of repeated mistakes before providing more support. The action may include the manager clarifying the current file, making an example available or arranging time that was never provided.

Keep any note proportionate: the task and version checked, the expectation that applied, the observation, the employee's relevant explanation, the agreed action and the review point. Include the manager's own correction or commitment. Store necessary notes through the appropriate process and allow inaccuracies to be raised; do not turn ordinary feedback into a public ranking or a collection of private personal explanations.

A conversation ending does not mean the matter can never be revisited. Follow up on the agreed correction, and use the appropriate process if a recurring or serious concern needs fuller handling. An urgent safety issue requires prompt action through its established route, without waiting for prior praise or a private coaching slot. Harassment or other formal concerns also need their proper route, not a compressed version of this exercise.

When recognising patient-facing work, apply the same discipline to the result you praise. Accurate information and respect for a patient's choice are worth noticing. Immediate booking or treatment acceptance alone does not establish good service. Questions about affordability, taking time, declining and rescheduling must remain legitimate choices.

Before your next brief response, identify the expectation, the action you observed and the result you can honestly describe. Say what you appreciate or what needs checking, listen for a correction to your account and agree the next step if one is needed. The aim is a clear, respectful response to actual work. Its quality is shown by the accuracy of the exchange and the follow-through, not by how quickly you finish speaking.