Grand Theft Auto 5 was built on an enormous scale, but one of the clearest lessons its developers took from earlier projects was not about map size, visual fidelity, or adding more activities to a city. It was about knowing when to let go.
In a 2013 interview with Edge, Aaron Garbutt, who served as art director on Grand Theft Auto 5, discussed the most valuable lessons Rockstar had learned while making its Grand Theft Auto games. His answer centered on adaptability: development teams should avoid becoming too attached to a process, a target, an asset, or an idea simply because they had previously committed to it.
"Let what's best for the game dictate the way forward," Garbutt said, stressing that a large project needs ideas that can change as its many parts come together.
That principle may sound straightforward, but it describes one of the hardest disciplines in game development. Games are made through long periods of iteration, with art, technology, mission design, writing, animation, audio, and gameplay systems all depending on one another. A feature that looks exceptional in isolation can create trouble elsewhere. A mission concept may conflict with how players naturally move through the world. A visual asset may be expensive to render at the scale required. A system with exciting possibilities may take so much time to implement that it prevents other parts of the game from receiving necessary attention.
For useful background on this topic, read Under Par Golf Architect: Northern Isles DLC Adds New Courses and Resort Challenges.
For a game as broad and interconnected as GTA 5, those decisions become especially significant. Los Santos is not merely a backdrop for the story. It has to support driving, shooting, exploration, side activities, scripted missions, ambient behavior, and the unpredictable ways players interact with an open world. Every major decision can affect several teams at once.
Flexibility over attachment
Garbutt's point was not that developers should make constant changes without purpose. He distinguished useful adaptation from changing direction merely for the sake of it. The goal is not instability; it is responsiveness. If a better solution emerges, or if testing reveals that an earlier decision is hurting the overall experience, the team needs to be willing to reconsider it.
That is the practical version of the long-standing creative expression "kill your darlings." The phrase usually refers to removing a favorite idea when it no longer improves the work. In games, however, the cost of holding onto a darling can spread far beyond a single scene or paragraph. A beloved feature can affect schedules, performance, controls, player readability, mission pacing, and the work of many departments.
Garbutt explained that Rockstar sought to remain open-minded about everything involved in development, from plans and goals to individual assets and concepts. Rather than treating an earlier choice as permanent, the team could assess whether it was still serving the game as the project evolved.
This is particularly important for open-world development, where the shape of the final experience cannot be fully understood at the start. Teams can establish a vision, build prototypes, and set milestones, but meaningful discoveries happen during production. A street layout that appears sensible in an editor may feel awkward at driving speed. A district designed to look distinctive may need changes to better guide players during missions. A gameplay mechanic might work beautifully in a controlled encounter but become frustrating when placed amid the freedom of a city.
Those discoveries are not necessarily signs that a project is failing. They are a normal consequence of making a complicated interactive space. The crucial issue is how a studio reacts when those discoveries arrive.
How Rockstar described its layering process
Garbutt described Rockstar's approach as one that begins with the world and then adds other major elements on top of it, including missions, story, and the broader structure of the game. Rather than operating as sealed-off layers, these components heavily influence one another.
A mission is shaped by the space where it takes place. In turn, a mission may reveal that the space needs clearer routes, stronger landmarks, altered traffic behavior, or different sightlines. Story requirements can demand a new location or a revised version of an existing one. Gameplay needs may lead designers to adjust the world so an activity is more readable, entertaining, or reliable. That feedback loop is continuous.
Garbutt said the team was always playing and refining the game, adjusting its elements to work better together. This emphasis on play is important. Plans and documents can identify intentions, but actual play exposes how systems feel once players are in control. It can reveal whether a pursuit has enough momentum, whether a location supports a sequence cleanly, or whether a mechanic creates confusion in situations the designers did not initially predict.
In an open-world game, that testing has another challenge: players do not always approach content in the anticipated way. They may arrive from an unusual direction, bring an unexpected vehicle, interrupt a sequence, or spend hours engaging with activities far from the main narrative. The development process must account for that flexibility because it is part of the appeal of the genre.
Experienced teams still need to adapt
At the time, Garbutt acknowledged the value of having an art team with deep experience in making open worlds. That familiarity means developers are less likely to be surprised by every production problem. They understand many of the constraints involved in constructing dense, navigable environments and can draw on techniques developed over previous games.
Yet experience does not remove uncertainty. New problems continue to appear as technology changes, design ambitions expand, and individual projects create their own requirements. Garbutt noted that Rockstar's method required the team to be ready to adapt when those new circumstances emerged.
That is a useful reminder that experience is not the same thing as rigidity. A veteran team can use what it has learned without assuming that every old solution is automatically the right solution for the next game. In fact, the ability to recognize the limits of past methods may be one of the biggest benefits of experience.
For players, this work is often invisible. A final game presents its streets, characters, activities, missions, and systems as if they always belonged together. The messy reality is that polished cohesion usually comes from repeated revision. Content may be redesigned, moved, repurposed, simplified, or cut before players ever see it.
Changing course does not always mean wasting work
One notable part of Garbutt's explanation is that changing plans did not necessarily mean throwing content away. He said the team was rarely discarding content outright. Instead, development could involve adapting work to a new purpose or revising surrounding systems so that existing material fit more effectively.
That approach matters on a project of GTA 5's scale. Building environments, props, vehicles, animations, and mission spaces requires substantial effort. When an original plan stops working, repurposing parts of that work can preserve value while still allowing the game to move in a better direction.
It also reflects a more productive interpretation of "killing your darlings." The phrase does not require destroying every idea that changes. Sometimes the right answer is to remove an idea from one context and find a place where it genuinely works. A location intended for a particular mission could become part of the wider city. A mechanic that is too disruptive for the main campaign might inform a side activity. An asset may survive even if the original sequence around it does not.
The larger objective is to avoid defending old decisions simply because time has already been spent on them. That tendency, often called sunk-cost thinking, can be dangerous in any creative production. In game development, it can lead teams to keep features that are no longer fun, stable, or compatible with the rest of the project.
A lesson that reaches beyond GTA 5
Garbutt's comments remain relevant because modern games are still defined by competing demands. Developers need to balance creative ambition against technical limits, production schedules, accessibility, performance, and the expectations created by the game's own design. A feature can be impressive and still be wrong for the final product.
Open-world games make that balance especially visible. Their promise is freedom, but that freedom adds enormous complexity. Systems must react to one another. Cities need to feel alive while remaining understandable. Missions need spectacle without breaking when players behave unexpectedly. The more moving parts a game has, the more valuable it becomes to regularly reassess whether they are working in harmony.
Grand Theft Auto 5's development philosophy, as Garbutt described it, was not about pursuing a fixed blueprint at all costs. It was about keeping the final game at the center of decision-making. That can mean preserving an idea, reworking it, moving it somewhere else, or abandoning it when it no longer earns its place.
For creators, it is a demanding standard. For players, it helps explain why the best open worlds often feel more unified than the vast amount of work behind them would suggest. The city, missions, story, and systems are not simply assembled side by side. They are refined against one another until the game itself points toward the better path forward.
Community
Discussion
Start the conversation.
No comments have been posted yet.