liveBook · Manning

Fairness

As explained in Think Like a Software Engineering Manager

Fairness is the equitable and impartial treatment of people according to consistent standards and processes.

Fairness means treating people impartially through consistent standards and processes. For an engineering manager, it matters when evaluating performance, assigning work, giving recognition, and supporting growth. Consistency does not mean ignoring circumstances: an employee with caregiving responsibilities may need empathy and support while still being assessed against clear expectations. section 4.2.2 section 5.3.3

Make fairness visible in everyday decisions:

  • Set shared performance standards. Use a leveling guide where available, and evaluate employees against it rather than relying on recent impressions or personal preference. section 4.2.2
  • Prepare evidence for calibration. Cross-team discussions compare proposed ratings against company standards and can expose favoritism or inconsistent judgments. section 4.3.2
  • Spread opportunities. Match delegated work to abilities and career goals, but do not give every valuable assignment to top performers. section 5.3.3
  • Check who receives recognition. Define criteria, consider data and peer input, and periodically review awards for bias—including whether less visible work is overlooked. section 6.2.5
  • Support equitable treatment beyond reviews. Provide a way to raise and appeal perceived unfairness; attend to inclusion, accommodations, and equal compensation for equal skill and experience. section 4.2.2 section 7.5.3

A fair performance discussion

When assessing two employees, compare each person’s work with the same leveling guide rather than comparing personalities. If one is caring for an elderly parent or experiencing a temporary change in productivity during pregnancy, discuss support and how the team can share work. Bring documented strengths, weaknesses, and growth opportunities to calibration so the proposed ratings can be checked across teams. section 4.2.2 section 4.3.2

Fairness is an ongoing check, not a one-time policy. Ask whose work is noticed, who gets growth opportunities, and whether people have a credible way to challenge a decision. section 6.2.5 section 4.2.2

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides practical checks for standards, bias, appeals, and recognition while acknowledging that no single bias-reduction approach fits every situation.
Examples
Uses two employees’ performance assessments, caregiving accommodations, delegated intern mentoring, and recognition of technical-debt work.
What you can do after
Practice/perform fairer decisions by applying shared criteria, distributing opportunities, reviewing recognition patterns, and providing routes to appeal.
How it connects
Links fairness to leveling guides, performance calibration, delegation, recognition, and diversity, equity, and inclusion.

Also explained in

Compare how 10 books explain fairness →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.