When Everyone Wins but the Team Loses

I’ve been thinking a lot lately about what it means to win as a team.

Organizations are full of talented, ambitious people trying to do good work. We ask people to take ownership. Advocate for their customers. Deliver results. Hit their goals. Demonstrate impact. Push for what they believe is right.

Those are all things I want from the people I work with.

But there’s a tension we don’t talk about enough:

What happens when everyone is winning individually, but collectively we’re losing?

A product team delivers its roadmap on time—but creates something another team will eventually have to rebuild.

A function protects its standards—but makes it harder for the organization to deliver a coherent customer experience.

A leader successfully fights for resources their team needs—even though those resources might create greater impact somewhere else.

Someone swoops in and saves the day and gets recognized for it, while someone else quietly prevented three fires from happening in the first place.

Everyone can point to their contribution. Everyone did their job. Everyone might even have a green dashboard.

And somehow, the organization still lost.

The Problem With Local Optimization

There’s a concept in systems thinking called local optimization.

Simply put, improving one part of a system doesn’t necessarily improve the whole system. In fact, sometimes making one part better makes the overall system worse.

Organizations do this all the time.

We create goals by function, team, product, portfolio, or individual. Then we ask people to take accountability for achieving them. Naturally, they do.

The problem comes when those goals collide.

The best decision for Product may not be the best decision for Engineering. The best decision for one product may create unnecessary complexity for another. The fastest way to launch something may create long-term costs for the platform. The thing that improves one metric may hurt the customer somewhere else in their journey.

None of that means the individual goals are wrong.

It means the system is bigger than any one goal.

And someone has to be willing to see the whole.

I Don’t Want Less Ambition

This is where I think conversations about teamwork sometimes go wrong.

The answer isn’t to stop competing.

I want people who care deeply about their craft. I want people who have strong opinions. I want someone to walk into a room believing passionately that their idea is the right one—and be able to explain why. I want people who want to win.

Healthy competition can raise the bar. Ambition creates momentum. Pride in our work pushes us toward excellence.

But there’s a difference between wanting to win and needing your idea to win.

There’s a difference between advocating fiercely for an outcome and protecting your territory.

And there’s a difference between being accountable for your part of the system and optimizing your part at the expense of everything around it.

Some of the most mature leadership I’ve seen happens in a much quieter moment:

My idea is good. Their idea gets us farther.

Or:

This may make my team’s metric look worse, but it’s the right decision for the customer.

Or even:

We could do this ourselves, but the organization will be better off if we build it together.

Those decisions rarely create heroes. But they create better organizations.

We Get the Culture We Reward

It’s easy to tell people to think beyond themselves.

Think enterprise. Collaborate. Break down silos. Be one team.

But people pay far more attention to what an organization does than what it says.

If we tell people collaboration matters but promote the person who consistently gets results by steamrolling everyone around them, we’ve communicated what matters.

If we say we’re one team but celebrate individual teams for shipping regardless of what their decisions create downstream, we’ve communicated what matters.

If we ask someone to sacrifice their own metric for a better company outcome and then penalize them because their metric didn’t turn green, we’ve communicated what matters.

If the hero who saves the project gets more recognition than the person who quietly built the conditions that kept another project from needing to be saved, we’ve communicated what matters.

Culture follows what organizations repeatedly reward, measure, celebrate, and tolerate.

That’s why rebuilding collective purpose can’t simply be a communication exercise. It has to become part of how the organization operates.

Leaders Have to Make the Whole Visible

It’s difficult to optimize for a system you can’t see.

One of our responsibilities as leaders is to help people understand the larger system around their work.

Where are we trying to go? Why does it matter? What outcomes are we collectively responsible for? Where are the dependencies? What happens downstream when we make this decision upstream? What does the customer experience look like across our organizational boundaries?

And, perhaps most importantly: What are we willing to trade to get there?

Because alignment isn’t everyone agreeing.

Alignment is people understanding the destination well enough to make intelligent tradeoffs along the way.

Sometimes that means pushing harder for your idea. Sometimes it means challenging the group when everyone else is heading in the wrong direction. Sometimes it means disagreeing and committing. And sometimes it means willingly giving something up.

That last one may be the hardest.

What Are We Actually Celebrating?

I think leaders should occasionally look around their organization and ask a few uncomfortable questions.

Are we measuring the outcome—or simply each person’s contribution to it?

Do people understand the shared outcome they’re collectively responsible for?

Who gets recognized here? The person who had the idea? The team that launched the feature? The person who rescued the project?

What about the person who helped another team succeed? The team that chose not to build something because another solution already existed? The leader who gave up resources because another part of the organization needed them more? The person who changed their mind when the evidence changed?

Those behaviors tell us something important about collective success. We should celebrate them, too.

And we should look just as closely at what we tolerate.

A brilliant high performer who consistently damages collaboration teaches an organization something about what we really value. So does the leader who protects their territory. So does the team that repeatedly optimizes its own experience while pushing complexity somewhere else.

Every time we reward or tolerate those behaviors, we’re designing our culture.

Remember What We’re Trying to Win

I don’t want teams with less ambition.

I want people who care deeply about their craft, advocate fiercely for their customers, challenge assumptions, push one another, and take pride in doing exceptional work.

But I also want us to remember what we’re trying to win.

The highest-performing team isn’t necessarily the one with the most individual victories.

It’s the one where people understand when to lead, when to follow, when to challenge, when to compromise—and occasionally, when to give up a win of their own so something bigger can succeed.

That kind of collective purpose doesn’t happen because we put One Team on a slide.

We build it through the choices we make every day: what we measure, what we reward, what we celebrate, and what we’re willing to tolerate.

Individual excellence can take us a long way.

But there are places we can only reach together.