Design Philosophy: Fumito Ueda, Design by Subtraction

Fumito Ueda, studio portrait at E3 2016

The Principle

“Whether it was the girl’s animation or the details of the map, I didn’t hold back on removing and subtracting elements as needed. If something felt unfinished or lacking, then I’d remove it.” – Fumito Ueda, on making Ico1

The method now has a name – design by subtraction – and Ueda’s own account of it is disarmingly practical. In the same interview he described noticing a chair in a castle screenshot that did not look good, and laying out the only two honest options: fix it or cut it. He cut the chair.1 The doctrine underneath is severe: every element in the work is either actively serving the core emotion or actively diluting it. There is no neutral furniture. Most games – most products – are assembled by addition, features accreting until the surface is full. Ueda builds the way a sculptor works stone, removing until only the feeling is left.

Three games in two decades. A boy leading a girl by the hand through an empty castle. A rider crossing a deserted land to fell sixteen giants. A boy and an enormous creature learning to trust each other. Nobody confuses an Ueda game with anyone else’s, and the signature is made entirely of what is missing.

Context

Ueda was born in 1970 in Tatsuno, a small castle town in Hyogo prefecture, and trained as a painter – he studied oil painting at the Osaka University of Arts, then spent his early twenties making art and animation on an Amiga while his classmates took salaryman jobs.2 He entered games sideways and late: a CG animator at Kenji Eno’s studio Warp in the mid-90s, then Sony in 1997, where the animator with no design credits somehow pitched and led one of the most radical projects of the PlayStation 2 era.23

The painter’s training is the key to everything after. A painting cannot explain itself with menus; it holds one composition, and everything inside the frame either strengthens it or weakens it. Ueda brought that criterion into a medium whose instinct was always more – more systems, more numbers, more screen furniture – and the collision produced his career. He has also credited his amateurism as an asset: not knowing how games were supposed to be made left him free to notice what they did not need.3

The Work

Ico (2001): Holding Hands as the Entire Design

The pitch was “boy meets girl,” and the shipped game is barely more: a horned boy and a pale girl escaping a castle, joined by the mechanic that defines the work – you hold R1 to grip her hand, and you feel the tug of her weight as she follows. No health bars, no score, no map, no dialogue you can understand. Ueda’s team cut the interface, cut the stats, cut nearly all combat, and cut the chair, leaving light, architecture, and the grip of one hand in another.1 The industry noticed what remained: Ico’s emotional directness became the founding document for every game since that chose feeling over features.

The PlayStation 2, the machine Ico and Shadow of the Colossus were carved from

Shadow of the Colossus (2005): Subtraction at Landscape Scale

The follow-up asked how far the method could go. A vast forbidden land with no towns, no NPCs, no side quests, no enemies at all – except sixteen colossi, each a living puzzle you climb like architecture. The empty traversal between battles is not padding; it is the game’s conscience, time to feel the weight of what you are doing, because every victory plays as a small death rather than a triumph. Where other studios filled open worlds with content, Ueda emptied one to make room for doubt. It remains the medium’s clearest proof that what you leave out does the emotional work.

The Last Guardian (2016): Trust as a Mechanic

Nine years in development, across a studio departure and a platform change, the third game staked everything on one relationship: a boy and Trico, a building-sized creature that behaves like an animal rather than a tool.2 Trico does not obey promptly. It gets distracted, hesitates, misjudges – by design, because trust that responds instantly is not trust, it is an interface. Players divided over the friction exactly as Ueda must have known they would; the ones it landed for describe an attachment no obedient companion has ever produced. It is the subtraction method applied to control itself: he removed the certainty.4

Fumito Ueda interviewed at Gamelab 2017

The Method

Ueda’s method begins where most design documents end: with a single feeling the finished work must produce. The girl’s hand. The sorrow of the kill. The creature’s trust. That emotion becomes the spec, and the production process is a long interrogation of everything else – does this system, this HUD element, this chair, sharpen the feeling or blur it? Blur means cut, regardless of the labor already sunk.

The discipline shows most in what his games refuse to explain. No tutorials narrate the mechanics; no interface quantifies the relationships. The refusal is functional: a number over Trico’s head would convert a creature into a resource, and a minimap of the Forbidden Lands would convert wandering into errand-running. Ueda understands that instruments change what they measure – the interface is not neutral packaging around an experience, it is the experience’s frame, and most of the time the strongest frame is none.

Influence Chain

Who Shaped Him

Oil painting – the frame discipline. Composition as a single statement, and the trained eye for the element that weakens it.2 (Formative training)

The amateur’s path – Amiga animation, a late start, no formal game-design education: the freedom of not knowing the conventions well enough to obey them.3 (Formative experience)

Who He Shaped

The emotional-minimalist school. Journey, Inside, and the entire wing of games that trust atmosphere over instruction descend from Ico’s example; its creators have said as much for two decades.

Design by subtraction as shared vocabulary. The phrase escaped his games and became a general design term – shorthand for cutting features to protect a core experience.1

The Throughline

Ueda completes this series’ second matched pair. Hideo Kojima and Ueda are both auteurs of the same machine generation, running opposite operations: Kojima grafts cinema on until the game overflows the screen; Ueda carves away until only one feeling remains. Maximal and minimal authorship, same medium, same conviction that a game should be someone’s. The deeper rhyme is with Peter Zumthor: both produce rare, slow, atmosphere-first work where presence is the product – Shadow of the Colossus is a thermal bath with sorrow instead of water. And behind both stands Dieter Rams: less, but better, applied to feeling. (Series bridge)

What I Take From This

The chair is the rule I quote most: when an element is not good enough, fix it or cut it – shipping it as-is was never on the list.1 Software grows chairs constantly, features too weak to defend and too familiar to delete, and every one dilutes the product’s single feeling. The emotion-as-spec move is the deeper practice: name the one thing a user should feel, then audit every screen against it – most interface elements fail that audit the way Ico’s health bar would have. And Trico taught me something uncomfortable about responsiveness: instant obedience reads as mechanism, and a little friction, honestly earned, is how software feels alive rather than merely functional.

FAQ

What is design by subtraction?

Fumito Ueda’s method of building a game around one core emotion and removing every element that does not serve it – interface, stats, dialogue, even furniture that looks wrong.1 The term originated with his work on Ico (2001) and has become general design vocabulary for protecting a core experience by cutting features.

What games did Fumito Ueda make?

Three, in twenty years: Ico (2001), Shadow of the Colossus (2005), both at Sony’s Japan Studio, and The Last Guardian (2016), completed after he left Sony and founded genDESIGN.2 Their rarity is part of the method – each is built around a single relationship refined for years.

Why does Shadow of the Colossus have only sixteen enemies?

Because the colossi are the levels: each is a climbable, living puzzle, and everything between them is deliberately empty travel that gives the player time to feel the sorrow of the hunt. The game subtracts towns, quests, and ordinary enemies so that its one act – felling something magnificent – carries full weight.

How does Ueda relate to Hideo Kojima?

They are the two poles of the auteur model in games, from the same generation: Kojima’s method is addition – cinema, spectacle, the director’s visible hand – while Ueda’s is subtraction, removing everything down to a single feeling. Together they mark the range of what personally authored games can be.



  1. ICO – 2002 Developer Interview, translated at shmuplations – Ueda on removing the girl’s animation details and map elements as needed (“If something felt unfinished or lacking, then I’d remove it”), the chair he cut rather than fixed, and his worry that a game with no stats or scoring would be accepted. 

  2. Fumito Ueda, Wikipedia – biographical scaffold: born 1970 in Tatsuno, Hyogo; oil painting at the Osaka University of Arts; animator at Warp; Sony Computer Entertainment from 1997; Ico (2001) and Shadow of the Colossus (2005); departure from Sony and genDESIGN; The Last Guardian (2016). 

  3. Game Developer, The birth of Ico, and Fumito Ueda’s visionary style – the animator-turned-designer path through Warp to Sony, and the role of his outsider’s perspective in Ico’s unconventional design. 

  4. Photographs: Fumito Ueda at E3 2016 by AI Dreamy (CC BY-SA 4.0); PlayStation 2 by Evan-Amos (public domain); Ueda at Gamelab 2017 by Gamelab Congreso de Videojuegos (public domain). Via Wikimedia Commons

관련 게시물

Design Philosophy: Hideo Kojima, The Director Who Ships Constraints

Hideo Kojima invented stealth games because his hardware could not draw bullets, then spent four decades smuggling cinem…

8 분 소요

Design Philosophy: Shigeru Miyamoto, The Player Is the Protagonist

Shigeru Miyamoto turned a childhood cave into Zelda, a rescue plot into Mario, and 'fun' into a testable engineering pro…

9 분 소요

Engineering Philosophy: Satoru Iwata

Satoru Iwata was a programmer who became Nintendo's president without ever stopping being a gamer -- technical mastery i…

22 분 소요