Some of the most familiar parts of a game can begin as a disagreement in a meeting room. For The Elder Scrolls V: Skyrim, one such debate centered on the way players would look at character progression: not as a plain list of skills, but as constellations spread across a night sky.
Bruce Nesmith, a designer whose Bethesda work included Morrowind, Oblivion, and Skyrim, has recalled that he doubted the idea throughout production. Todd Howard wanted the visual design of the constellations to help express how skills related to each other. Nesmith initially favored a more conventional, explicitly functional presentation.
“Todd had this vision for how the constellations would reflect your skills,” Nesmith said. “He was looking at the art and wanted the art to drive some of how the skills related to one another.”
Nesmith’s concern was direct: a list would be easier to read, while an elaborate star chart might confuse people. His position was not that character progression itself was unnecessary. The question was how that information should be presented to a player who is trying to make choices quickly and understand the consequences of those choices.
“Why can’t we just put a list out? It’s far more functional. People are going to get confused by these constellations; it’s not going to work, I’m not seeing it.”
After release, Nesmith says the response showed that his prediction had missed the mark. Players liked the constellations, and he has been unusually candid about the result.
“I held that all the way through production, and the game gets out there, and people loved the constellations. They thought they were fantastic. I was clearly wrong.”
A skill tree that looked like it belonged in Skyrim
A skill tree is a progression interface that lets players spend advancement points or perks on abilities within a category. The word “tree” usually refers to the branching structure: early choices can lead to later, more specialized options. In Skyrim, those choices were tied to the game’s skills and shown in a constellation-like arrangement rather than being delivered as a plain numerical screen.
Related coverage includes Skyrim Designer Admits He Misjudged Todd Howard's Constellation Skill Trees.
That distinction matters because menus do more than store information. They establish tone. A spreadsheet-style list may make comparison and scanning feel immediate, but it can also feel detached from the place and fiction around it. A constellation presentation can communicate that progression is part of the game world’s atmosphere, even if it asks players to spend an extra moment learning its visual language.
Nesmith’s retelling identifies the central trade-off clearly. The proposed list favored immediate utility. Howard’s approach gave visual art a larger role in communicating relationships between skills. Neither priority is frivolous: players need usable menus, while a role-playing game also benefits when its systems feel coherent with its world.
The eventual outcome suggests that players were willing to meet the interface on its own terms. An initially unfamiliar design can become legible through repetition, and it can leave a stronger impression than a more generic alternative once that learning step is past. That does not mean every ornate menu is automatically clearer, or that function should surrender to decoration. It does show why teams sometimes take risks on a presentation that is less conventional at first glance.
From Oblivion’s numbers to Skyrim’s stars
Nesmith framed the difference as a noticeable change from Oblivion, where progression was associated more closely with sets of numbers. Skyrim made the interface itself a visual statement. Its stars did not merely sit beside the character system as decoration; they became the form through which players navigated it.
That is an important design distinction. When art is added after a system has been made, it may only ornament the underlying structure. When the art helps determine how connections are displayed, it becomes part of the system’s communication. The player is still considering progression, requirements, and possible choices, but they do so through an image rather than a simple vertical list.
For players, the practical implication is that interface design can shape how a game is remembered. A player may not recall every numerical detail of a character build years later, yet still immediately remember the act of moving through a field of stars. That sort of visual identity can make a routine process—opening menus and assigning perks—feel specific to one game rather than transferable to any other RPG.
There is also a useful lesson in the fact that Nesmith did not suddenly change his mind halfway through development. He says he held his objection through production. Development is often described as collaboration, but collaboration does not require everyone to reach the same conclusion before a decision is made. It requires a team to surface concerns, choose a direction, and then build the result with enough conviction that players can judge the finished work rather than an abandoned compromise.
Why the admission matters
Nesmith credits Howard not just with the better call, but with being in the leadership position to make it. That is a compact explanation of an often difficult creative responsibility. A lead must listen to an objection that may be sensible, identify where the team is divided, and decide whether an unconventional idea is worth the risk.
There is no evidence here that the concern about usability was irrational. In fact, it was precisely the kind of concern a game team should raise when it is considering an unusual interface. Players must be able to understand their options. The lesson is instead that usability cannot always be reduced to presenting information in the most stripped-down form possible. Familiarity, mood, visual hierarchy, and a game’s wider identity can all contribute to whether people ultimately find a system satisfying.
That tension is especially relevant to RPGs, where players repeatedly interact with inventories, maps, quest logs, dialogue choices, and progression screens. A single menu is rarely a minor detail when it becomes a routine part of dozens of hours of play. It can either feel like an interruption or like a continuation of the game’s world.
The story also serves as a reminder that player reaction is the final test for many debated design decisions. Internal experience can reveal problems, but the audience brings different assumptions, habits, and preferences. Developers can make informed predictions; they cannot fully reproduce the perspective of everyone who will eventually use the feature.
That is why candid retrospectives are valuable. They replace the simplistic idea that successful games emerge from unanimous certainty with something more credible: people disagree, leaders make calls, and sometimes the person who argued hardest against a decision gets to acknowledge that the audience proved them wrong.
What it does—and does not—tell us about the next Elder Scrolls
The discussion is a retrospective about Skyrim, not a confirmation of any specific interface, progression feature, or design plan for the next Elder Scrolls. It should not be read as evidence that constellations will return, nor that a future game will follow the same approach.
What it does offer is a useful window into the reasoning behind a major design choice in one of the series’ best-known games. The constellation interface was a visual leap from the more numbers-driven presentation Nesmith associated with Oblivion. Its positive reception, in his account, validated the choice to let the artistic concept carry some of the explanatory weight.
For anyone watching future Bethesda projects, the broader point is not “all menus should be celestial.” It is that a game’s systems and its artistic presentation need not be separate departments of thought. A bold interface can be a calculated risk: less immediately conventional, perhaps, but potentially more memorable and better aligned with the game it belongs to.
Creative disagreements of this kind are not confined to game menus. They sit within wider debates over how technology, tools, art direction, and decision-making should serve a final work; related questions are also emerging in industry conversations about creative tools and artists. Nesmith’s anecdote is smaller and more concrete: a designer wanted the straightforward list, another leader trusted the stars, and players responded warmly enough to settle the argument.
