There is a particular kind of optimism that appears whenever a company owns a successful piece of intellectual property. The assumption is that the hard part has already been solved. Players know the name. The audience exists. The world has history. All that remains is to put another game into production and wait for the familiar logo to do the heavy lifting.
Hasbro’s latest financial results are a useful reminder that game development doesn’t work like that.
As PC Gamer reports, Hasbro has recorded a $56 million non-cash impairment after cancelling several games that were expected to release in 2028 and beyond. Hasbro’s second-quarter results confirm that the charge is connected to a refocused digital-games portfolio.
That doesn’t mean someone accidentally fed $56 million into a shredder marked “videogames”. An impairment is an accounting recognition that assets are now worth less than the value previously recorded for them. In this case, those assets include capitalised development costs attached to projects that won’t reach the market.
But the accounting language shouldn’t hide the production reality. Years of work, knowledge, iteration, tools, prototypes, relationships, and creative decisions have been assigned a new value because the games they were building no longer fit the plan.
The Wrong Lesson From Baldur’s Gate 3
The strange part is that Hasbro is still pointing to Baldur’s Gate 3 as evidence of what its videogame business can become. That makes sense on the surface. The game was a critical and commercial success, strengthened the value of Dungeons & Dragons, and demonstrated that a deep, premium, single-player-focused RPG could attract a huge audience.
The danger is learning the wrong lesson from that success.
Baldur’s Gate 3 didn’t succeed simply because Baldur’s Gate is valuable IP. The name helped. The ruleset helped. Decades of Dungeons & Dragons history helped. But none of those things automatically produced the game players loved.
Larian brought years of experience building reactive role-playing games. It had developed a production culture around systemic problem-solving, dense authored content, player experimentation, and the terrifying idea that someone, somewhere, will absolutely try to solve your quest by throwing a boot at a chandelier.
The studio understood how to make rules, characters, environments, and consequences support one another. It also had time to test those relationships with players, discover where the experience broke, and iterate until the game felt coherent.
Hasbro owned the world. Larian built the capability.
Insider Tip: When analysing a successful game, separate what the licence contributed from what the development team learned how to do. Recognition can be inherited. Capability has to be built.
IP Creates Recognition, Not Capability
Strong IP can reduce the cost of explaining why a game matters. Players already recognise the setting, characters, factions, tone, and fantasy. That is enormously valuable in a market where discovery is brutal and attention is expensive.
Recognition, however, isn’t the same as production capability.
An IP can tell a team what world they’re working in. It can’t tell them how to structure a quest, how much systemic freedom the engine can support, how companions should respond to player behaviour, where scope needs to be cut, or how thousands of narrative and mechanical dependencies will survive contact with production.
Those answers live inside teams. They’re built through shipped games, failed prototypes, technical scars, design arguments, production compromises, and the suspiciously specific knowledge that one innocent-looking door can break forty-seven quests.
When a company treats IP as the strategy, it risks underestimating the people and conditions required to express that IP properly. The result may still look recognisable, but recognition alone won’t make the experience meaningful.
IP Value vs Production Capability
| What Strong IP Provides | What A Strong Team Provides |
|---|---|
| Audience recognition | Coherent player experience |
| Established world and characters | Systems that express that world |
| Marketing familiarity | Production knowledge |
| Existing expectations | The judgement to meet or challenge them |
| A reason to look | A reason to keep playing |
IP can shorten the distance between announcement and attention. It can’t shorten the distance between a concept and a finished, coherent game. That journey still belongs to the team.
Insider Tip: If the pitch explains the licence more clearly than it explains the player experience, the IP is probably doing too much of the design work.
Cancelling A Game Can Be Rational
Not every cancellation is evidence of incompetence. Games should be cancelled when the concept isn’t working, the market has moved, the technology can’t support the promise, or the remaining investment can’t be justified. Continuing a bad project because money has already been spent is how sunk costs become sinkholes.
The problem appears when cancellation becomes part of a repeating strategic rhythm.
A company sees a successful game and expands its portfolio. Studios are created, projects are funded, and long-term ambitions are announced. A few years later, forecasts tighten. The portfolio is “refocused”. Projects that haven’t yet proven their value are cut. The company then concentrates resources around a smaller number of supposedly safer opportunities.
On a spreadsheet, this looks like discipline. In production, it can prevent the very capability the company needs from ever becoming mature.
Healthy Cancellation vs Strategic Churn
| Healthy Cancellation | Strategic Churn |
|---|---|
| The core experience isn’t working | The portfolio direction has changed again |
| Evidence exposes a specific problem | Forecasts replace creative evidence |
| Lessons are retained and reused | Teams and knowledge are dispersed |
| The decision protects future investment | The decision resets capability |
| The studio understands why it stopped | The studio learns that every plan is temporary |
Cancellation can be responsible production management. Churn is different. Churn happens when the organisation repeatedly changes the conditions around projects faster than teams can learn from them.
New teams need time to learn how they make decisions together. Pipelines need to stabilise. Technical assumptions need to fail early enough that they can be replaced. Designers need to discover what the game actually is, which is usually a slightly different game from the one described in the first presentation with all the attractive arrows.
If every project must quickly justify a distant commercial forecast, teams can be dismantled before that capability compounds.
Insider Tip: A cancelled project should still leave the studio with stronger tools, clearer knowledge, and better judgement. If everything disappears with the project, the company has paid for the lesson and then thrown away the receipt.
You Can’t Portfolio-Manage Your Way To A Singular Game
Baldur’s Gate 3 is useful to investors because it proves a large return is possible. It is less useful as a production template because exceptional games aren’t created by copying the visible features of the last exceptional game.
You can commission another fantasy RPG. You can reuse the setting. You can request companions, romance, branching dialogue, tactical combat, character creation, and enough choices to make the quality-assurance team quietly reconsider every decision that brought them to this moment.
Those ingredients still won’t reproduce the relationships that made the original work.
The important part of a successful game is rarely the list of features. It is the way those features support one another. Exploration creates information for combat. Combat changes narrative conditions. Narrative choices alter relationships. Relationships reshape later decisions. The player believes in the world because the systems remember what happened.
That coherence is a production outcome. It depends on leadership, team continuity, technical foundations, iteration time, and a willingness to protect the game’s central design logic when schedules and budgets start applying pressure.
Copying Features vs Rebuilding Conditions
| Copying The Visible Game | Rebuilding The Conditions |
|---|---|
| Add branching dialogue | Build tools that can track consequences |
| Add companions | Give writers, designers, and systems teams shared rules |
| Add player freedom | Test how systems respond to unexpected behaviour |
| Add more content | Protect iteration time |
| Reuse the licence | Retain the people carrying production knowledge |
The first column is easy to put into a presentation. The second is what makes the presentation survivable. Features describe what a game contains. Production conditions determine whether those features can form a believable whole.
Insider Tip: Don’t benchmark a successful game only by its feature list. Benchmark the tools, decision-making, iteration, and team stability that allowed those features to support one another.
The Production Conditions Are The Strategy
If Hasbro wants another success on the scale of Baldur’s Gate 3, the question isn’t simply which IP should be adapted next. The better question is what production conditions would allow a team to build something equally coherent.
- Does the team have relevant experience, or is it learning the genre while building it?
- Can the project’s systems support the promised level of reactivity?
- Is there enough time to test relationships between content, mechanics, and narrative?
- Does leadership understand what makes the game distinct, beyond the value of the licence?
- Can the studio retain the people who carry the project’s history when priorities change?
These questions aren’t as exciting as announcing a billion-dollar investment strategy. They don’t produce a heroic trailer voice. Nobody has ever shouted “stable knowledge transfer!” while a dragon flies over an orchestra.
But they’re the difference between owning an opportunity and being able to build it.
Investment Inputs vs Production Outcomes
| Investment Input | Required Production Outcome |
|---|---|
| Funding | Enough stability to iterate |
| Valuable IP | A design identity that fits the world |
| Experienced hires | A team that can make decisions together |
| Technology | Tools that support the promised experience |
| Long-term strategy | Continuity when short-term forecasts change |
Money, licences, technology, and talent are inputs. They only become strategy when the organisation turns them into reliable working conditions. Otherwise, they remain expensive ingredients waiting for a production system that knows how to combine them.
Insider Tip: Investment creates possibility. Continuity converts that possibility into capability.
What Players See
Players don’t see impairments, portfolio reviews, or capitalised development costs when they launch a game. They see the consequences.
They see worlds that recognise their decisions or forget them. They see mechanics that support the fantasy or sit beside it. They feel when a game has been built around a clear idea, and they feel when a valuable licence has been asked to carry an experience that never developed its own identity.
Repeated cancellations also change the relationship between audiences and announcements. Every ambitious reveal becomes conditional. Every new studio becomes temporary. Every promise about a long-term videogame strategy arrives with a small invisible asterisk explaining that the plan may be refocused before the game exists. That is a trust problem, not just a financial one.
Corporate Decision vs Player Experience
| Corporate Decision | What Players Eventually Feel |
|---|---|
| Project cancellation | Promised worlds never arrive |
| Team disruption | Sequels lose accumulated knowledge |
| Portfolio refocus | Announcements become less believable |
| Shorter investment horizon | Games feel safer and less distinct |
| IP-first planning | Familiar worlds without coherent identity |
Players may never see the internal decision, but they experience its downstream effects. Trust erodes when companies repeatedly announce long-term creative ambitions and manage them through short-term reversals.
Insider Tip: Every public announcement spends a little player trust. Repeated cancellations teach audiences to wait for proof instead of believing the promise.
Final Thoughts
Hasbro’s $56 million write-down doesn’t prove that investing in games was a mistake. It proves that investment is only the beginning.
The company still has valuable worlds, major projects, talented teams, and a clear reason to keep building games. But if Baldur’s Gate 3 remains the model for future success, then the lesson needs to go deeper than “players like Baldur’s Gate”.
Players like games whose systems, stories, and consequences feel as though they were built by people working toward the same experience. That takes more than a licence. It takes accumulated capability, creative clarity, and enough stability for thousands of small decisions to become one coherent world. IP can open the door. It can’t build the game that waits behind it.
That’s it for this one! Subscribe to The Design Lab for more breakdowns and analysis. Please like, share, and comment if you found this article useful AND…
Need help applying these concepts to your game? Most games don’t fail because of bad ideas. They fail because the systems don’t work together to evoke immersion.
> Work with me:
https://thedesignlab.blog/services/
> Or go deeper into this framework:
Register for my upcoming book – Immersive Design Framework – below and get a second book, now, free!
Grab Myles’ FREE ebook now and find 15 indispensable design patterns that will equip you to craft exceptional Web3 gaming experiences. We’ll also notify you when his new book on immersive design is out!