Starfield set out to answer a gloriously unreasonable question: what if Bethesda Game Studios took its familiar open-world role-playing formula, loaded it into a spaceship, and refused to stop adding planets until someone unplugged the galaxy? Former lead systems designer Kurt Kuhlmann now suggests that the answer was both impressive and revealing. Bethesda achieved an enormous amount, he says, but the project’s scale ultimately stretched beyond the studio’s natural advantages.
That is a more useful observation than a simple declaration that Starfield was “too big.” Big games are not automatically misguided, and a game does not need to surpass every prior hit to justify existing. But Kuhlmann’s reflections describe a particular production problem: Starfield was not merely an established Bethesda structure shifted into a sci-fi setting. It required major new technology, a giant quantity of content, and a form of world-building that differed from the tightly authored geography associated with games such as The Elder Scrolls and Fallout.
A new universe came with new foundations
Kuhlmann pointed to the extensive engine work behind Starfield as an early challenge. The game represented Bethesda’s largest engine overhaul since the original Oblivion, meaning the team had to get fundamental systems working before it could build everything dependent on them. In development, that sequence matters enormously. If core technology arrives later than planned, the remaining time for quests, balancing, environmental detail, encounters, polish, and the countless smaller decisions that give an RPG personality becomes smaller too.
It is the least glamorous part of making an enormous game. Players may remember a city skyline, a faction quest, an unexpectedly useful side character, or the first time a ship lands on a distant world. Development teams also need to make sure the machinery underneath those moments is dependable: how locations stream, how encounters populate, how spaces connect, how characters behave, and how all of it holds together across a vast game.
Starfield had the additional burden of being a wholly new setting for the studio. The Elder Scrolls and Fallout each arrived with years of accumulated identity, recognizable visual language, established lore, and audience expectations that could be extended. Starfield needed to establish its own future history, factions, systems, planets, ships, and tone while also modernizing the technical foundation supporting them. A fresh universe can be creatively liberating, but it does not come with a pre-built warehouse of assumptions.
“Skyrim in space” was never the intended shortcut
Kuhlmann explained that Todd Howard’s ambition was not to make a straightforward version of Skyrim relocated to one alien planet, with perhaps a handful of nearby stops. The intended game was a broad open-world space experience. That distinction is central to understanding both the design and the difficulty.
A single densely constructed landmass allows a studio to concentrate its authored content. It can place a cave just beyond a road, put a strange NPC beside a ruined tower, align a faction storyline with a memorable city, and make a journey feel full because the distance between discoveries is carefully managed. The density itself becomes part of the game’s rhythm.
A multi-planet space RPG changes the equation. The player expects travel, scale, exploration, and a sense that the stars contain more than one curated district wearing a different helmet. Yet every destination also invites scrutiny. If a game promises a huge frontier, it must decide how much of that frontier can be hand-authored, how much must be systemic, how often content can repeat, and what exploration should feel like when the player is moving between worlds rather than hiking across one continuous province.
Related coverage includes Former Starfield Lead Says Bethesda's Space RPG Was Too Ambitious for Its Team.
Kuhlmann’s retrospective assessment was blunt: the vision was extraordinarily ambitious, but Bethesda could not fully make the game that vision demanded. He did not dismiss the accomplishment. Instead, he said the team pulled it off to an impressive degree while acknowledging that this style of project was not especially aligned with Bethesda’s strongest suit.
The challenge was not simply creating a large game. It was creating enough meaningful content for the scale promised by an open-world game spread across space.
The content problem is bigger than a map size problem
Kuhlmann said that even Starfield’s sizable team was not large enough to produce the amount of content required by its grand concept, and that the game would have needed substantially more developers. This is a reminder that raw map scale and playable density are not interchangeable. A planet count can communicate scope, but it cannot independently create the feeling that every landing site, route, settlement, and detour was worth the trip.
For a studio famous for wandering off the main road and finding a surprising pocket of handcrafted storytelling, the challenge is particularly sharp. Bethesda’s reputation rests in part on places that feel deliberately positioned for curiosity: the odd quest hook, the cluttered room that implies a life, the dungeon that turns out to be more elaborate than its entrance suggests. Those qualities take time. They often require artists, designers, writers, quest teams, and testers to revisit a location again and again.
Space makes that labor multiply. A larger number of worlds creates more terrain, more points of arrival, more possible player routes, and more expectations for what lies beyond the next landing. Systems and procedural generation can help make a universe navigable at that size, but they do not erase the cost of making individual discoveries distinct. The broader the canvas, the greater the pressure on every authored layer placed over it.
That does not mean a space RPG must be small to work, or that systemic exploration is inherently inferior to curated adventure. It means the balance is unusually difficult. A studio can make an expansive game that supports player stories, or a concentrated game packed with authored surprises. Combining both across a galaxy asks for a level of production capacity that even large teams may struggle to provide.
Why the comments matter for Bethesda’s next chapter
Kuhlmann’s comments also add context to the long-running anticipation around The Elder Scrolls 6. He previously indicated that many people at the studio wanted to move to that sequel after Fallout 4, but Howard chose Starfield instead. That decision makes sense as a creative swing: a new science-fiction universe gave Bethesda an opportunity to attempt something it had not done before. It also meant postponing the follow-up to one of its most enduring fantasy RPGs.
There is no need to treat that choice as evidence that Starfield should never have been made. New ideas are valuable precisely because they carry uncertainty, and a major studio’s catalog would be poorer if every project were a sequel built only from its safest ingredients. Still, Kuhlmann’s comments explain why the gamble was so demanding. Bethesda did not simply take its existing expertise and apply a space texture pack; it tried to expand the boundaries of what that expertise could cover.
For observers watching the industry’s crowded schedule, the lesson is wider than one studio or one game. As noted in the increasingly packed fall 2026 gaming calendar, major releases compete not only for sales but for players’ time and attention. Massive games face another competition before launch: the internal contest between their biggest idea and the practical resources needed to make every part of that idea feel intentional.
Ambition is not the villain, but it needs a shape
There is an easy, slightly smug response to any difficult blockbuster: just make it smaller. Sometimes that is correct. But “smaller” is not a design philosophy by itself. The more important question is where a game concentrates its effort. Starfield’s development, as described by Kuhlmann, shows what happens when a project must simultaneously establish new tools, a new setting, and a massive exploratory framework.
The strongest reading of his remarks is not that Bethesda failed to achieve anything, nor that large-scale space adventures are impossible. It is that Bethesda’s best-known talents may be most potent when they can pour detail into a more focused space. The studio delivered a vast sci-fi RPG and, by Kuhlmann’s account, did so under formidable constraints. Yet the same account recognizes that its intended scale required more people and more content than the production could realistically supply.
That candor is valuable. Players often see a finished game as one indivisible object: either it meets their hopes or it does not. Developers see the trade-offs behind it—the systems finished later than desired, the content that a grand concept still needs, the team size that looks huge until it is measured against an entire galaxy. Starfield remains a striking attempt to broaden Bethesda’s formula. Kuhlmann’s view is that the attempt was real, ambitious, and in important ways larger than the studio could fully serve.
