Do you prefer when a dev creates a sequel or an entirely new world?

The #PCGamingShow Tokyo Direct is just a few weeks away, but don’t forget this gem from our last show!

What was your favourite game from our June show?

#SignetCity #PC #RPG

Do you prefer when a dev creates a sequel or an entirely new world?

In the lifecycle of any software product, teams frequently confront a pivotal question: should a developer extend the existing universe with a sequel, or should they venture into an entirely new world? The answer isn’t binary; it hinges on user expectations, product strategy, and the organizational capacity to deliver value that resonates. The following considerations can help teams decide which direction to pursue and how to execute with clarity and impact.

Audience expectations and brand continuity A sequel leverages familiarity. Users arrive with a set of mental models, workflows, and rituals built around the current experience. Delivering a sequel that preserves core interactions while incrementally adding depth can deepen engagement, foster trust, and reduce onboarding friction. However, audiences can grow tired if sequels merely repeat the same patterns without meaningful evolution. When brand signals, documentation, and support artifacts consistently highlight continuity, a sequel can strengthen loyalty while offering fresh capabilities.

Exploration, risk, and opportunity in new worlds Launching a new world invites curiosity and can attract new user segments. It’s a chance to redefine the value proposition, experiment with different interaction paradigms, and address problems the previous edition could not. The trade-off is risk: users may hesitate to invest time and mental effort into a space that isn’t yet established in their workflows. A new world benefits from a crisp, targeted problem statement, rapid feedback loops, and a minimal viable experience that demonstrates clarity of purpose.

Value delivery and measurable impact Regardless of direction, value should be measurable in near-term business and user-centric metrics. Sequel projects can demonstrate compound value through enhanced compatibility, backward-compatible improvements, and deeper integrations with existing ecosystems. New worlds should showcase a compelling use case, a clear differentiation from the prior version, and tangible outcomes—such as reduced task time, increased adoption, or expanded applicability to new domains.

Product strategy alignment – If the goal is to deepen existing relationships, preserve core workflows, and deliver additive capabilities without displacing current users, a sequel is often the prudent path. – If the objective is to break into new markets, attract different personas, or reinvent the user experience to solve problems the old version didn’t address, a new world can create strategic leverage.

Engineering and delivery considerations Sequels typically offer lower risk in architecture because the underlying platform remains familiar. They enable incremental refactors, feature flags, and gradual migration strategies that minimize disruption. New worlds demand investment in exploratory design, architecture that supports future evolution, and robust strategies for data migration, integration, and user onboarding. Regardless of choice, establish strong governance: a clear product brief, explicit success metrics, and a phased roadmap that includes checkpoints for user feedback and pivot opportunities.

User onboarding and learning curves A sequel can capitalize on prior learning; the learning curve is often shorter, and help resources can reference established patterns. A new world requires thoughtful onboarding, storytelling, and guided explorations that help users discover the novel affordances without overwhelming them. In both cases, invest in documentation, in-product guidance, and community channels that facilitate feedback and knowledge sharing.

Culture and organizational impact Sequel projects tend to consolidate momentum within an existing team and ecosystem, reinforcing established practices. New worlds can catalyze cross-functional collaboration, attract diverse skills, and refresh motivation but may demand more deliberate change management. Successful outcomes align with the organization’s capacity to sustain momentum, iterate quickly, and maintain quality across iterations.

Conclusion Whether you favor a sequel or a new world, the decision should be driven by user value, market signals, and the organization’s ability to deliver with confidence. A sequenced approach often resonates with long-time users who crave depth and continuity, while a new world can energize the market and unlock untapped potential. The most durable choice is a clear narrative: articulate the problem you’re solving, the desired impact on users’ workflows, and a pragmatic plan for delivering that impact with rigor and transparency.