We're Not a Family. We're a Team. Here's Why That's Kinder.

This week, our People and Culture manager sent me a draft message for the team. It was warm, well written, and it used the word family.

I sent her a short note back. Avoid using the word family in any communication; always use team instead. Then I wished her a good long weekend.

It took about ten seconds to write. It took me years to learn.

Why the word bothers me

Here's the thing: a modern workplace is not a family, and calling it one doesn't make it one. It just makes the relationship harder to see clearly.

What a workplace actually is, is an exchange. We pay people to do good work. They give us their skill, their attention and a large share of their working hours.

They rightly expect to grow, in ability and in income. And sometimes the best growth for them is somewhere else, so they leave for a better salary or a bigger role.

That's not a failure of the relationship. That IS the relationship.

There's a reluctance to say this out loud, because "transactional" sounds cold.

I don't think it is. I think an honest exchange is more respectful than a sentimental one, because it doesn't quietly ask people for things the job isn't paying for. Loyalty beyond reason. Availability beyond hours. Guilt when they leave.

Nobody signs an employment contract expecting to be adopted.

Mislabelled relationships

So here's the model I've taken from it, and it's useful well beyond hiring.

When you label a relationship as something it isn't, every normal act inside it starts to look like betrayal.

Call your company a family, and watch what happens to ordinary events. An employee resigns for a 30 percent raise; it feels like desertion.

A founder restructures a team to keep the business healthy; it feels like abandonment. Someone declines to answer messages on a Sunday; it feels like they don't care.

None of those are betrayals. They're the normal operations of a working relationship. They only feel like betrayals because the label promised something else.

Netflix said this out loud years ago in its culture memo, describing itself as a team rather than a family. I think that's more honest than it first sounds.

A team asks a great deal of you inside the work and very little outside it. And a team expects people to move on; players change, and the team carries on.

You'll find the same pattern elsewhere. Founders call clients "partners" and then feel wounded when the client shops around. Agencies call vendors "an extension of our team" and then can't understand why the vendor won't work weekends for free.

The label set up an expectation the arrangement was never built to meet.

The fix is boring and effective: call each relationship what it is, and then do that relationship exceptionally well.

From people to process

There's a second thing the honest label changed for us, and it took longer.

In our earlier years, the business ran on particular people. Certain things only got done because a certain person knew how.

Which meant a lot of Harshit’s time and my own time went into managing personalities: keeping specific individuals happy, working around specific moods, worrying about what would happen if specific people left.

Thinking of the company as a team, not a family, forced a better question. If people will move on, and they will, what does the work need so that it doesn't depend on any one person?

The answer was process. Documented ways of working, clear handovers, systems a new person can step into and become useful in quickly.

Look at that last row, because it's the part people get backwards. Process dependence sounds like it makes people replaceable. In practice it protects them.

The person who is the only one who knows how something works can never fully switch off, never be ill in peace, never leave without guilt. A good system frees them from all of that.

The boundary outside work

And then there's privacy, which is the lesson I've had to learn most slowly as an employer.

Beyond working hours, our people have their own lives. Where they go, what they wear, who they spend time with and what they're planning next is their business, not ours.

I don't think an employer earns any claim on those things by paying a salary. The salary buys work. It doesn't buy the rest of a person.

That sounds obvious written down. It isn't always obvious in practice, especially when you've worked closely with someone for years and genuinely like them.

Liking someone is fine. Feeling entitled to their life is the family label creeping back in.

Why the honest version compounds

Here's why I think this matters for the long game, not just for tone.

A family label buys a short burst of warmth and then charges interest every time reality disagrees with it.

Each resignation stings more than it should. Each boundary feels like a rejection. Over years, that builds a quiet resentment on both sides.

An honest label works the other way. Because nobody was promised more than the job, people can leave well, and people who leave well speak well of where they were.

Some refer others. A few come back. And because the work runs on systems rather than on particular personalities, every person who passes through leaves it a little better documented than they found it.

That accumulates. Not as sentiment, but as a company that keeps getting easier to join, easier to work in, and easier to leave on good terms.

So no, we're not a family.

We're a team. And I'd like to think we're a very good one.