WORK IS A CONTRACT. NOT A FAMILY.

"We're a family here."

It's said with the best intentions. Warmth. Belonging. The sense that the people in this building care about more than the output. I understand the appeal. In a world where work takes up a disproportionate share of life, the idea that the place absorbing all that time might actually give a damn feels meaningful.

But I think it's the wrong framing. And I think it does quiet damage in ways that don't get talked about honestly.

The Family Frame

When an organization positions itself as a family, it's making an implicit promise: the standards of a family will apply here. Loyalty is unconditional. Support is personal. People are valued for who they are, not just what they produce. Conflict is handled privately, with care, in the interest of preserving the relationship.

This sounds good. In a family context, it is good.

In an organizational context, it creates problems that compound slowly.

Families don't have performance standards. They have love. You don't fire a family member for underperformance. You don't expect a family member to have measurable outcomes by the end of the quarter. The loyalty is not contingent on contribution — and that's exactly what makes it meaningful in the family context.

When you apply family logic to an employment relationship, you muddy the standard. Suddenly holding someone accountable feels like betrayal. Setting a performance expectation feels clinical. Letting someone go feels like abandonment. The emotional register of the family frame makes every hard decision harder than it needs to be — and makes the people doing the deciding feel worse about doing it.

Meanwhile, the work still has to get done.

What Work Actually Is

Work is a contract.

This sounds cold. I'd argue it's the opposite.

A contract is honest. A contract says: here's what I will do for you, here's what I expect in return, here's what success looks like, here's what happens if the terms aren't met. A contract is specific, clear, and doesn't pretend to be something it isn't.

An employment relationship is genuinely contractual: the organization offers compensation, development opportunity, and a work environment. The employee offers effort, skill, and professional contribution. Both parties have expectations. Both parties can be let down by the other. Both parties have real interests worth protecting.

Calling it a contract doesn't diminish the relationship. It clarifies it. And clarity — as I've argued everywhere in my writing — is the foundation on which real respect is built.

You can have warmth inside a contract. You can have genuine care, real camaraderie, meaningful relationships. Most enduring professional relationships have all of these things. What you can't have is the pretense that the relationship is unconditional when it isn't — because that pretense makes the people inside it less able to advocate for themselves, less prepared for the hard conversations, and less able to make clear-eyed decisions about their own interests.

The Hidden Cost of Family Culture

Organizations that lean hard into family language tend to develop a specific kind of dysfunction: the inability to have honest conversations about performance.

In a family, you don't put your brother on a performance improvement plan. You have a long, emotional conversation over Thanksgiving. You give him another chance, and another, and another, because he's family and that's what families do.

In an organization, that same dynamic produces chronically underperforming teams, resentment from the people who meet standards and watch others not be held to them, and a gradual erosion of the belief that performance actually matters.

The irony is that the family language, intended to create belonging and psychological safety, often produces the opposite: an environment where people can't be honest about problems because honesty threatens the emotional contract, where hard conversations get avoided until they're impossible, where the people who most need direct feedback never receive it because directness feels cruel in a family.

High-performing teams are not families. They're something better: groups of people who trust each other precisely because they're honest with each other. Who can have hard conversations because the relationship is built on professional respect, not unconditional loyalty. Who can give and receive feedback without it feeling like a referendum on their personal worth.

The Distinction That Actually Matters

None of this is an argument for cold organizations. The research on psychological safety, employee engagement, and high-performing teams is consistent: people do better when they feel respected, valued, and safe to speak up.

But safety doesn't require pretending the relationship is something it isn't.

Real safety, in an organizational context, comes from clarity: knowing what's expected of you, knowing that the standard applies equally to everyone, knowing that honest conversation is welcomed rather than punished, knowing that the relationship is durable enough to survive disagreement.

That's not family. That's trust.

And trust, built on clarity rather than unconditional loyalty, is more resilient than family language ever produces.

You can care deeply about the people you work with. You can invest in their development, advocate for their interests, and build environments where they feel genuinely valued. None of that requires calling it family.

Call it what it is: a professional relationship, built on mutual respect and honest expectation.

That's not less than family.

In most cases, it's more.