Shawn Layden Says Developers Should Chase Passion, Not Just the Next Hit

Former Sony Interactive Entertainment America CEO Shawn Layden has put a familiar industry anxiety into unusually direct terms: too many game teams may be trying to manufacture the next hit instead of making the game someone on the team feels compelled to create.

Layden’s point is not that commercial thinking is inherently bad, or that every project should be an unchecked personal experiment. Rather, he drew a distinction between a game designed around an expectation of market success and one driven by a creative idea with real internal urgency. In his view, the stronger starting point is a project that a developer feels they have to make—the kind of idea that keeps pressing at them—rather than a calculated attempt to reproduce whatever appears successful at the moment.

That argument lands at a time when large-budget games are frequently discussed in terms of familiar structures, known genres and predictable routes to player engagement. It also arrives alongside continued attempts across the business to find a share of the enormous audience commanded by Fortnite-style live-service games. Layden’s warning is ultimately about the cost of treating a past success as a design brief.

What Layden is arguing for

Layden suggested that some developers are building games around what they believe will “hit,” rather than following the more personal creative drive of someone who feels a particular game needs to exist. He was careful not to frame the issue as simple pandering, acknowledging that the word may be harsher than he intended.

That distinction matters. A hit-oriented project begins with a prediction: a particular genre, business model, visual language or set of mechanics is assumed to have an audience because something comparable has worked before. A passion-led project begins elsewhere. It may begin with a particular feeling, character, world, gameplay interaction or problem a designer desperately wants to solve.

Neither approach guarantees quality. A team can care deeply about a bad idea, and a commercially minded game can be excellent. But the two starting points produce different pressures. When the central question is “what has already proved itself?” the safest answer often becomes a combination of elements players already recognize. When the question is “what can this team uniquely make?”, the answer may be less easily summarized but potentially more distinctive.

For players, that difference can show up in the details: a game’s pacing, its willingness to leave room for unfamiliar ideas, the specificity of its systems, or whether its world feels constructed around a particular perspective rather than a checklist of expected features.

The budget problem behind safe decisions

The complaint that major games have become cautious is not just an artistic one. Larger projects can make risk harder to approve. If a game is expensive to build, decision-makers may be more inclined to favor formulas that look easier to explain to investors, partners and audiences. The logic is understandable: proven elements can appear to lower uncertainty.

Yet “proven” is not the same as guaranteed. An approach that succeeded for one game may not work for another team, another audience or another moment. More importantly, a design assembled from recognizable successes can struggle to answer the question players eventually ask after the marketing has faded: why should this particular game exist?

Layden identified Rockstar and Take-Two as companies that know what they are doing and are in a secure position, while directing his broader concern toward other parts of the business. His remarks do not offer a universal diagnosis for every publisher or studio. They instead describe a wider creative temptation: to treat the most visible success in the market as a blueprint.

That temptation has practical consequences. Teams may spend more time defending familiar choices because they are easier to justify, while unusual concepts face a higher burden of proof. A pitch that can be compared to an existing blockbuster may be simpler to fund than one that asks a publisher to trust a fresh combination of ideas. The result can be an industry where originality is praised in principle but difficult to support at the moment a project needs approval.

Live service is not a shortcut to an audience

One major example is the ongoing pursuit of live-service success. Live service generally describes a game designed to receive continuing updates, events or content after launch, often with the goal of keeping a community active over a long period. The model can work enormously well, but it also asks for something unusually scarce: players’ sustained time.

Players cannot realistically devote the same level of attention to an unlimited number of continually updated games. A live-service game does not merely compete for an initial purchase or download; it competes for routine, attention and the space another game occupies in someone’s week. That makes copying the ambition of a dominant game far different from recreating the conditions that made it successful.

In that light, chasing “Fortnite money” is a misleading goal if it means assuming that an established audience can simply be transferred to a new product. A service game needs a clear reason for players to return, but it also needs a reason for them to leave behind—or at least divide time away from—games they already know. A familiar genre label or monetization model cannot provide that reason on its own.

Layden’s emphasis on a creator’s urgent idea therefore has a business implication as well as an artistic one. A project with a strong identity may have a better chance of establishing a relationship with players than one whose main identity is that it resembles an existing winner. That does not eliminate financial risk. It does suggest that imitation can be risky in its own way, particularly when many companies pursue the same perceived opportunity at once.

Creative vision still needs guardrails

Crucially, Layden did not advocate for total creative freedom without oversight. He said artistic vision still requires guidance and referred to projects driven by artistic ambition without sufficient “guard rails”—games that reach the market and leave observers wondering what the people making them were thinking. He did not name examples, but his intended principle was clear: a passionate concept is not automatically a finished, coherent or market-ready game.

Guardrails, in this context, are not simply rules that make a project safer. They can mean experienced people asking hard questions during development: Is the idea understandable to the intended audience? Does the game’s scope match the team’s resources? Do its systems serve its core purpose? Are players being asked to tolerate friction that adds nothing meaningful? Is the project changing in response to useful feedback without losing the thing that made it interesting?

That role can be essential. Good guidance helps a studio identify where a strong idea is getting blurred by unnecessary features, vague priorities or ambition that cannot realistically be completed. Bad guidance, by contrast, can reduce every unusual choice until the project is indistinguishable from its competitors. The challenge is not choosing between control and creativity. It is finding leadership that can protect the valuable, specific heart of a project while helping it become playable, legible and finishable.

Layden’s argument is therefore more demanding than the simplified slogan “let creators cook.” Developers need room to pursue ideas that matter to them, but they also need collaborators and leaders able to test those ideas rigorously. The ideal is neither cynical trend-chasing nor unfiltered individual expression. It is creative conviction paired with disciplined development.

The greenlight is where the conflict lives

The difficult part is that the people who want to make a game and the people who approve its budget may not be rewarded for taking the same risks. A developer can have an exciting original concept, while a publisher must consider staffing, schedules and the possibility that a new idea will not find an audience. Layden’s remarks speak to the creative side of that tension, but they do not remove the institutional barriers that can stop an unconventional project before production begins.

The discussion also raised examples of Xbox closing or divesting studios including Double Fine and Compulsion Games, both associated in the conversation with pursuing their own creative visions. The broader takeaway is not that a studio’s creative ambitions alone determine its fate; the available information does not support such a simple claim. It is that a call for more creator-led work exists in a business where studio ownership, shifting corporate priorities and approval structures can sharply limit which ideas get the chance to grow.

That makes the greenlight process especially important. If organizations say they want originality but require every proposal to resemble a known success, they have already narrowed the kinds of games that can be made. Conversely, supporting a distinct vision does not require abandoning evaluation. It requires evaluating a project on more than its resemblance to last year’s blockbuster.

Industry pressure can also shape projects late in development. As discussed in a recent report on annual release pressure and development deadlines, scheduling demands can constrain the time teams have to refine complex creative work. A studio may begin with a focused vision, then find that deadlines and shifting demands force compromises that weaken it. Protecting curiosity is not merely about approving unusual pitches; it is also about giving teams a workable path to realize them.

Why curiosity is the key word

Layden has separately warned that games have stagnated and urged developers not to lose their curiosity as the medium approaches a major turning point. Curiosity is a useful word because it does not demand novelty for its own sake. It describes the willingness to ask whether existing assumptions still serve the game being made.

For a designer, that may mean questioning whether a popular feature belongs in a project at all. For a publisher, it may mean asking whether a game’s most marketable quality is its connection to an existing trend or its own clear personality. For players, it means that the most promising game is not necessarily the one that promises the longest checklist, the largest map or the closest match to something already popular.

There is no simple fix in Layden’s remarks. Big games will continue to need budgets, plans and commercial accountability. Creative projects will still need editing, production discipline and leadership. But his central standard is a worthwhile one: before pursuing the next hit, teams and publishers should be able to explain what genuine idea is driving the work—and why this particular group of people is the one that needs to make it.