DICE 2026 briefing: Five conversations shaping gaming’s next chapter

D.I.C.E. Summit 2026 (“The Story Ahead”) lands in Las Vegas on February 10–12 and the timing feels unusually loaded for games. It’ll be my first DICE, and I’m going mainly to listen: what are leaders actually worried about, and what are they betting on next? I’m attending as Head of Client Partnerships – Americas at Streamline Studios, a co-development company with 25 years in the space.

Five conversations I expect to define the week

1) A room carrying scars and cautious optimism. The industry is still processing a historic layoff cycle, and that emotional reality will be present in every serious conversation. At the same time, demand signals haven’t disappeared — players are still showing up at scale. That tension (hurt + hope) will shape the tone of DICE.

2) AI: tool, threat, or both. AI won’t be one panel — it’ll be the subtext of almost every panel. The real debate isn’t “are you using it?” but “where does it help, where does it harm, and what rules are we willing to commit to?”

3) Co-development is becoming a default operating model. When internal headcount shrinks but roadmaps remain ambitious, partnerships move from “nice to have” to “how we ship.” From a co-dev lens, I expect more nuanced conversations about integration, accountability, and trust — not just cost.

4) Indie momentum is rewriting assumptions about where hits come from. Smaller teams keep proving that focus + craft can beat scale. Meanwhile, many big slates still lean heavily on sequels and proven IP. DICE will highlight that paradox.

5) Consolidation and ownership shifts will dominate the business track. M&A, private capital, and platform strategies continue to reshape incentives across the ecosystem.

DICE 2026 feels like an inflection point — not because anyone has the full answer, but because the contours of “what’s next” are becoming visible. If you’re attending DICE this year, I’d love to compare notes.

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *