Skip to content
Playbook
IntermediateHRFounderManager

Broken HR advice #2: 'We're a family'

Families don't fire each other. Why this framing produces worse outcomes for everyone — including the loyalists.

6 min read
On this page
60-Second Summary
  • Netflix's culture deck explicitly rejected 'family' in 2009 — and the empirical retention/performance data over the next decade vindicated the choice.
  • Family framing produces unhealthy loyalty: employees stay too long, founders defer hard feedback, and exits feel like betrayal on both sides.
  • The mature alternative is the sports-team metaphor — high investment in the player, but no pretence that the relationship is unconditional.

If you would not fire your sister to hit Q3 revenue, you are not a family. You are an employer. Conflating the two does damage in both directions.

Why family language fails

  • It suppresses difficult feedback — managers withhold honesty because 'family doesn't talk to family like that.'
  • It creates exit guilt — leaving feels disloyal even when career-correct.
  • It enables tenure inertia — early employees who plateau are protected past their useful contribution.
  • It collapses during stress — the layoff or PIP shatters the implicit contract, producing more bitterness than a transactional framing would.

The sports team alternative

We're a team, not a family. We're like a pro sports team — we invest heavily in players, but if a position needs an upgrade, we make the move.
Reed Hastings, No Rules Rules

The sports-team frame allows two truths to coexist: the company invests in the individual's development AND the individual is accountable to perform. Either side can end the relationship without it being a moral failing.

For the loyalists

The cost on the most loyal employee

Loyalty-rewarding cultures often punish their best people. The engineer who stayed for seven years out of a sense of family obligation watched five outside hires earn 40% more. That's not love — that's a tax on loyalty.

Written by Pawan Joshi.Sources cited inline.
First published 7 Oct 2024See site changelog →