The sports analogy is often weak — "treat the team like a sports team" is the kind of advice that says nothing. Football is more useful when you stop using it as a vibe and start looking at the specific things good football teams actually do.
A few patterns that transfer cleanly to product leadership, mostly because the underlying problem is the same: how do you get a group of skilled individuals to perform together, under pressure, against a moving opponent?
The system makes the player, more than the player makes the system
Most football fans overweight the star. The team won because the striker scored. The team lost because the goalkeeper made a mistake. Those things matter. They're also less explanatory than the system the players were operating inside.
A great striker in a poorly-organised team produces fewer goals than a decent striker in a well-organised one. The chances they get, the protection they have, the context they're playing in — all of it is set by the system. The same player can score 30 goals at one club and 12 at another.
Same in product. A great PM in a chaotic team produces less than a decent PM in a well-organised one. The roadmap they get to work with, the engineering capacity available, the support of leadership, the clarity of the strategy — all of it shapes what an individual can produce. Individual brilliance helps. The system is what produces consistent output.
The leadership move that follows: spend more time on the system than on the individuals. Hire well, but invest more in the conditions the team operates inside. The compounding return is much higher there.
Pressure exposes preparation
The teams that play well in big moments aren't the ones that get clutch. They're the ones that prepared so thoroughly that big moments feel like normal moments. The match-winning play in the 89th minute is usually a play they ran a hundred times in training.
In product, the equivalent is what happens when a team faces an unexpected event — a competitor launches, a key customer threatens to churn, a major bug ships. The teams that handle these well aren't the ones that improvise brilliantly. They're the ones whose default operating habits already cover most of the response.
The team that knows how it makes decisions under normal pressure handles unusual pressure with the same playbook. The team that lacks operating habits scrambles, miscommunicates, and produces a worse outcome than the actual situation required.
The leadership job: build the operating habits during calm. Deploy them during pressure. Don't try to develop them while the building is on fire.
The best coaches don't play
A football coach who tries to do the players' work has lost the room. The coach can't be on the pitch. Their job is to set the system, prepare the team, and make a few critical calls during the match — a substitution, a tactical shift, a pep talk at half time. Most of the match is run by the players.
Same shape in product. The leader can't write all the specs, run all the discovery, and make all the decisions. The PMs and engineers are on the pitch. The leader's job is the system, the preparation, and the few calls that genuinely belong to the leadership level. Trying to do more than that is interference.
The best leaders, like the best coaches, know which moments call for them and which don't. They get involved sparingly and with high impact, and stay out of the way most of the time.
Substitutions matter
In football, the manager has a small number of substitutions per match. Each one is a high-stakes decision — wrong substitution can lose the game, right one can win it. So managers think hard about timing, who to swap in, what message it sends.
The product analogue: people decisions are the highest-leverage decisions a leader makes. Who to hire. Who to promote. Who to move teams. Who to part ways with. Each of these has more impact on outcomes than most operational calls. They're also the ones leaders most often delay, second-guess, or under-invest in.
A leader who's getting people decisions right will tolerate a lot of operational mediocrity and still produce good outcomes. A leader who's getting them wrong will be impeccable on operations and still struggle.
Loss recovery is its own skill
Football teams lose. The good ones lose less often, but everyone loses sometimes. What separates good from great is what happens in the week after a loss.
Bad teams blame, fragment, and concede the next match too. Good teams diagnose, regroup, and come back sharper. The recovery is a real, practiced skill. The squad doesn't accidentally come back stronger — the manager and the coaching staff do specific things to make that happen.
Product equivalents: the failed launch, the missed quarter, the project that didn't ship. Bad teams blame. Good teams diagnose, learn, and ship the next one better. The diagnosis-and-regroup is a leadership skill, and it's most visible immediately after something has gone wrong.
The leader's main job in the week after a loss is to keep the team intact and pointed forward. That's harder than it sounds and matters more than most other leadership moves.
The shift
Football is useful as an analogy when you look at what the best managers actually do — build the system, prepare the team, deploy substitutions thoughtfully, manage the recovery from losses, and otherwise stay off the pitch.
Most of those translate directly to product leadership. None of them require the full sports-vibes treatment.
The system makes the player. Pressure exposes preparation. The coach doesn't play. Substitutions matter. Recovery is its own skill.
Run those well and the team produces over the long arc, regardless of any one match.
If you're working out the move from PM to product leader, the system-vs-player frame is useful. And building a high-performing team is mostly a coaching job — same patterns, different sport.