Workplace Favoritism Isn't a People Problem, It's a Design Problem

Workplace favoritism isn't usually caused by a manager who wakes up deciding to treat people unfairly. It's caused by an organisation that never built clear, structured ways to make decisions about promotions, projects, and feedback, so managers fall back on instinct, comfort, and proximity instead. Fix the structure, and most of what gets labelled favoritism quietly disappears.

That's a different starting point from most advice on this topic. Most of it tells the employee on the receiving end how to spot it, how to talk to HR, and how to protect their own career while someone else gets the better assignments. That advice has its place. But it treats favoritism as a personality flaw in one manager, something to be managed around rather than removed. In practice, workplace favoritism is far more often a predictable output of how work gets assigned, how performance gets judged, and who gets access to decision-makers, the same structural gaps addressed through deliberate organisational design.

What Workplace Favoritism Actually Is

Workplace favoritism is when access, opportunity, or leniency is distributed based on personal closeness rather than performance or role requirements. It shows up as one person getting the visible project, the benefit of the doubt on a missed deadline, or a seat in the room where decisions get made, while someone doing comparable work does not.

It's worth separating this from two things it often gets confused with. Favoritism is not the same as recognising genuine high performance, rewarding someone who consistently delivers is not favoritism, even if it looks similar from the outside. It's also not automatically illegal. In most jurisdictions, favoring someone because you like them, trust them, or find them easy to work with is legal, if unfair. It only becomes unlawful discrimination when the preference tracks a protected characteristic such as race, sex, age, or disability.

What makes favoritism at work so corrosive is that it rarely announces itself. Nobody sends an email saying "I'm choosing you because I like you more." It shows up quietly, in who gets looped into an informal conversation before a formal one happens, whose ideas get repeated back as the manager's own good idea, and whose small mistakes get remembered while someone else's identical mistake gets forgotten.

Why "It's a People Problem" Is the Wrong Frame

The instinct to treat favoritism as a people problem comes from a reasonable place. A manager is doing the favoring, so surely the manager is the problem. Send them to a bias workshop, tell them to be fairer, and the issue should resolve.

It rarely does, and there's a simple reason why. Most managers who play favorites don't experience themselves as biased. They experience themselves as trusting the person who's proven reliable, or giving stretch work to whoever seems most ready for it. The behaviour feels like sound judgement from the inside. Telling someone to "just be more fair" gives them no new information about what fairness would actually look like in their next decision.

This is where the design problem becomes visible. If a manager has no defined criteria for who gets the high-visibility project, no requirement to document why a decision was made, and no one reviewing the pattern of those decisions over time, they are making dozens of small judgement calls a year with nothing to check that judgement against except their own comfort. Favoritism doesn't need bad intent to take root. It just needs an absence of structure.

The Design Flaws That Make Favoritism at Work More Likely

Certain organisational conditions make favoritism almost inevitable, regardless of who's managing the team.

Vague or unwritten decision criteria. When promotion, project allocation, or stretch assignments aren't tied to explicit, documented criteria, the decision defaults to whoever the manager already trusts. Trust is built through familiarity, and familiarity is built through proximity, not necessarily merit. This is closely related to a pattern we've written about before, where no one knows who owns what, leaving decisions to whoever happens to be in the room rather than whoever should be making them.

No calibration across decision-makers. A single manager's judgement, unchecked by peers or a second reviewer, tends to compound in one direction. The employee who impressed them once keeps getting chosen, because there's no mechanism forcing the manager to compare that choice against other credible options each time.

Informal access replacing formal process. In many organisations, the real decisions happen in hallway conversations, quick messages, or after-hours catch-ups, and the formal process just ratifies what was already decided. Whoever has informal access to the manager, through personality fit, shared background, or simply sitting closer, ends up shaping outcomes that should have gone through a wider, fairer process. It's a similar dynamic to how organisational silos form, where proximity and informal networks quietly start to matter more than the formal structure they sit inside.

Feedback that isn't structured or shared. When feedback is inconsistent, unrecorded, and dependent on whoever remembers to give it, perceived favoritism becomes almost impossible to disprove or correct. One employee gets regular, specific coaching. Another gets silence until an annual review. Neither the manager nor the team can point to a documented, comparable trail.

Reward systems that favor visibility over contribution. If recognition depends on who happens to present in the big meeting rather than who did the underlying work, the system quietly incentivises access-seeking behaviour and rewards the people already closest to power.

None of these require a manager with poor intentions. They require an organisation that never built the guardrails.

How This Plays Out in Practice

Consider a mid-sized team where one person consistently gets the client-facing projects. Colleagues start to describe this as blatant favoritism at work, and from where they're sitting, that's a fair description of what they're experiencing.

Look at the process behind it, though, and a different picture often emerges. There's no defined criteria for who leads a client project. The manager makes the call under time pressure, and defaults to the person who did it well last time, because that feels like the lowest-risk choice. Over several cycles, that "safe choice" compounds into a visible pattern that looks exactly like personal favoritism, and functionally produces the same unfair outcome, even if the manager never consciously decided to exclude anyone else.

This is why fixing the individual decision rarely solves the underlying pattern. The next manager, with the same absence of structure, will likely produce the same result with a different favorite.

The Organisational Cost of Leaving It Unaddressed

Workplace favoritism is expensive in ways that rarely show up on a single line of a P&L, which is part of why it gets deprioritised. It shows up in disengagement among employees who conclude that performance isn't what gets rewarded here, proximity is. It shows up in the quiet exit of strong performers who were never given a fair shot at visibility. Perceived favoritism has been linked in workplace research to lower trust in leadership, weaker team relationships, and reduced motivation, patterns explored in research from Ohio State's Fisher College of Business on how employees experience and respond to perceived favoritism at work.

It also erodes something harder to measure and more damaging over time: people stop bringing their best ideas forward if they believe the outcome was already decided by who's in the room, not what's said in it.

Redesigning the System, Not Just the Manager

If favoritism is a design failure, the fix has to operate at the level of design, not just at the level of individual coaching, although coaching still has a role later.

Make the criteria explicit and written down. Before a promotion cycle, project allocation, or stretch assignment is decided, the criteria should exist in writing, in advance, and be visible to everyone eligible. This alone removes a large share of the ambiguity that favoritism thrives in.

Introduce calibration. No single manager should be the only voice in a consequential people decision. A second reviewer, a panel, or a calibration session where multiple managers compare their choices against shared criteria interrupts the pattern of one person's comfort quietly becoming policy.

Move decisions out of informal channels. If the real conversation happens over coffee and the formal meeting just confirms it, the process needs to be redesigned so the formal conversation is where the decision genuinely gets made, with documented reasoning.

Standardise feedback. Give every manager the same structure and cadence for feedback, and require it to be documented. This doesn't remove judgement, but it makes the judgement visible and comparable across the team.

Rotate access to visibility. Deliberately rotate who presents, who leads the client call, and who gets the stretch assignment, rather than defaulting to whoever performed well last time. This widens the pool of people who get the chance to prove themselves, rather than concentrating opportunity in the same hands.

Audit the pattern, not just the incident. A single decision rarely looks like favoritism. A pattern across twelve months usually does. Organisations that periodically review who received opportunities, promotions, and leniency, broken down by team, often find the pattern before employees have to raise it as a grievance.

Where Individual Awareness Still Matters

None of this means individual self-awareness is irrelevant. A manager who understands their own tendencies, who they naturally trust, what makes them comfortable delegating, where their blind spots sit, will use a well-designed system better than one who doesn't. Structure reduces the damage bias can do. It doesn't require managers to stop being human.

But asking managers to overcome favoritism through willpower alone, without giving them clear criteria, calibration, or documented process, is asking them to solve a systems problem with a personal virtue. It rarely works, and it quietly blames individuals for outcomes the organisation's own design made likely.

A Few Direct Questions

Is workplace favoritism illegal? Not on its own. It becomes unlawful when the preferential treatment is based on a protected characteristic such as race, sex, age, disability, or religion, rather than personal closeness or performance.

How do you prove favoritism at work? Documentation matters more than a single incident. Patterns across time, in who receives assignments, feedback, and recognition, are far more persuasive than one example, whether you're raising it with HR or reviewing it as a leader.

What's the difference between recognising good performance and favoritism? Rewarding demonstrated, comparable performance against clear criteria is not favoritism. The distinction collapses the moment criteria are vague enough that "good performance" becomes a matter of the manager's personal opinion.

The Real Fix Isn't a Better Manager

Favoritism at work will keep resurfacing under new managers, new teams, and new leadership as long as the underlying process stays undefined. Blaming the individual in charge treats a structural gap as a character flaw, and structural gaps don't get fixed by asking people to try harder.

The organisations that actually reduce favoritism aren't the ones with the most self-aware managers. They're the ones that stopped leaving consequential decisions to instinct, and built a process that made fairness the default, not the exception.