Fairness and recognition

Fairness at work has three sides. Outcome: what people get (pay, bonus, shifts, projects). Process: how it was decided (consistently, with a voice for the people affected, on accurate information, open to correction). Treatment: how people were dealt with along the way (with respect, and with an honest explanation).

The sides don't weigh the same in practice. People accept an outcome they dislike far more readily when the process was consistent, they had a say and someone explained the decision honestly. A good outcome reached through a closed process still feels unfair.

So listen for which side a complaint is about. Maryna says she isn't upset about the money; she's upset that a rule about the team's work was set without one question to them, and that nobody can explain why careful replies count for nothing. That's process. Treating it as a pay demand, or as her motivation problem, answers a question she didn't ask.

A lead may not set pay, but owns a lot of fairness decisions: who gets hard tickets, who works the late shift for EU families, who gets the interesting projects. Each one is a small distribution of good and bad work.

The most common way these go wrong is by default: nobody decides, and the pattern settles on whoever doesn't say no. At Klasna, Dmytro and Sofiia have had the late shift every week since March. Nobody chose that; they're seasonal and never objected.

A fair rule has four features. It is known in advance (a rotation everyone can see a month ahead). It is applied the same way to everyone, not by contract type. It is explained, including its exceptions (a health issue, say). It is open to challenge, with swaps allowed and noted in the rota. Rules like "whoever is online when the shift opens takes it" reward whoever logs off fastest, and "seasonal staff first" is unequal treatment, which is exactly how the default arose.

It's tempting to think that pay and bonuses decided above you are not your problem. They are, in three concrete ways.

First, explain the process honestly: what the rule is, who set it and why, as far as you know, without defending what you don't understand and without blaming your manager. Second, carry the team's view upward with evidence: what people say, what the numbers show, what you'd keep and what you'd change. Iryna asked for exactly that in writing: "I'd rather fix the rule than lose Maryna." Third, ask for a voice next time: a rule about the team's work is better when the team is asked before it starts.

What you don't do: promise a change that isn't yours to make, or discuss a colleague's pay. And remember that the decisions you do own (hard tickets, shifts, projects) are fairness decisions too, often the ones people feel every week.

Fairness questions often arrive as a question about someone else's pay: "How much did Taras get?" The answer is the same every time: a lead never discusses a colleague's pay, and makes the rule as clear as possible instead.

The distinction matters. A person's pay is their own information; sharing it, even as a hint ("a lot"), breaks their trust and sets two reports against each other. The rule, on the other hand, should be open to everyone it affects: how the bonus is calculated, who decided it and why, what it counts and what it doesn't. Most fairness complaints are about the rule anyway.

So answer the concern, not the curiosity: "I won't discuss anyone's pay, yours included. I can explain how the rule works, and I'm taking the team's view to Iryna this week." Don't shut the question down either; "none of your business" ignores a real worry about whether the system is fair.

A quick test for any decision about pay, promotion, workload or opportunities: could you explain it to everyone it affects, in the same words? If you need one story for the person who benefits and another for the person who doesn't, the decision probably rests on something you wouldn't say out loud.

The test works best with criteria set before the decision. For a stretch project: who has the skill gap it would close, who has capacity this month, who hasn't had one recently. Announce the criteria, then pick. Promotion works the same way: known criteria, not a reward for whoever the lead knows best or likes most.

The test also produces evidence. The lead can't explain Iryna's bonus to Maryna and to Taras in the same words: it pays one for speed and gives the other almost nothing for the best quality in the team. That mismatch is worth writing down for Iryna, who asked for the team's view in writing.

Recognition is the cheapest fairness tool: noticing a specific contribution, soon, in a form the person values. It costs nothing and it works only when it's sincere and specific.

A message that lands has three parts: what the person did, what it changed for someone, and that you noticed it soon after. "Your reply to the family whose maths tutor left mid-package found them a new tutor the same day; they wrote back to thank us" tells Bohdan exactly what to repeat and why it mattered.

Three common forms miss. Generic thanks ("thanks for all your hard work this month") could be sent to anyone, so it says nothing. Praise of a trait ("our most experienced person, as always") is about who he is, not what he did. And "good, but next time a bit faster" turns thanks into criticism: people remember only what comes after "but". Keep thanks and feedback in separate messages.

Recognition only works when it lands with the person, and people differ. Some enjoy a thank-you in the team channel; others find it embarrassing and would rather hear it one to one. Don't guess: ask once, then remember.

In a remote team, written thanks last longer than a word on a call: the person can reread it, and it leaves a trace for the review season. A short message after the fact ("your review caught two wrong refunds before they went out") beats a general shout-out at the end of the month.

Watch the spread as well as the form. Recognition is a fairness tool, so it has to be fair itself. It's easy to thank the visible work, such as the fastest closes or the dramatic rescue, and never notice the quiet work: Maryna's careful replies, Olha's reviews, the hand-up note that saved an hour. Once a month, check whose name you haven't mentioned, and look for what they did.

When someone says a rule is unfair, most leads jump straight to explaining it. Explain before you've listened and checked the facts, and you end up defending a rule you don't fully understand.

A sensible order has five steps. Listen and repeat back what the person sees as unfair, so they know you got the actual complaint. Check the facts: how the rule was set and who it affects. Explain honestly what you know about the process, and what is and isn't your decision. Act: fix what you own, or take the case upward with evidence. Close the loop: come back with an answer, even if the answer is "no change yet". Olha's warning: most leads skip that last step, and the team notices. A complaint that disappears into silence feels like the same unfairness twice.

How it fits together: fairness is outcome, process and treatment; rules known in advance, the same-words test and fair recognition keep it visible. Next, the module's case, The "tickets closed" bonus: the April numbers and your proposal to Iryna.