I shipped skillcraft.ai !!!
Skillcraft helps you find the best learning resources tailored to your goals. Get a personalized roadmap with the best courses, books, and tutorials. Try it out, for free!
Up to date
Published
4 min read

Trevor I. Lasn

Building tools for developers. Currently building skillcraft.ai and blamesteve.lol

A Company Is Not a Family. It's a Sports Team

'We're not just a company, we're a family!' It's a nice sentiment, sure. But it's also a load of crap.

Families don’t fire you when times get tough. They don’t replace you with someone more qualified. And they certainly don’t expect you to sacrifice your personal life for the good of the “family.”

So if a company isn’t a family, what is it? I’ve come to believe that a much better analogy is a sports team.

Why a Sports Team?

Think about it. A sports team has clear goals, defined roles, and a shared mission. Sound familiar? It should, because that’s exactly what a well-run company looks like. Let’s break it down:

  1. Clear Objectives: In sports, the goal is to win. In business, it’s to create value and turn a profit. Both are measurable, tangible outcomes.
  2. Defined Roles: A quarterback doesn’t suddenly decide to play defense. Similarly, your backend dev shouldn’t be making executive decisions about UI design (unless that’s part of your unique process, in which case, more power to you).
  3. Performance Matters: Let’s be real. If you’re not pulling your weight on a sports team, you get benched. In a company, underperformance should have consequences too. It’s not personal; it’s business.
  4. Constant Improvement: Athletes are always training, always pushing to be better. In tech, if you’re not learning, you’re falling behind. The sports team mentality encourages continuous growth.

The “Family” Trap

I’ve seen too many companies fall into the “family” trap. I once consulted for a startup that prided itself on its “family-like” atmosphere. Sounds great, right? Well, it led to some seriously questionable decisions:

  • They kept an underperforming CTO because he was the founder’s college roommate. “You don’t give up on family,” they said. Meanwhile, their tech was falling behind competitors.
  • They promoted based on tenure rather than skill. “It’s only fair to reward loyalty,” was the justification. The result? A leadership team that was more about longevity than capability.
  • When they finally had to do layoffs (because, surprise, running a business like a family doesn’t always work), it felt like a massive betrayal. People were blindsided because “families don’t do this.”

Spotify’s Squad Model

Let’s look at a company that got it right. Spotify’s engineering culture, particularly their famous “Squad” model, is a perfect example of the sports team mentality in action.

Spotify organizes its engineering department into small, cross-functional teams called Squads. Each Squad is like a mini-startup within the company, responsible for a specific feature or part of the Spotify experience.

Sports team mentality

  • Clear Goals: Each Squad has a long-term mission and short-term goals, just like a sports team has a season objective and game-by-game strategies.
  • Autonomy with Accountability: Squads have the freedom to decide how to best achieve their goals, but they’re also accountable for their results. It’s like a coach trusting their players to make decisions on the field.
  • Cross-functional Collaboration: A Squad includes not just developers, but also designers, product owners, and others. It’s like having offense, defense, and special teams all working together.
  • Adaptability: Squads can be formed, changed, or dissolved as needed, much like how sports teams trade players or change strategies based on performance and needs.

This model has allowed Spotify to remain innovative and agile, even as they’ve grown into a tech giant. It’s not about being a family; it’s about being a high-performing team.

So, how do you shift from the “we’re a family” mindset to the more realistic and effective sports team approach? Here are some practical steps:

  1. Set Clear KPIs: Just like sports teams have clear metrics (points scored, games won), your teams should have clear, measurable goals.
  2. Regular Performance Reviews: Athletes get constant feedback. Your team members should too. Make reviews a normal, non-threatening part of work life.
  3. Encourage Skill Development: Allocate time and resources for your team to level up their skills. It’s like training sessions in sports. A great example of this mindset in action is Google’s 20% rule, where engineers could dedicate one-fifth of their workweek to side projects, leading to innovations like Gmail and AdSense.
  4. Celebrate Wins, Learn from Losses: Had a successful product launch? Celebrate it! Project didn’t meet expectations? Analyze why and learn from it.
  5. Foster Healthy Competition: Internal hackathons, coding challenges, or even friendly competitions between teams can drive innovation and improvement.

The Bottom Line

Look, I get it. The “family” analogy feels warm and fuzzy. It sounds nice in recruiting pitches and company all-hands meetings. But it’s not honest, and it’s not helpful.

A company is not a family. It’s a group of professionals working together towards common goals. And the sooner we embrace that reality, the healthier our work cultures will be.


Found this article helpful? You might enjoy my free newsletter. I share dev tips and insights to help you grow your coding skills and advance your tech career.


Check out these related articles that might be useful for you. They cover similar topics and provide additional insights.

Reflections
6 min read

The Monday Morning Test to Measure Engineering Team Health

Why the first day back can reveal everything about your engineering team's health

Nov 4, 2024
Read article
Reflections
4 min read

Unrealistic Deadlines In Software Engineering

Unrealistic deadlines are more than just stressful—they set engineers up for failure

Sep 7, 2024
Read article
Reflections
5 min read

Conway's Law: The Hidden Force Shaping Your Software Architecture

If you've ever wondered why your carefully planned software architecture ends up looking suspiciously like your org chart, you're not alone. Welcome to the world of Conway's Law.

Sep 24, 2024
Read article
Reflections
3 min read

The 5:1 Rule: Effective Performance Reviews For High-Performing Teams

Research reveals the ideal ratio of positive to negative feedback within high performing teams

Mar 20, 2025
Read article
Reflections
8 min read

What Makes a Great Engineering Manager?

People don't quit jobs, they quit bad managers. Here's what great engineering leadership actually looks like

Dec 8, 2024
Read article
Reflections
4 min read

It's More Fun to Be Competent

Once you're competent, everything changes. You stop second-guessing yourself. You stop panicking every time you encounter a new problem. And you start taking on bigger challenges with excitement rather than dread.

Sep 20, 2024
Read article
Reflections
4 min read

How to Launch Software Projects On Time and On Budget

Learn the art of scope management to keep your projects fixed in time and cost

Oct 7, 2024
Read article
Reflections
5 min read

When Should You Actually Worry About Tech Debt?

Technical debt isn't the monster under your bed, but it can become one if ignored too long.

Sep 12, 2024
Read article
Reflections
5 min read

Advice to New Engineering Managers

Tips for being an effective engineering leader and how to avoid common pitfalls

Feb 15, 2025
Read article

This article was originally published on https://www.trevorlasn.com/blog/a-company-is-not-a-family-its-a-sports-team. It was written by a human and polished using grammar tools for clarity.