Competition and Cooperation Are Not Opposites
We often talk about competition and cooperation as if they sit at opposite ends of a scale. A competitive system encourages people to pursue their own success; a cooperative system asks them to work toward a shared success. From a design perspective, however, this distinction is much less useful than it first appears. Many of the most interesting games are competitive precisely because players sometimes need one another, and many real-world systems fail because they assume that putting people on the same team automatically gives them the same interests.
The more useful question is not whether a system is competitive or cooperative, but how the goals of its participants relate to one another. Does my success require your failure? Can we both improve at the same time? Do I benefit when you succeed, even if I still want to outperform you? Is there a result that we both need before our individual achievements matter? Once we ask those questions, competition and cooperation stop looking like categories and start looking like outcomes of the goal structure we designed.
This matters well beyond games. Gamification systems, sales incentives, learning environments and organizational targets all define relationships between participants whether their designers intend to or not. When we choose what counts as success, we are also deciding when people have a reason to help one another, when they have a reason to withhold help, and when another person’s progress becomes a threat.
Not every competition is zero-sum
The term zero-sum describes a system in which one participant’s gain is matched by another participant’s loss. Poker is an obvious example: the chips one player wins come from the other players. Many sports have the same logic at the level of the result. One team receives the win because the other does not.
It is tempting to extend that logic to every competitive game. If only one player wins, then surely everyone must be fighting over the same fixed quantity of success. But that mixes up the final ranking with the system that produces it. In Catan, Splendor or 7 Wonders, my development does not usually require your development to move backward. I can build a stronger engine, produce more resources or gain points without taking those points away from you. We may still be competing for the final result, but much of the value inside the system is being created rather than transferred.
Catan makes the distinction particularly visible because players are rivals and trading partners at the same time. I want to reach ten points before you, but I may still want you to produce resources because your production creates trading opportunities for me. I may refuse to help the current leader while gladly making a mutually beneficial deal with someone else. Competition remains intact, yet the system repeatedly creates moments in which helping another player can also be the best way to help myself.
That produces a very different social experience from a system in which every advantage I gain must come directly at your expense. The design has not removed competition. It has changed the relationship between the competitors.
Shared goals, shared interests and shared rewards are different things
This distinction becomes clearer if we separate three ideas that are often treated as interchangeable. A shared goal means that several participants are trying to achieve the same defined result. A shared reward means that several participants receive value if a particular result occurs. A shared interest is looser: our goals may be completely different, but at this moment there is an outcome that benefits both of us.
Temporary alliances in games are built on shared interests. In Diplomacy, I do not need my neighbor to win. In fact, eventually I may need exactly the opposite. But if a third player is expanding rapidly between us, my neighbor and I suddenly have a reason to coordinate. A Game of Thrones: The Board Game creates similar situations through support in combat. Cosmic Encounter goes further by rewarding players for joining another player’s attack. The players retain individual victory conditions, but the mechanisms continually manufacture short-term reasons to cooperate.
This is important because cooperation does not require harmony. The two players do not need to become a team, share every objective or trust one another indefinitely. They only need enough overlap between their interests to make a particular cooperative action worthwhile.
For a designer, that opens a much richer space than simply deciding whether a game is competitive or cooperative. We can design systems in which interests overlap for one turn and diverge on the next, in which players need help from people they may later betray, or in which the strongest move is available only when two competitors find a reason to coordinate.
Sometimes individual success should depend on collective success
Semi-cooperative games use another structure. Instead of creating occasional overlap between otherwise separate interests, they place an individual objective inside a larger collective condition. A player may perform extremely well personally, but that performance matters only if the group first avoids a shared failure.
I use this structure in Alibi. Participants have personal goals and reasons to pursue their own interests, but the group also has to solve the murder. If the table fails at the central investigation, individual achievements lose much of their meaning. The players therefore cannot optimize only for themselves. Personal success exists inside a larger system that also has to survive.
Some competitive games create a similar effect without formally becoming semi-cooperative. Catan: Game of Thrones, for example, still allows an individual winner, but the players also have to protect the Wall. If the shared threat overwhelms them, the normal competition becomes irrelevant. Before the table can ask who performed best, it has to make sure there is still a game in which individual success can matter.
This structure is especially interesting for gamification because it gives us an alternative to two common incentive designs. Pure individual incentives can make colleagues treat one another as obstacles. Pure team incentives can weaken the connection between personal contribution and personal reward. A layered structure can preserve both: individual performance matters, but only inside a minimum level of collective success.
Goals design behavior between people
Imagine a sales team in which bonuses are based entirely on an individual leaderboard. If I improve your performance, I may make it harder for myself to finish above you. The organization can talk endlessly about teamwork, but the scoring system is quietly telling us that your success is my problem.
Now imagine the opposite system, in which everyone receives the same bonus whenever the department reaches a target. Cooperation becomes more rational, but the system can also weaken the relationship between individual effort and outcome. Someone who contributes very little may receive exactly the same reward as the person who carried the team.
A layered target creates a different relationship. The team must first reach a collective threshold, and only then do individual achievements determine additional rewards. A strong performer now has two reasons to care about a struggling colleague. They still want to perform well personally, but their personal result is worth less if the group fails. Helping another person is no longer merely an expression of goodwill; the structure has made that person’s progress relevant to their own success.
The same principle can appear in learning. If students are ranked only against one another, sharing knowledge can become strategically irrational. If the entire class receives recognition only for a group average, individual mastery may become less visible. But a system can combine personal competence with a shared threshold: each learner has their own progress, while some group achievements depend on enough members reaching a required level. The goal is not to force cooperation through slogans. It is to create circumstances in which cooperation makes sense.
Be careful what kind of competition you create
This does not mean that every gamified system should add a team target or that competition is inherently harmful. Competition can create focus, comparison, urgency and a clear standard of performance. The problem begins when we introduce competitive mechanics without examining what kind of relationship they create between participants.
A leaderboard is not merely a way to display scores. If positions are scarce, another person’s progress can reduce my status even when my own performance has not changed. A limited prize pool makes that relationship even stronger. By contrast, a system in which everyone can reach a meaningful achievement threshold allows participants to compare themselves while still benefiting from one another’s knowledge. Both systems contain competition, but they create very different incentives around helping, sharing and withholding information.
This is also why simply adding a cooperative task to an otherwise competitive system may not work. If the individual reward is much more valuable than the collective one, rational participants may sacrifice the group whenever the two goals conflict. If the collective condition dominates everything, the individual layer may become decorative. The relationship between goals has to be designed with the same care as the goals themselves.
Design the relationship, not just the reward
When we design a game, a learning system or a workplace incentive, we tend to focus on the participant and the reward: what do I want this person to do, and what will they receive for doing it? But in any multi-person system there is another question that is just as important: what does my success make you want to do?
If my progress automatically harms you, we have created one kind of relationship. If we can both progress independently, we have created another. If I need you to succeed up to a certain point before my own achievement becomes valuable, we have created a third. And if our interests overlap only temporarily, we may cooperate today while remaining competitors tomorrow.
Games make these structures unusually visible because their goals and rewards are explicit. That makes them useful models for gamification. They show us that competition and cooperation are not opposites that we choose between at the beginning of the design process. They can exist simultaneously, at different levels and at different moments, because both emerge from the same thing: the way we connect people’s goals.
When we design goals, we are also designing relationships between participants. The most interesting question is therefore not whether we want people to compete or cooperate. It is when, why and with whom the system gives them a reason to do each.