Technology Doesn’t Save Projects. Focus Does.

A pixel art scene depicting a group of people working at computers with green code on their screens, some showing confusion with question marks above their heads. One character at a desk is focused on drawing, with a light bulb above indicating a bright idea.

Brendan Greene’s PlayerUnknown Productions has announced layoffs, cancelled further development of Prologue: Go Wayback!, and is downsizing its team while continuing work on its proprietary terrain-generation technology, Melba. The studio says the decision was driven by the costs associated with developing the technology, which is also intended to power its future MMO project, Artemis. On the surface, this looks like another unfortunate downsizing story in an industry that has seen far too many of them. But underneath it sits a problem that affects studios of every size. Sometimes the technology becomes the project.

When the Tool Becomes the Product

Most developers have experienced this at some point. You start building a game and discover a technical limitation. Maybe the world isn’t large enough. Maybe the AI isn’t flexible enough. Maybe the content pipeline is too slow. So you build a tool to solve the problem. The danger is that the tool slowly becomes more important than the game it was supposed to support. The original goal was to create an experience for players. Now the team is spending most of its time creating technology. At some point, you stop asking: “Is the game getting better?” And start asking: “Is the technology getting better?” Those are not always the same thing. Neither approach is inherently wrong.

Product Focus vs Technology Focus

Product FocusTechnology Focus
Builds player experiencesBuilds technical capabilities
Success measured by player valueSuccess measured by technical achievement
Content drives developmentTechnology drives development
Solves immediate design problemsSolves future possibilities
Ships value quicklyOften requires long investment cycles

The challenge is knowing which one your studio actually needs, as there are various options available on the market today, each with its own unique features and benefits. It’s essential to carefully evaluate the specific requirements of your studio, considering factors such as the type of projects you typically undertake, the size of your team, and the technical expertise of your staff. Additionally, understanding the long-term goals of your studio can help guide your decision-making process, ensuring that the equipment or software you choose will not only meet your immediate needs but also support your growth and evolving capabilities in the future.

Insider Tip: Technology should remove barriers between the player and the experience. The moment the technology becomes the primary goal, it deserves closer scrutiny.

The Cost of Building for Tomorrow

One reason proprietary technology is attractive is because of what it might enable later. Melba isn’t just intended for Prologue. It’s also expected to support Artemis, Greene’s much larger vision of an Earth-scale multiplayer experience. That makes the investment easier to justify. The problem is that future opportunities still need to survive present realities. Every dollar spent building technology is a dollar that isn’t being spent on content, iteration, testing, or production. Every month spent improving infrastructure is a month players are waiting for something tangible. This creates a difficult balancing act.

The Future Vision Problem

BenefitCost
Long-term scalabilityHigher development costs
Proprietary advantageLonger development timelines
Unique technical capabilitiesGreater financial risk
More ambitious future projectsFewer immediate player-facing outcomes
Studio independenceIncreased pressure to justify investment

Many studios underestimate how difficult it is to survive the journey between those two sides, often ignoring the myriad challenges that can arise along the way. From managing budgets and timelines to navigating creative differences and unexpected setbacks, the path can be fraught with obstacles. Additionally, the emotional toll on team members, who pour their hearts and souls into the project, cannot be overlooked. These complexities highlight the need for resilience, adaptability, and robust support systems to ensure that studios not only endure but thrive as they transition from concept to completion.

Insider Tip: A future vision only creates value if the studio survives long enough to realise it.

Why Players Rarely Care About the Technology

Players care about experiences. They care about whether a world feels believable. Whether exploration feels rewarding. Whether systems create interesting situations. They rarely care how those things were built. A player doesn’t buy a game because it uses a custom terrain-generation engine. They buy it because the game creates an experience they want to have. This is one reason technology-first projects can become dangerous. Internal excitement around technical breakthroughs doesn’t always translate into external excitement from players.

What Studios Celebrate vs What Players Remember

Studios CelebratePlayers Remember
New rendering technologyMemorable moments
Procedural generation systemsInteresting worlds
Custom engine featuresGreat gameplay
Technical breakthroughsEmotional experiences
Development innovationsPlayer stories

The technology matters. But only because of what it enables. This story isn’t really about Brendan Greene, Prologue, or even Melba. It’s about focus. Every project has limited resources. Limited time. Limited money. Limited attention. The most successful teams are often not the ones with the most ambitious technology. They’re the ones that remain relentlessly focused on what creates value for players. That doesn’t mean innovation is bad. It means innovation needs a purpose. Technology should exist to serve the experience. Not the other way around.

Insider Tip: Players remember outcomes. Developers remember implementation. Successful projects bridge the gap between the two.

Final Thoughts

The cancellation of Prologue: Go Wayback! serves as a poignant reminder that ambitious technology comes with real costs and significant implications for those involved. While building proprietary tools can unlock incredible opportunities and bring innovative ideas to life, it also introduces financial pressure and production complexity that can overwhelm smaller studios. These challenges often manifest as prolonged development timelines, which can hinder progress and creativity. For these smaller studios, especially those operating on limited budgets, the challenge lies in ensuring that technology serves as a means to enhance creativity and storytelling, rather than becoming the end goal itself.

Ultimately, players judge experiences based on the immersion and enjoyment they derive, not the infrastructure that supports them. The studios that succeed in the competitive landscape of gaming are usually the ones that maintain a clear focus on that crucial distinction between technological advancement and the artistic vision of their games. Because great technology can support a great game by providing developers with the tools they need to craft engaging narratives and dynamic gameplay. But it cannot replace one; the heart of gaming lies in the experiences created, not just the engines that drive them.

Please like, share, and comment if you enjoyed this article 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!

* indicates required
The eBook will be sent to your email address immediately.
technology doesn’t save projects. focus does, technology won’t save us, tech won’t save us, technology will not save us, if technology advances, if technology does not improve in the long run then, g technology g drive not showing, g technology drive not showing up, geforce now doesn’t save settings, project not saving, microsoft project does not save, technology does not work, why technology projects fail, project couldn’t save, project setting is not saved due to an error, project not in a recommended save location, r won’t save, r not saving, rstudio won’t save file, which program does not automatically save the document, final cut pro x didn’t save my project, 4 technology is not a way for economic growth, 5 2 final project milestone two technology solutions and recommendations, 5 times tech saved lives, 5 technologies that help the environment, 5 technologies that will change the world, 5 2 project one technology hardware and software, 7 does technology always follow science explain, 7 technology resources, 7 technology, 7 technologies remaking the world, 8 what does new technology almost always do, technology cannot save you, project technology examples

Leave a Reply