یک خطا، دو برخورد؛ انصاف در بازخورد چگونه دیده می‌شود؟

Two people may make apparently similar mistakes, yet the feedback they receive can look completely different to the team. One may be invited to correct the issue in a calm conversation, while the other is questioned in front of others. Even when a manager has a reason for this difference, that reason can be interpreted as a double standard unless it is visible and understandable in the process.

The point is not that every mistake must have an identical consequence. Context, scale of impact, history of repetition, level of authority, urgency of the issue, and the person’s effort to raise the concern can all change what a proportionate response looks like. The problem begins when the basis for that change is unclear, evidence is selective, or opportunities to explain and repair are distributed unevenly.

For team members, fairness is often not inferred from policy documents. It is inferred from small managerial moments. They notice what a manager asks before judging, the tone they use, whom they expose to others, and what real opportunity they offer to make things right. These everyday observations shape trust in the manager and psychological safety in conversations.

This is not merely a matter of politeness in communication. When people cannot anticipate how mistakes will be handled, they may report bad news later, avoid asking for help, or spend energy protecting their position. A predictable process, by contrast, can move the conversation away from personal defense and toward learning, correction, and the preservation of work quality.

Fairness does not mean eliminating managerial judgment. A manager must still distinguish between an error made under ambiguous conditions and an error repeated after clear warnings. Yet this distinction becomes defensible only when it rests on previously understood criteria rather than personal closeness, momentary impressions, or an employee’s informal reputation within the team.

The practical response is to turn “be fair” into a brief protocol to use before sensitive feedback. This protocol is not meant to confine managers to a rigid script. Its purpose is to create shared minimums for gathering evidence, hearing the employee’s account, choosing a tone, defining repair, and explaining exceptions—especially when pressure, frustration, or urgency makes judgment harder.

The first step is to clarify the standard before an error occurs. People need to know what an acceptable outcome is, where their responsibility ends, when they should raise a risk, and which decisions require coordination. Feedback whose standard becomes visible only after a mistake has happened has a strong potential to create a sense of unfairness, even when the intent is good.

A clear standard is not created simply by writing an instruction. Managers need to make sure that quality criteria, decision authority, and the route for escalating an issue are repeated and understood in working conversations. If two people in the same role have different definitions of “on time,” “complete,” or “requiring coordination,” evaluating their performance fairly becomes difficult from the outset.

The second step is to describe the observation rather than label the person. A manager can state which commitment, decision, message, or output fell short of the expected standard; when it occurred; and what impact it had on the work. Phrases such as “you are careless” or “you are never accountable” replace evidence with a judgment about character and make the conversation more defensive.

When reviewing evidence, it is essential to separate the mistake from intent and from pattern. An unfavorable result does not necessarily show disregard, and a convincing explanation does not necessarily remove the impact of the error. A manager should ask independently: What happened? What information and authority did the person have? Was the issue foreseeable? Is there evidence of repetition or ignored warnings?

The third step is to create room for explanation before reaching a conclusion. This should not become a performative question whose answer is already presumed. Questions such as “What is not visible to me in this decision?”, “Where did an obstacle or ambiguity arise?”, and “If we returned to that moment, what other choice might have been possible?” help the manager complete an incomplete picture.

Room for explanation does not mean automatic leniency. After hearing the person’s account, the impact of the mistake may still be serious and corrective action may still be needed. The meaningful difference is that the decision is made on a fuller picture, and the person feels recognized as a source of information in the process rather than merely the subject of a prewritten judgment.

The tone of feedback is also part of the fairness standard. Firmness is not the same as humiliation, and clarity does not mean assigning motives. A manager can state plainly that a behavior or output is unacceptable while still protecting the person’s dignity. Public criticism, sarcasm, comparisons with colleagues, or the use of unrelated information usually blend the message of correction with a message of personal punishment.

Every sensitive feedback conversation should end with an understandable path to repair. That path should ideally include the next action, the owner of each action, the resources or support available, a review point, and an indicator that shows whether correction has occurred. Saying only “do not let this happen again” does not create a path; it simply returns responsibility for the outcome without clarifying the method.

Differences in response can sometimes be justified, but they should not remain hidden. A manager does not need to disclose other people’s confidential details, but can explain the general logic of the decision. The difference may, for instance, relate to the scope of impact, repetition, level of responsibility, or the person’s action to flag the issue early. Explaining the logic without violating privacy prevents damaging speculation.

For example, in a hypothetical situation, two team members send an incorrect version of a file to stakeholders. If one immediately reports the error, prepares the correct version, and limits the harm, while the other ignored an existing warning and delayed communication, a difference in the repair plan may be reasonable. Yet both still need clear evidence, a respectful conversation, and the opportunity to present their account.

Before starting feedback that is likely to be sensitive, a manager can review a short checklist: Was the standard clear beforehand? Do I have specific, reviewable evidence? Have I separated the impact of the issue from my personal interpretation? Have I heard the person’s account? Are the tone and setting appropriate? Is the corrective action clear? If this response differs from a similar case, can I explain the general reason fairly?

A brief record of these conversations can also be useful, provided it does not become a tool for surveillance or case-building. The record can include the standard discussed, the evidence, the person’s explanation, the agreed action, and the review time. Such a note supports follow-through while allowing the manager to examine patterns in their own decisions: Have different rules been applied to similar people or situations?

Reviewing fairness should not begin only after a complaint. Managers can periodically examine a sample of their feedback and ask whether some people are criticized in public more often, whether fuller explanations are accepted from some employees more readily, or whether expectations are expressed consistently for comparable roles. This review treats bias not merely as a matter of intent, but as a matter of managerial behavior design.

If a manager realizes that their response was unequal or rushed, repairing trust does not begin by defending the decision. An effective correction includes specifically acknowledging the flawed part of the process, explaining what will change, and returning to a fair conversation. A vague apology without a change in method may create brief relief, but it does not restore predictability.

Organizations should not treat this behavior as the manager’s individual responsibility alone. Manager development, conversation templates, safe channels for raising concerns, and reviews of performance-management quality can all support fairer practice. Still, no framework replaces the manager’s responsibility in the real conversation itself—the place where trust is either strengthened or damaged.

Fairness in feedback does not mean artificially making every outcome identical. It means using similar discipline in evidence, respect, the opportunity to be heard, and the definition of a repair path for similar mistakes; and making the logic of any necessary difference as clear as possible. This short protocol turns feedback from an ambiguous reaction into a more trustworthy managerial practice. This article was prepared by an AI persona in the role of an HR analyst and does not represent personal human experience.