Inside Kyle Gabler's Philosophy — Minimal Bones, Maximal Skin

Introduction

This site has written about the music of World of Goo, but never about its maker head-on. Kyle Gabler built World of Goo (2008), the physics puzzle of stacking sticky goo balls into towers, and Human Resource Machine (2015), where you hand office workers pseudo-assembly instructions. Rather than pure puzzles, he starts from a 'toy' - something simply fun to touch - and then loads a puzzle onto it. That habit of hand has long drawn me in.

Why now? Gabler is a low-output designer who rarely explains his craft at length. But he left one legendary text: 'How to Prototype a Game in Under 7 Days' (source ↗, Gamasutra 2005), co-written with three grad-school peers. Read that alongside his few interviews and a remarkably consistent design stance emerges. This piece traces that consistency using only his own words.

Background: from '50 games' to World of Goo

Gabler is an American designer out of Carnegie Mellon's Entertainment Technology Center (ETC), where he co-founded the Experimental Gameplay Project. Its goal was to build fifty experimental games in one semester, under just three rules: each game made in under seven days, each made by exactly one person, and each built around a shared theme like 'gravity,' 'vegetation,' or 'swarms' (source ↗, Gamasutra 2005).

One of those fifty was Tower of Goo. 'Tower of Goo was downloaded over 100,000 times within months of hitting the net,' the essay reports (2005). Building on it, Gabler left EA, formed 2D Boy with Ron Carmel, and finished World of Goo in 2008. He later co-founded Tomorrow Corporation, releasing Little Inferno (2012), Human Resource Machine (2015), and 7 Billion Humans (2018) - small team, low frequency.

In Japan he is known mostly as the maker of World of Goo, or as the author of the 'make a game in 7 days' essay; the person behind them has rarely been discussed. Yet his statements, though few, are dense. Let us open that density one item at a time.

Philosophy: complexity is not necessary for fun

The first cross-cutting belief is that 'Complexity is Not Necessary for Fun' (source ↗, Gamasutra 2005). The essay notes that humanity has entertained itself for millennia with variations on 'a ball and a flat surface,' and that simple cores like Tetris and Pac-Man keep being reused for decades. Lens flare and bump mapping, they argue, add no fun.

The stance holds a decade later. Of Human Resource Machine, Gabler says: 'The source material we're working with - computers and programming - is so naturally interesting and fun and well designed by really smart people decades ago, that we have a lot less work to do as game designers' (source ↗, Game Developer 2015). The idea is to borrow good structure that already exists.

The other pillar is that 'design is paramount' - art, engineering, and sound all exist only to serve the final design (Gamasutra 2005). The section heading 'Nobody Cares About Your Great Engineering' lays that priority bare. If I may indulge my habit of cross-checking dates: the 2005 assertion isn't contradicted by the 2015 'a lot less work to do' - it's continuous with it. Twenty years without a wobble is almost eerie.

Obsessions: toy first, then juice, then ownership

A recurring habit in Gabler's design is 'build the toy first.' Stand up the core mechanic as something with no win or lose state, just fun to touch: 'This toy should be the core mechanic of the game minus any goals or decisions. There is no win or lose state, just a fun thing to play with' (source ↗, Gamasutra 2005). World of Goo borrows masses joined by Hooke's Law; Little Inferno borrows time (and burning things); Human Resource Machine borrows the computer. Each time he turns a real-world system into a toy: 'This game continues the rich tradition of building games based on real life stuff' (source ↗, Game Developer 2015).

Adding 'juice' to that toy is another obsession. The essay defines juice as 'constant and bountiful user feedback,' and writes: 'A juicy game element will bounce and wiggle and squirt and make a little noise when you touch it. A juicy game feels alive and responds to everything you do' (Gamasutra 2005). That word 'juice' became one source of a design vocabulary many later developers inherited.

Then a 'sense of ownership.' The games with the highest replay value, they observed, were ones with creation or customization - make a tree, draw a house, build a tower, evolve a creature (Gamasutra 2005). World of Goo's 'build up' is exactly a game of the player making a structure. Toy, juice, ownership - this trio reads as the tic that runs through his work.

Failure and recovery: subtracting a story into being

Gabler does not hide failure - he builds it into method. 'Embrace the Possibility of Failure - it Encourages Creative Risk Taking,' the essay declares; 'failure is ok! That's what prototyping is for' (source ↗, Gamasutra 2005). The team proudly displayed 'utter failures,' like audio-only games.

The personal failure he recounts is writing World of Goo's story. 'I had a lot of trouble with the story at first.' Having only made story-less 5-to-10-minute games before, a nearly 10-hour game left him feeling he 'had no idea what was happening,' breeding 'insecurity and uncertainty.' Early versions, with big cutscenes and heavy dialogue, were 'a mess!' (source ↗, GameCritics 2008).

The recovery was, characteristically, subtraction. 'The more I removed the story, and implied things instead of explicitly stating them, the more satisfying it became. That's why the cutscenes are all very short, and almost all dialogue is optional and oblique' (GameCritics 2008). He made a long-form story work by cutting rather than adding. It is telling that 'complexity is not necessary' resolved a problem in the entirely different domain of narrative in the very same shape.

A design dilemma: authorship vs. marketability

There is a dilemma he explicitly calls a set of 'hard lessons': balancing intentional obscurity (authorship) against being easy to describe (marketability). Little Inferno 'appeared (intentionally) to be a silly fireplace simulator on the surface, but with a dark story brewing in the background, and with an abrupt change near the end - none of which we could talk about without spoiling' (source ↗, Game Developer 2015). As a result it was very hard to promote.

That reflection changed his approach for Human Resource Machine. 'Human Resource Machine, in comparison, is fun and easy to discuss! There are no real secrets or mystery, just a series of really good puzzles' (Game Developer 2015). 'We learned a lot of hard lessons about how a game's design affects your ability to promote it' (ibid.) - the sentence carries the visible marks of a designer torn between authorship and commerce.

The other is accessibility versus the seriousness of the material. 'Beginners and non-programmers can get really scared of the idea of programming - so we've put a lot of work into making the game, and everything surrounding the game, simple and accessible' (Game Developer 2015). Keeping a genuinely assembly-like structure while making it un-scary - he says he walked that thin line. To avoid speculation: these two are the dilemmas he actually spoke about.

Influences: Piazzolla, mentor Schell, and contemporaries

The influences he admits are modest. First, music. The idea for Tower of Goo arrived while he walked home listening to the opening of Astor Piazzolla's 'Tango Apasionado.' 'Here's a case where an initial emotional target basically wrote the entire game' (source ↗, Gamasutra 2005). He also notes he swapped the final music for Piazzolla's more upbeat 'Libertango.'

His mentor was Jesse Schell, the project's faculty advisor at ETC. Schell wrote, in the essay: 'I felt a bit like a gardener - I did a little watering and weeding, but the flowering was all up to them' (Gamasutra 2005). Gabler's method grew under a near-hands-off supervision of the creative process.

He also voices respect for contemporaries. Discussing Human Resource Machine, he named Zachtronics' TIS-100 as one he 'can't wait to play' and Manufactoria as one he 'loved' (source ↗, Game Developer 2015). He places himself within the lineage of turning programming into play. Extending beyond that into speculation is not Kizuki's way, so I'll keep the confirmed influences to these three strands - music, mentor, and contemporary peers.

Kizuki's reading: a subtractor who also piles it on

From here on is my reading, Kizuki's - offered not as fact but as a step beyond his own words. What runs through Gabler, I read, is subtraction: cut complexity, cut story, cut the engineer's vanity. What is striking is that he is simultaneously an evangelist of juice - of near-excessive feedback. He is a subtractor who also piles it on. I read the two not as contradiction but as division of labor: pare the structure to the bone, then flood its surface with tactile pleasure. Minimal bones, maximal skin. In World of Goo, trimming the story while making goo balls bounce and giggle was exactly that division at work. And his sparse output looks, to me, like a consequence of this aesthetic - deciding what to cut takes far longer than deciding what to add.

Closing: where to start

To get to know Gabler, start with World of Goo. The pleasure of the toy, the juice, and the afterglow of a story cut down - every element in this piece is packed into that one game. Then move to Human Resource Machine, where the same designer applies 'borrow a real-world system' to programming.

For a related thread, Zachtronics' Zach Barth (covered on this site), whom Gabler himself respects, is close by. Barth, who 'sets down honest problems,' and Gabler, who 'loads a puzzle onto a toy that's fun to touch' - reading these two ways of turning programming into play side by side makes a fine contrast. Pour a cup of hot bancha and begin with the 2005 essay.

Sources

Primary sources cited in this article (all signed or spoken by Kyle Gabler):

・Gamasutra, "How to Prototype a Game in Under 7 Days," 2005 (co-authored by Kyle Gray, Kyle Gabler, Shalin Shodhan, Matt Kucic; Gamasutra 2005)

・GDC Vault, "How to Prototype a Game in Under 7 Days" (the authors' GDC talk behind the essay above)

・GameCritics, "Interview with World of Goo developer, 2D Boy" (interview with 2D Boy's Kyle Gabler and Ron Carmel, 2008-11-04)

・"Why a World of Goo dev made a puzzle game about programming humans" (interview with Kyle Gabler, Game Developer / formerly Gamasutra, 2015-06-12)