TL;DR: Simplicity is a competitive advantage — and it erodes. Every product starts simple. The hard part isn’t achieving simplicity. It’s maintaining it as the org grows, users demand features, and competitors force expansion. Simple is sticky. Complex is forgettable. The drift toward complexity is the default state of every product team and almost no one fights it deliberately enough.

What it means

The best products feel obvious in retrospect. They do one thing well, and that one thing is immediately clear to a new user. This is not an accident of design — it’s a strategic choice that most companies abandon under pressure. The pressure comes from every direction: power users want more features, competitors add capabilities, and internal teams need to justify their existence by shipping something (messy-middle).

The paradox is brutal and worth saying out loud: the features that delight your most engaged users are often the same features that confuse your newest users. Pleasing the vocal minority of power users gradually makes the product hostile to everyone else. Growth slows. Activation drops. Word-of-mouth thins out. Nobody connects any of it to the complexity they’ve been adding because each individual addition seemed obviously correct in isolation.

The argument

“Simple is sticky.” Products that are easy to understand get recommended. Products that require explanation don’t. Word-of-mouth — still the most powerful growth channel that exists — depends on the recommender being able to explain what the product does in one sentence. Every feature you add makes that sentence longer and less compelling, which makes the recommendation less likely to happen, which kills the growth engine the founders thought they were boosting (messy-middle).

The first mile deserves 30% of your engineering hours. Most teams spend almost all their effort on features for existing users and almost none on the experience of a brand-new user’s first 30 seconds. This is exactly backwards. The first mile — signup, onboarding, the first moment of value — determines whether you get a user at all. A product that’s incredible at minute 30 but confusing at minute 1 will never get to show you minute 30. The user is gone (messy-middle).

Great products remove, not just add. The discipline of simplicity isn’t about freezing the product. It’s about relentless subtraction. Every feature addition should be weighed against the question: does this make the core experience clearer or muddier? The best product teams kill features as often as they ship them. Apple removing the headphone jack. Google keeping the search homepage empty for 25 years and counting. Basecamp shipping fewer features per year than competitors ship per quarter. These are acts of strategic restraint and they look like risks at the time and like genius in retrospect.

Connections to other frameworks. Amazon’s working-backwards-method enforces simplicity through the press release format — if you can’t explain it simply in a six-page PR/FAQ, you shouldn’t build it. Boyd’s ooda-loop favors simplicity because simpler strategies enable faster reorientation in changing conditions. Direction-setting (“own the developer workflow”) over goal-setting (“ship features X, Y, Z by Q3”) keeps the organization’s OODA loop tight (certain-to-win).

Simplicity also connects to counter-positioning. Some of the most lethal counter-positions are simplicity plays: In-N-Out vs. McDonald’s menu sprawl. Basecamp vs. enterprise project-management bloat. early Google vs. Yahoo’s portal strategy. ChatGPT’s text box vs. every “AI workflow” startup’s six-step wizard. The incumbent literally can’t simplify because their existing users and revenue depend on the complexity. The newcomer’s simplicity is the business model the incumbent cannot adopt without setting fire to its own P&L.

The erosion is inevitable. Here’s the uncomfortable truth almost no PM wants to face: no product stays simple forever. Markets mature, customer needs diversify, and the org accumulates people who need to ship things to justify their headcount. The question isn’t whether complexity will come. It’s whether you can manage its arrival deliberately — adding it on your own terms, through explicit mechanisms, with someone authorized to delete it again — or whether you let it creep in through a thousand small product-review decisions where everyone optimizes locally and the global product slowly becomes unusable (messy-middle).

The companies that manage this well treat simplicity as a constraint, not a phase. They make complexity a cost that must be justified, not a default that accumulates. They create explicit mechanisms — Amazon’s PR/FAQ, design reviews that ask “what would we remove?”, regular feature audits — to counterbalance the natural organizational drift toward more.

The clean modern example

ChatGPT’s interface is a single text box with a send button. That is the entire product surface for most users. OpenAI shipped GPTs, plugins, browsing, image generation, voice mode, advanced data analysis, custom instructions, memory, and search — but the first thing every user sees is still: text box, send button. They’ve added enormous capability without adding visible complexity, by hiding everything behind a conversation primitive. That’s the atomic concept doing the work: the simplicity isn’t in the feature count, it’s in the primitive the user has to learn.

Loose threads

  • Is simplicity a Power type that Helmer missed? Probably not — it’s more of a meta-strategy that enables other Powers. But it might be a variant of counter-positioning when used against complex incumbents.
  • The relationship between simplicity and moats is tricky. Simplicity itself isn’t a moat — anyone can copy a simple product. The moat comes from the organizational discipline of maintaining simplicity, which starts to look like Process Power.
  • Simplicity is a precondition for the hook-model: “doing must be easier than thinking.” If the action step requires cognitive effort, the habit loop breaks. Products that stay simple stay habit-forming.

What links here