Create one squad.
Choose players across the tournament within the credit budget and team rules.
DREAM11 / MANAGER MODE
Bringing a more skill-led fantasy format to Dream11. One team to manage across a season, with planning, resource decisions and competition that unfolds over time.
MY ROLE
Product design
COLLABORATION
Product, Engineering, Content, Data,
Illustrations & Graphics
FIRST TOUR
1M+
Players in the first tour.
LOWER CHURN
23%
Lower likelihood of leaving regular Dream11 play before the tour ended.
THE EXPERIENCE
THE OPPORTUNITY
Dream11 wanted a more skill-led fantasy format: one squad, sustained planning, and decisions that matter across a season.
A continuing team also offered a reason to return throughout the tour. The design challenge was to explain that commitment without removing the strategy.
Connect today’s squad decisions to upcoming fixtures and the management of a continuing team.
Make a limited resource understandable while leaving the decision to use it—or save it—with the player.
Give managers a continuing competition in which their decisions and progress unfold across the season.
HOW THE FORMAT WORKS
Choose players across the tournament within the credit budget and team rules.
Use limited transfers and Boosters as fixtures change. Captain choices shape scoring.
The same team competes in weekly and season standings. Private Leagues bring friends into the competition.
THE DESIGN APPROACH
Familiar team-building controls did not guarantee understanding of a season-long format. Some participants expected only the next match’s squads; others assumed their team would stay unchanged throughout the tour.
My work centred on three decisions: organise around the continuing team, bring fixtures into selection, and explain what a transfer will count against the allowance.
The research describes the earlier experience; the screens show the latest iteration. Product-level outcomes are presented separately.
ONE CONNECTED JOURNEY
Select the squad → choose C/VC → save → arrive at team home.
An upcoming fixture or new match information gives the player a reason to reassess.
Return to home → choose replacements → review transfer usage → review C/VC & save.
DECISION 01 / STRUCTURE
I explored team-first and leagues-first structures. Leagues-first establishes the competition upfront; team-first starts with the squad the player will keep managing. I chose team-first, with Championship League entry following the first save.
Two ways to organise the same experience, considered across three player tasks.
Leagues firstEstablishes the competition before asking for a squad.
Team firstBegins with team building; league entry follows the first save.
Leagues firstThe competition remains the route into the team.
Team firstThe continuing squad provides the management starting point.
Leagues firstStandings are prominent within the competition structure.
Team firstWeekly and season standings need clear access from team home.
THE TRADEOFFTeam-first prioritises the recurring act of management. It also makes clear competition access from home essential.
DECISION 02 / SELECTION
Keep familiar team-building actions, but put the tournament schedule beside the choices. The task is to help players consider the team they need beyond the next match.
Earlier testing found that prizes could distract from the format explanation. The latest entry places “Create · Transfer · Boost” above rewards, introducing the ongoing activity before the first team is built.
Role tabs and credits keep selection familiar. Fixture filters and “plays next match” labels connect the wider player pool to the schedule. The tradeoff is density: fixture context must remain readable alongside player statistics.
The pitch view shows squad balance by role, with credits and resource totals still visible.
Captain and vice-captain choices get a dedicated step. Selected multipliers stay visible before Save.
The first save leads into the Championship League and back to team home. On a later visit, the next fixtures give the manager a reason to reconsider the squad.
Management comes before standings. Players motivated by rank and rewards still need clear access to competition below the team.
DECISION 03 / TRANSFERS
Earlier research found uncertainty about whether each confirmation counted as another transfer. The player needs to consider both the credit budget and the transfer allowance; the review must distinguish a squad change from a new deduction.
Reuse the familiar builder, with incoming and outgoing markers showing what changed. Credits answer whether the squad fits the budget; transfer usage shows how much of the allowance the change consumes.
Compare the proposed changes against the last-match team. “No new transfers deducted” separates changes without a new deduction from the total beside Confirm. Modification guidance explains that choices can be revisited before the next match.
The extra step earns its place by explaining the accounting—a generic confirmation would not address the earlier confusion.
Captain choices complete the updated squad. Unlimited captain changes stay distinct from the limited transfer allowance.
Keep the interaction familiar.
Make the consequences visible.
In the earlier June research, engaged managers commonly planned before lineups and revisited their choices as match information arrived. The connected journey gives that pattern a place: a continuing team to return to, fixture context to reconsider it, and a review of the proposed change.
THE OUTCOMES
Manager Mode introduced a different commitment to Dream11: one team to follow and manage across a tour. More than a million players took part in the first tour. The retention result connected it to the wider product: Manager Mode players were less likely to leave regular Dream11 play before the tour ended.
players in the first tour
More than one million players played Manager Mode in its first tour. Season-long team management reached a substantial audience from the outset, bringing the ambition for deeper fantasy play into use at scale.
The achievement was adoption of the format itself: players entered an experience built around a continuing team and decisions that extended beyond a single match.
lower likelihood of churn
before the tour ended
Players who played Manager Mode had a 23% lower chance of churning out of regular Dream11 play before the end of the tour, compared with players who did not play Manager Mode in the same LTV buckets.
This was the wider business significance. The retention comparison concerned continued participation in Dream11’s regular experience, connecting the season-long format to the goal of keeping players engaged across the tour.
Manager Mode players vs non-players · Same lifetime-value buckets · Churn from regular Dream11 play before tour end
23% is a relative reduction in churn likelihood, not a percentage-point change. This cohort comparison shows an association; it does not isolate the effect of individual design decisions.
The launch established reach.
The churn result connected that reach to retention.
Together, these outcomes made Manager Mode meaningful at two levels: a substantial audience for a more strategically demanding format, and lower observed churn in the broader Dream11 experience. These are product-level outcomes, separate from the later interface refinements shown in this case study.
THE DESIGN THREAD
The research highlighted a distinction that matters for a deeper format: knowing how to operate familiar controls is not the same as understanding how to play across a season. Team-first organisation gives the experience a continuing centre. Fixture information explains the planning horizon; transfer review explains the consequences of a change. The design responsibility is to make those rules legible while leaving the sporting judgement with the player.
Reduce the friction around the decision. Preserve the depth within it.