A team is not one strength, it is several
In games played across multiple maps, a team does not have a single win chance against an opponent. It has a separate chance on each map, shaped by layouts, preferred strategies and how much practice has gone into each one. The map pool is the set of maps that can appear in a series, and a team’s results are best thought of as a profile across that pool.
This is why two teams with similar overall records can behave quite differently in a series. One may be solid everywhere, and the other may be excellent on a few maps and weak on the rest. Their overall averages could match while their series outcomes do not.
A simple three-map illustration
Suppose, purely for illustration, that Team A has these chances against Team B:
| Map | Team A win chance |
|---|---|
| Map 1 | 60% |
| Map 2 | 50% |
| Map 3 | 40% |
The simple average across the three is (60 + 50 + 40) / 3 = 50%, so on paper the matchup looks even. In practice it is not decided by the average, because the maps actually played are chosen by the teams. If Team A can steer the series toward Map 1 and Team B toward Map 3, each side is trying to play where its own edge is largest.
If the series were played only on Map 1, Team A would be a favourite. If it were played only on Map 3, Team B would be. The real result depends on the process that decides the maps, which is why the veto system is part of the analysis rather than a side detail.
Bans, picks and who controls the pool
Many competitive formats use a pick and ban process: teams alternate removing maps, then picking those they want to play. The details differ between games and events, but the effect is similar. A team can protect a strong map by picking it, and avoid a weak one by banning it.
A few consequences follow.
- Depth matters. A team that is competent on every map has fewer maps to ban and fewer weaknesses to hide. A narrow team can be strong on its best maps and then forced to play something uncomfortable.
- Order matters. The side that bans or picks first, or that chooses a deciding map, may have more control, depending on the format.
- Bans reveal preferences. What a team removes, and what it picks, is itself information that opponents use.
The same logic appears in other competitive settings, such as character selection in fighting games, where character counterpicks let a player respond to the previous game. The main difference is that map choices are usually fixed in advance rather than adjusted game to game.
Reading map win rates carefully
A map win rate is easy to compute and easy to misread. Three points apply.
Small samples. A team that has played a map four times and won three has a 75% record, but that is weak evidence of strength. With only a few games, results of that size are common even between evenly matched sides. Without a larger sample, it is safer to blend such figures with the team’s overall record rather than trusting the raw map number.
Opponent quality. Winning a map often against weaker teams says less than winning it a few times against strong ones. A map record should be weighed against who the team played.
Staleness. Patches, map reworks and roster changes can make older results less relevant. A record from a different version of the game, or with different players, may describe a different team.
This is one reason studying recent professional matches carefully, and keeping an eye on how long ago each result occurred, is better than leaning on all-time numbers.
From map chances to series chances
Once each map has an estimated chance, the series result can be built up much like any other. For a best-of-three played on Maps 1, 2 and 3 above, Team A’s chance of winning a map is 60%, 50% and 40% in order. The calculation needs each combination of results, and the length of the series determines how much the weaker maps matter.
In a short series, a team may only play two or three maps, so a strong specialist map can make a large difference, and a weak one may never come up if it is banned. In a longer series, more of the pool is exposed, and a team’s depth is tested more fully. This is related to how series length changes the effect of a per-game edge in general.
Practical caveats
- Map strength is partly a matter of preparation, so it can change quickly when a team decides to practise a weak map.
- Teams sometimes hold back their best strategies for later in an event, which makes earlier map records a poor guide.
- Win rates on a map can be inflated if a team usually picks it only when it already expects to win.
A map pool view is a helpful lens on why results vary between opponents, but it is a model, not a rule. It works best as a way to ask which maps each side wants to play, and how likely it is that the veto process gives them those maps. Outcomes will still contain a lot of uncertainty from game to game.