What makes a co-op squad an economy?

Finite ammo, revives, information and time are shared and competing. Teams that perform well have an implicit rule for who receives the scarce resource, rather than resolving it case by case mid-fight.

Should the lowest-health player always get the heal?

Usually not. Give the resource to the player whose role is hardest to replace in the next two minutes. A low-health player who is out of position cannot convert that heal into progress.

Why is information treated as a currency?

A single accurate call-out changes several players' decisions at once, often more than one extra hit would. Silent teams leak the cheapest and most valuable resource they have.

When does splitting up stop being efficient?

In scaling games like Risk of Rain 2, once spawn rate outpaces individual clear speed. Good teams regroup at a defined trigger, such as the second or third teleporter, rather than after a death.

How does this apply to vehicle combat games?

A resource spent on repair or reload is not available for repositioning, so winning a duel while ending out of position is a bad trade even when the scoreboard looks good.

Why do these lessons transfer to an office team?

The structure is the same: scarce context, a shared deadline and one working build. Naming the scarce thing before allocating it, and agreeing the switch trigger in advance, works in both settings.

The economy of a squad: co-op lessons that work at the office too

Well-made co-op is an organisation class disguised as fun. After a thousand hours in four-player squads, the patterns separating clean missions from disasters are the same ones from any small team.

Lesson one: complete roles beat overlapping roles. A squad of four flexible players loses to four specialists who trust each other. Overlap creates dispute; gaps create blame. The ideal design covers everything without duplicating.

Lesson two: communicate state, not instructions. 'Out of ammo, reloading behind cover' beats 'get off that one'. Instructions try to command the other player; state lets everyone decide with the same information. Teams trading state decide faster.

Lesson three: the plan includes the exit. Missions that only plan the advance die on the way back. Every objective needs an agreed exit criterion - time, resource or partial success.

Lesson four: review the loss together, briefly. Five minutes of 'what killed the mission' beats an hour of blame. The answer is almost always a state nobody communicated.

None of this requires a game. But a well-chosen game trains all of it in thirty-minute evenings - and Deep Rock Galactic remains the best team simulator with dwarves and mining.

A squad is an economy before it is a team

Every co-op game quietly runs a small economy: finite ammo, finite revives, finite attention, and a shared clock. Teams that play well are not necessarily the ones with the best aim; they are the ones who have an implicit rule for who gets the scarce thing. Once you see it, the same rule set explains Deep Rock Galactic, Monster Hunter Wilds, Sea of Thieves and a War Thunder wing.

Four currencies worth tracking

Consumables. Ammo, heals, nitra, potions. The question is not "who needs it now" but "who converts it into the most progress before the next resupply".
Revive capacity. A downed teammate costs time, position and often a second player's safety. Deciding in advance whether to revive under fire prevents the mid-fight argument that loses both.
Information. In extraction shooters and tactical co-op, calling out one enemy position is worth more than landing one extra shot. Silence is a resource leak.
Time. Risk of Rain 2 makes this explicit: the difficulty scales with the clock, so a chest that costs forty seconds is a purchase, not a freebie.

A decision rule that survives most games

Give the scarce item to the player whose role is hardest to replace in the next two minutes, not the player who is lowest. In Deep Rock Galactic that is usually the Gunner during a swarm or the Scout before a traversal; in Monster Hunter it is whoever is closest to completing a break that ends the phase; in Sea of Thieves it is the helmsman during a chase. "Lowest health gets the heal" is intuitive and often wrong, because a recovering player who is out of position cannot convert the resource into progress.

The second half of the rule: announce the trade. A ten-word call — "Scout takes nitra, Gunner holds shield" — removes the ambiguity that costs more time than the item is worth.

How scaling changes the maths

In Risk of Rain 2 and similar scaling games, the economy inverts. Early on, splitting up to farm is correct because each player generates more than the difficulty rises. Later, the same split is a loss, because the spawn rate outpaces individual clear speed and a lone death cascades. Good teams switch from gathering to grouping at a defined trigger, usually the second or third stage teleporter, rather than when someone happens to die.

War Thunder and other vehicle games add a different twist: a resource spent on a repair or a reload is not available for repositioning, and a player who wins a duel but ends up out of position has made a bad trade even though the scoreboard disagrees.

Carrying it into a real project team

The reason these lessons transfer to an office is that the structure is identical. One person holding context, another holding the deadline, and a third holding the only working build is a squad economy. The useful habit is to name the scarce thing out loud before allocating it, and to decide the trigger for switching strategy before the failure forces you to.