Ico, and Design by Subtraction

Many games are described as inspirational, but few modern games can claim the influence of Ico.

Game makers have pointed to it as an important reference for Papo & Yo, Brothers, Journey, Rime, The Last of Us, Prince of Persia, and even Halo 4. Dark Souls creator Hidetaka Miyazaki has said that Ico awakened him to the possibilities of the medium.

That is striking because Ico is such a quiet, restrained game. It is not overloaded with systems, spectacle, rewards, or modes. It is a simple story about a boy and a girl escaping a castle.

The player controls Ico, helps Yorda move through the castle, solves some puzzles, and fights shadowy monsters with a stick or sword. That is mostly it.

Even now, Ico feels minimalist. On the PlayStation 2, that kind of bare-bones design felt even more unusual. There was no broad culture of small, restrained, atmospheric games around it yet.

The lack of features was deliberate. Designer Fumito Ueda later described the approach as "design by subtraction." The idea was not to add until the game felt large. It was to find the core, then remove anything that did not fully support it.

Early in development, when the game was being made for the original PlayStation, Ico had more conventional material: complex combat, a wider cast of characters, and areas such as a village, a dense forest, and a deserted island.

Those things were cut, not simply for budget or technical reasons, but because they distracted from the heart of the game.

The core of Ico is the bond between Ico and Yorda. The game is about companionship, protection, vulnerability, and looking after someone in need.

That theme is expressed physically. Holding a button to hold Yorda's hand is not just an input trick. It makes the relationship tactile. The player feels the act of staying connected.

Because that bond is the core, the remaining systems support it. Most puzzles are only half complete when Ico reaches the solution himself. The other half is making the space safe or accessible for Yorda.

Combat follows the same logic. Ico generally does not die in ordinary fights. The real fail state is letting Yorda be taken away by the shadowy enemies. The player's own safety is less important than hers.

Ico does not level up, learn elaborate combos, parry attacks, or perform flashy finishers. He swings a stick or sword with the desperate simplicity of someone trying to defend another person.

Yorda is needed to open doors, which makes her part of progression. She is also needed to save the game, because the two characters sit together on stone benches to store progress.

That means her absence is not just narrative. It changes the player's sense of safety and capability. When Yorda is gone for a stretch, the game feels more vulnerable and lonely because several familiar supports disappear with her.

The design keeps returning to the same point: the relationship is not decoration. It is the structure of the game.

The team's attention went into the things that made the relationship and place feel real. The castle is intricate and interconnected, so it feels like an actual space rather than a sequence of levels.

The animation is expressive and believable, drawing on the tradition of games such as Another World, Flashback, and the original Prince of Persia. The characters' movement sells the weight and fragility of the connection.

The game also removes elements that would break the spell. There is no health bar, no map screen, no inventory screen, no static characters repeating dialogue, and often no background music.

Those absences matter. They prevent the player from constantly seeing the machinery of the game. What remains is unusually focused: a game distinctly about something, with little extraneous material to dilute that message.

This does not mean every game should be as stripped down as Ico. Its combat can feel too simple and repetitive, and even Ueda has suggested that the subtraction may have gone too far in places.

Shadow of the Colossus, his follow-up, has more elements: health bars, music, more overt action, and a broader mechanical frame. But it still subtracts in service of the core. It is an action game without traditional enemies because ordinary enemies would distract from the titanic boss encounters that actually express the game's idea.

The lesson is not that fewer features are always better. The lesson is that features should earn their place by strengthening the central experience.

A small game can be unfocused, and a large game can be coherent. What matters is whether each piece supports what the game is trying to be.

That lesson is useful in an era where many games seem to need two dozen weapons, crafting, micromanagement, collectibles, side missions, upgrade trees, and a long list of store-page bullet points.

Those features may be fun in isolation, but each one has a cost. It takes attention, development time, interface space, tutorial space, and player focus. More importantly, it can blur the idea at the center of the game.

Does every action game need a side mode that belongs to another genre? Does every sequel benefit from another traversal gimmick or mechanical layer? Sometimes the honest answer is no.

Removing a feature can be a creative act. It can make the remaining game sharper, clearer, and more memorable.

Fez offers a clear example of this thinking. Creator Phil Fish has said that the game once had hearts, Zelda-like heart containers, and puzzles about redistributing weight.

Those ideas were removed because they did not support the central mechanic of rotating the world or the central theme of seeing things from a different perspective.

Fish described Ueda's approach as giving him the strength to cut into his own game. Each time he removed something that did not belong, the game became tighter and more streamlined.

The advice to other developers is direct: look hard at the game and ask what is necessary. Ask what really has anything to do with what the game is trying to accomplish.

It is easy to add features because they seem cool, increase length, or create another selling point. It is harder to ask whether they dilute the game's message.

Ico resonates because it is so clear about what matters. The bond between Ico and Yorda shapes the puzzles, combat, saving, progression, animation, interface, sound, and world design.

Design by subtraction is not minimalism for its own sake. It is a discipline for protecting the core of a game from everything that weakens it.

The useful question is not "what else can this game have?" It is "what can this game remove so the thing it is really about becomes impossible to miss?"