Why does one promotion decision damage a whole team?
When Decisions Look Arbitrary
People accept unwelcome outcomes from a process they consider legitimate. Process transparency does more work than outcome generosity.
Analysis
Fairness is the area where a single visible failure does disproportionate damage, and where the remedy is mostly procedural.
Process over outcome
The consistent finding: perceived fairness of the process affects acceptance more than the favourability of the outcome.
Someone passed over for promotion through a clear, consistently applied process is disappointed.
Someone passed over through an opaque process concludes the system is rigged, and that conclusion generalises to everything else.
This is why transparency is cheap and effective. It does not require giving people what they want.
Where fairness fails visibly
Pay. Opacity invites the least generous assumption, and people talk anyway. Compression, where new hires arrive above long-serving staff, is noticed and rarely explained.
Promotion. Criteria that are unstated, or stated and then not applied.
Workload distribution. The reliable person given more because they are reliable, which is a punishment for competence.
Policy application. Rules enforced for some and not others, particularly where the exception is a senior or high-performing person.
Recognition, distributed by visibility rather than contribution.
Flexibility, granted informally, which means granted to those who ask and those the manager likes.
The high performer exception
Worth naming separately because it is the most common single fairness failure.
Someone whose output is valuable behaves badly, or ignores process, or receives accommodations others do not.
Everyone sees it.
The message received is that the stated standards apply to ordinary people. That message damages more than the individual's behaviour does.
Consistency here is expensive and it is the price of the standards meaning anything.
Making process visible
Publish the criteria for pay bands and promotion, even approximately.
Explain decisions to the people affected, with reasons that are specific.
Show the distribution, where possible. Ranges, timelines, how many progress and when.
Apply policy consistently, and where an exception is made, be able to state the principle behind it.
Give a route to challenge that produces an actual answer.
The grievance problem
A process nobody trusts is worse than no process, because it consumes effort and confirms the suspicion.
Test yours: ask people whether they would use it, and whether they think it would change anything. The answers are usually known and unspoken.
A process with no outcomes — where nothing has ever been upheld — is telling you something about itself.
Track outcomes and report them in aggregate. A process that visibly finds in favour of complainants sometimes is a process people will use.
The measurement
Fairness perception is measurable and rarely measured.
Do you understand how pay is decided here?
Do you believe promotion decisions are made on stated criteria?
Are the rules applied consistently regardless of who is involved?
If you raised a concern, do you think anything would happen?
Segment the results. Fairness perception frequently varies sharply by team, level and demographic group, and the average conceals exactly the finding worth having.
Testing your grievance route
A process nobody trusts is worse than none, and its condition is knowable.
Ask people whether they would use it. Anonymously, and the answer is usually already known informally.
Ask whether they believe it would change anything.
Look at the outcomes. A process that has never found in favour of a complainant is telling you something about itself.
Look at what happened to people who used it, afterwards. If they left within a year, everyone noticed.
Report outcomes in aggregate: how many raised, how many upheld, what changed. A process that visibly produces outcomes sometimes is one people will use.
Where the answers are bad, say so and rebuild it rather than continuing to publish a route nobody believes in.
Explaining an unwelcome decision
Process legitimacy is mostly built at this moment, and most organisations handle it badly.
Say the decision plainly, first, without preamble.
Give the actual reason, not the presentable one.
Say what the criteria were and how they were applied.
Say what would need to be different for a different outcome.
Allow the reaction without defending.
Follow up in writing if the person wants it.
People accept disappointing outcomes explained this way. They do not accept silence, and they especially do not accept a reason they can tell is not the real one.
Also in this section
- Everyone is at capacity all the time. How did that happen?
- Why is my team stressed when the workload is not extreme?
- We pay well. Why does the team feel undervalued?
- The team is fine individually but something is wrong collectively.
- Good people are leaving and saying the culture changed.
- Nobody is required to work evenings, so why does everyone?