Playing the Infinite Game

Ask most executives what their company's goals are, and you'll hear some version of one of two answers: something about becoming the market leader, or something about maximizing value for shareholders. Both are variations on the same theme: win. Get to the top. Hit the number.

I understand the appeal. I like money as much as the next person. Also, these goals are concrete, measurable, and motivating in a simple way. That said, I've come to believe they're fundamentally the wrong goals - not because ambition is bad, but because optimizing for them produces exactly the wrong behavior at every level of the organization.

Two kinds of games

The philosopher and game theorist James Carse drew a useful distinction between two types of games: finite games, which are played to win, and infinite games, which are played to keep playing. Simon Sinek applied this framework to business in his work on leadership - his talk on the subject, and corresponding book, are well worth your time. It's one of my favorite subjects of Simon's, and it fundamentally reframed how I think about what we're actually trying to do as leaders.

A finite game company is running a race. There's a finish line, a scoreboard, and a winner (and losers). Every decision is evaluated against one question: does this move us closer to the goal? This produces a kind of organizational tunnel vision - short-term results get optimized at the expense of long-term health, quarterly numbers crowd out multi-year bets, and the people doing the work become inputs in a function rather than the whole point of the enterprise.

An infinite game company is focused on building something worth building. The goal isn't to win - it's to remain a great place to work, to keep doing meaningful work well, and to compound that over time. Decisions get evaluated against a different question: does this make us better in the long run? That question leads somewhere very different.

The trap hiding in plain sight

The finite game mindset is a trap that's surprisingly easy to fall into, even when you know better.

Becoming #1 is a seductive goal because it's clear. You can point to it. You can measure your distance from it. You can report progress against it each quarter. The trouble is that when winning becomes the organizing principle, you start making decisions that serve the metric rather than the mission. For example, you might cut investment in people development because it doesn't show up on the earnings call. You might deprioritize the technically correct decision in favor of the one that ships faster. You might very well optimize for the number instead of the thing the number was supposed to represent.

I've seen this play out in many organizations I've been part of. The teams most fixated on winning - on hitting the goal, beating the competitor, closing the quarter - were often the ones that made the most short-sighted decisions and had the most fragile products and cultures. If not managed carefully, the pressure to win has a way of crowding out the judgment that actually produces winning.

The employees-first corollary

One of the clearest expressions of the infinite game mindset is the employees-first principle, and it's one that tends to make finance-oriented executives uncomfortable until they think it through.

As a senior leader, your job is not to focus on your customers. It's to ensure that your people have what they need to focus on your customers. Customers are taken care of by employees who feel supported, trusted, invested in, and are clear on why their work matters. If the people doing the work are struggling, distracted, or disengaged, no amount of customer-centricity at the leadership level will fix it.

It strikes me that this is the logic behind servant leadership - the idea that the manager's job is fundamentally to remove blockers, not to direct traffic. A leader who is genuinely invested in their team's growth and well-being creates a downstream effect: the team delivers better work, which serves customers better, which produces the business outcomes that leaders often try to manufacture directly. Success, in this framing, is a byproduct. Not a goal.

What infinite game leadership looks like in practice

This type of leadership means making investments in people that won't show returns until next year, because the organization needs those returns, even if this quarter's review cycle doesn't reward them. It means choosing the architecturally sound approach over the one that ships faster, checks a box, and yet accumulates two years of debt. It means building a culture where transparency, long-term thinking, and doing the right thing are rewarded rather than quietly penalized whenever they slow something down.

It also means resisting the very natural impulse to treat your team's work as a means to an end. The engineers building your product aren't just shipping features - they're developing expertise, building judgment, and accumulating institutional knowledge that takes years to grow and surprisingly little time to lose. Treating that as a renewable resource is one of the most common and costly mistakes I've seen firsthand.

The right question to ask

I've started using a simple gut check when I'm navigating leadership decisions: am I doing this because it makes us better, or because it makes us look better right now?

Those two things are not always the same. And in my experience, the gap between them is where most of the important leadership choices actually live.

Play the infinite game. The score will take care of itself.

Epilogue - Many years ago, I worked under a CEO who set a very clear vision for our company. His stated objective was to make the company a great place for people to come and work every day, grow themselves through their careers, and provide for themselves and their families. Admittedly, I was younger and more foolish at the time, and hence thought that this was all, candidly, BS. With the ever-present benefit of hindsight, it turns out he was spot on.