← All issues

The Compound Years · Issue #14 · August 2026

One feature at a time

The hardest discipline in building anything is removing before adding -- because adding feels like progress, and removing feels like loss.

01The experiment

Cut Pi-Squared down to one core game loop before scaling installs.

Pi-Squared had three game modes at launch. Two were technically fine and nobody played them. I cut them. Installs picked up almost immediately because the one mode left was actually good -- and the App Store listing finally said one clear thing instead of three blurry ones.

02The lesson

Removing a feature and reading the metrics afterwards taught me more than adding one.

Reading about minimalism in product design did almost nothing for me. Cutting two features and seeing retention go up -- that built the dataset. Most product instincts are built that way: by deleting a thing you were proud of and being honest about the result a week later.

03The founder

Patrick Collison sold Stripe on the promise that seven lines of code was all you needed.

The original Stripe pitch was: drop seven lines of JavaScript into your site and you can accept payments. That was the whole demo. Patrick and John Collison stripped payments down to the one thing developers actually wanted to do -- and the discipline of that removal is still the brand.

04The mindset

Anyone can add. Working out what to take away is the harder skill.

I try to ask one question before adding anything new to a product, a page, or a calendar: what am I willing to take out to make room for it? If nothing, I usually do not add it. The constraint forces the trade-off out into the open.

05The question

What is one feature, page, or commitment you could remove this week?

Hit reply and tell me. I read every one.


Forward to one person whose product or schedule is doing too many things at once.

-- David