What Overwatch's Battle Pass redesign gets right about progression

The old system was a single queue

The previous Battle Pass was one 100-tier bar. You earned XP, the bar filled, you unlocked the next reward in a fixed order. It's the simplest progression model there is: one track, one direction, no decisions required from the player. You can build it in an afternoon, explain it in one sentence, and it never confuses anyone.

That simplicity is also its failure mode. A single long bar tells the user two things whether it means to or not: this will take a while, and you have no say in how. There's no way to work on the reward you actually want first. There's no way to see "almost there" on more than one front at a time. Progress becomes something that happens to you on a schedule the system set, not something you're steering.

Earlier in 2026, Blizzard had already reworked most of the game's UI: a new 3D hero lobby, a notification hub, faster global navigation, a revamped hero gallery and social panel. The Battle Pass was left alone in that pass. It kept being the one place in the game where progress still felt imposed rather than chosen, sitting there as unfinished business while everything around it got faster and more legible.

What changed

The new structure breaks the single bar into separate tracks, each shown as an 8 to 10 tier "page." Players can navigate between them and change which track is active at any time. Same total content as before, restructured into units small enough to see the end of, with the order left up to the player instead of the system.

They paired this with a "Tier Hack": at the end of a track, instead of a single fixed reward, players can swap it for another legendary skin from a curated seasonal list. It's a small mechanic on its own, but it follows the exact same logic as the restructuring above it. Replace one more forced outcome with a moment of actual choice, even a bounded one.

Neither change adds new content. Nothing was added to the pass, nothing was made easier to earn. What changed is entirely structural: how the same total amount of progress is chunked, sequenced, and handed control of back to the person doing the work.

Why this is a design decision, not a game decision

None of this is specific to Battle Passes, or to games. Any product with a mandatory sequence, onboarding flows, courses, setup wizards, compliance checklists, insurance application funnels, is making the same bet the old system made: that completion matters more than agency.

That bet is sometimes correct. Sequences exist because order genuinely matters in some flows. You can't configure step 4 before step 3 supplies the data it needs, and pretending otherwise just moves the confusion to a worse place, a broken step 4 instead of a clear "finish step 3 first." Forced order that reflects a real dependency should stay forced. Hiding that dependency behind a false sense of freedom is worse than a straight linear bar.

But a lot of forced sequence isn't structural. It's just how the first version got built, back when the team needed to ship something and one track was the fastest path to a working product. It survives because nobody revisits it once it's live, and because "it works" quietly becomes the bar instead of "it works well for the person going through it."

The cost side nobody puts in the pitch

It's worth being honest about why this took until now instead of shipping alongside the rest of the UI overhaul in February. Modular progression is a heavier build than a linear bar, and the extra weight is mostly invisible until you're the one building it.

You need clear wayfinding between sections, so switching tracks doesn't feel like getting lost. You need a way to represent overall progress without a single continuous bar to point at, some aggregate view that still answers "how far along am I, really" without lying by oversimplifying. You need the individual track UI to hold up whether someone lands on tier 1 or tier 9 of it, and you need the reward-swap mechanic to have real constraints so "choice" doesn't become "everyone picks the same optimal path and the variety was theater."

None of that shows up in a before/after screenshot. It shows up in QA time, in edge cases, in the extra design review pass for "what does this look like at every possible state," and that's exactly why teams under time pressure default back to the one linear bar. It's not that nobody thinks of the modular version. It's that the modular version is the one that gets cut when the deadline gets tight, because the linear one is the one that's guaranteed to ship correctly.

What I'd take from this

If you're looking at a flow in your own product that forces a sequence, the useful question isn't "should this be linear or modular." It's narrower than that: which parts of this sequence are real dependencies, and which parts are just the order the first version happened to ship in. Everything in the second category is a candidate for the same move Overwatch just made, not because modular is inherently better, but because a leftover decision dressed up as a requirement is the cheapest kind of friction to remove once you actually look for it.

The UI polish, the new visual effects and animated backgrounds, is the easy 20% and the part that gets all the screenshots. The expensive 80% is the information architecture underneath it: the wayfinding, the aggregate progress view, the constraints on the reward swap. That's the difference between a system that processes people through a sequence and one that lets them navigate it, and it's very rarely the part anyone budgets time for.