I have been watching a lot of the World Cup 2026, not all of it (there are far too many games for that), but many of them when time allows. The thing that keeps pulling my attention is not the scoreline. It is that the team conversation looks completely different depending on which squad is on the pitch. Some teams talk like a collection of individuals who happen to wear the same shirt. Others talk like a single organism. Watching that difference play out, game after game, is what I went looking to explain: what actually makes one squad cohere and another one fall apart, and why the answer keeps rhyming with the engineering teams I have worked on.

That question is the quest of this post, so let me name the angle up front, because it is the thing I only understood by writing my way to it. Soccer is a one-dimensional model of a team: one field, eleven positions, one ball, one clock running forward at the same rate for everyone. Engineering teams are not one-dimensional. They are played across many fields at once (one person's field is the language, another's is the network, another's is the deployment pipeline) and across time, where the ball you pass may not be received until six months from now. So the plan here is to take the clean one-dimensional intuition soccer hands us, stretch it onto the multi-dimensional reality of engineering, and see what survives the stretch. The part that survives is the "why" I am after.

Go back to Messi, or Maradona before him. Both make the same thing obvious: you can have a star team, but if you do not build a strategy around that team, cohesion is very hard to come by. And you can have a star player, but if you do not build a strategy around that star player, cohesion is just as hard. A star player on its own is not a plan. It really comes down to whether the team gives its players chances that do not get wasted, and I think that is the actual difference between a regular player and a star player.

It is not a good idea to have everybody be a forward. It is not a good idea to have everyone standing there to be a shooter. If you tried to build a team that way, there would be no one to pass the ball to you, no one to defend, no one to push the play forward. So it is a balance, and it is a team effort. Even when you have a genuine star player, the strategy still has to change around them, because at the end of the day it is about winning, not about the star player. Having a star player is good. Ideally you have more than one, so you can balance them and rotate them.

What Actually Makes a Star Player

Here is my definition. A star player is someone who, when given the chance, has a high percentage of taking advantage of it. They convert. They do not waste opportunities, and the chances they create are higher quality than normal. That is it. It is not about flash. It is about recognizing a chance, executing on it, and doing it more reliably than the people around them.

I have watched plenty of moments where a beautiful pass gets played through and no one is there to receive it. That is a miss, and it is a miss the whole team owns, not just the passer. I have also watched the rarer thing: a player who makes their own luck, who manufactures the chance out of almost nothing and then finishes it. That is uncommon, and it is exactly the quality worth prizing. It is recognizing the chance, going full Quest Engine on it, and executing on the opportunity. It sounds like a cliché, but it really is about honoring the opportunity, respecting it, and acting accordingly. In the Quest Engine terms I keep coming back to, the star player is the one whose searching (seeing the chance before anyone else) and being driven (committing to it without hesitation) are both sharp at the same instant.

This is the same three-term dynamic I wrote about in Timing, Momentum, and Resonance. The chance is the timing (the window the world opens, which the player does not control). The conversion is the momentum (the sustained force the player brings, which they do control). And the pass actually being received is the resonance (the coupling between the player and their teammates, which they can only influence). A star player is the one who couples all three at once. That beautiful pass with no one there to receive it is not a timing failure and not a momentum failure. It is off-resonance: the force was applied but never coupled. And the pass that arrives six months too early at work (the proposal the team finally asks for long after you made it) is the same phase mismatch, right frequency, wrong moment. The miss belongs to the whole team because resonance requires two oscillators, never one.

The same is true in engineering. A star engineer is not the person who talks the most or touches the most code. It is the person who, handed an ambiguous chance, recognizes it, sizes it correctly, and converts it at a higher rate than the people around them. And just like in soccer, a chance created with no one positioned to receive it is still a miss.

The Single Point of Failure

Building your entire strategy around one person is not the best strategy, and the reason is boringly practical: that person is going to get sick. That person is going to need to step away. That person can leave. When you have built everything around a single hero, the moment they are gone the team is left with a structure where only one person was ever able to make progress.

It gets worse when the roles pile up on the same individual. When your top scorer is also the captain, that can quietly become a problem. As a captain you often do not want to, or need to, take every shot yourself. You want the team to succeed. Being the top star player should not automatically make you the captain, even though the two so often land on the same person. The management structure and the scoring structure are not a one-to-one mapping, and they should not be. Forcing them to line up just means you are trying to make one routine do two jobs, and neither gets done well.

I do not want to pretend there is no value here. There is real value in having a single point of failure who is the person that scores the most goals, for a short and fairly certain stretch of time. Sometimes you do need that. But it is not a viable long-term solution. The person leaves, and the whole thing that was built around them collapses. So if you are going to lean on a star player, the way to make it resilient is to build in a way to rotate that star-player role. The star-player role has to be able to move between people, or it becomes the exact fragility you were trying to avoid.

Engineering has all the same failure modes. The teammate who is the only one who understands the deployment pipeline, or the one service, or the one gnarly subsystem, is a single point of failure wearing a cape. It feels great right up until they take a vacation. And stacking captain-and-top-scorer onto one person (the tech lead who is also the highest-output individual contributor and also the only on-call escalation) is the same mistake soccer teams make when they pin everything on one number nine.

Many Star Players, Across Many Planes

The solution, at least in the engineering world, is that you need multiple star players, and you need to be able to develop multiple star players who are actually happy being on the same team. There is no fighting over the ball, no fighting the bell curve. There is no reason to fight the bell curve at all. But the average of the curve needs to be higher. You use everyone's qualities to the max, in whatever way makes the whole team better, you balance people across positions, and then you rotate them in and out of the spots that are hard to sustain. Offense versus defense is the obvious one: those are different kinds of exhausting, and nobody holds up forever in either without a break. Rotating star players like this is how a team keeps its momentum up without burning down its mass: you sustain velocity across a whole season instead of spending one player's capability all at once.

This is where the stretch from one dimension to many finally pays off. On a soccer pitch there is a single field, so "star player" sounds like a single title there can only be one of. Engineering is not played on one field. It is played on many at once, and each one has its own game with its own rules. In any given timeslot one person is the star on the language plane (the one who can see through a type system or a memory model faster than anyone), another is the star on the networking plane, another owns the deployment plane, another the gnarly-subsystem plane. These are not the same skill wearing different jerseys. They are genuinely different games being played on the same team, at the same time, and every one of them can have its own number nine. So the question stops being "who is the star" and becomes "does every plane that matters have someone who converts on it, and can that role move when the plane heats up." You can have many star players in many places instead of one hero and ten supporting cast members, because the field itself is plural.

Once you see the planes, a quieter truth shows up: the most valuable star player is often not the deepest specialist on any single plane. It is the versatile one, the generalist, the player who can move between planes without the whole play collapsing. A specialist is a star only while the game stays on their field. A generalist is the person who can drop into the language plane today, the networking plane tomorrow, and the coordination-across-teams plane the day after, and be a real threat on each. In a one-dimensional game versatility looks like a compromise (a jack of all trades, master of none). In a multi-dimensional game it is the rarest and most load-bearing kind of star, because they are the ones who keep the separate fields stitched into a single team instead of a set of silos that happen to share a repository.

And there is one more field that never shows up on a soccer diagram: time. In engineering you are not only passing the ball across space to a teammate standing there now. You are kicking it six months into the future, to a receiver who is not there to receive it yet (the proposal nobody is ready for, the abstraction nobody needs until the quarter it suddenly saves everyone). Landing that pass is not luck. It takes the same skill and coordination as a perfectly weighted through-ball, except the hard part is the timing across months instead of meters. The star players who can do that (aim the ball at where the team will be, not where it is) are playing a dimension the one-dimensional model cannot even draw.

I want to be careful here, because I am advocating for star players and I would like to think I am one of them. The point is not to flatten everyone into interchangeable parts. The point is the opposite: work is not the simple game with simple rules, the dynamics are much more complicated than eleven positions on a field, and that complexity is a gift. It is exactly what lets a team have many star players in many places, each one a genuine star on their own plane and across their own slice of time, mostly working with each other rather than against each other.

So the "why" I went looking for, the thing that separates the squad that talks like an organism from the one that talks like strangers in matching shirts, is this. A single star who scores all the goals is a one-dimensional answer to a multi-dimensional game, and it fails the moment that person is sick, on vacation, or gone. The resilient answer is a team that recognizes stardom is local (every plane and every timeslot can have its own), that prizes the versatile generalists who move between planes and pass the ball into the future, and that keeps the star-player role rotating so no single absence ever ends the season. That is what lets a team gel, and it is the pattern I keep landing on in soccer and in engineering both: not one hero on one field, but many stars across many planes, coordinating across time.

This one started as a set of notes scribbled during World Cup 2026 games and turned into another way of looking at the Quest Engine. It even followed the Quest Engine's own arc to get here: I went exploring by watching squad after squad and searching for what made some of them cohere, I executed on the idea by pinning down what a star player actually is (recognize the chance, convert it, own the miss when the receiver is not there), and then I reflected back to answer the why, which turned the single-star intuition into a multi-dimensional, across-time one. The star player is the person whose searching and driving line up on the opportunity, and a resilient team is one that renews by developing and rotating that capability across many planes instead of hoarding it in one place. The chance-and-conversion pattern is the soccer version of Timing, Momentum, and Resonance, and for more on how teams take ownership of their own identity, see Team Identity Ownership.