---
title: "Simplicity"
description: "Simplicity is a decision about what the product will not do."
canonical: https://moa.giglabo.com/strategies/simplicity/
locale: en
---

# Simplicity

> Markdown twin of https://moa.giglabo.com/strategies/simplicity/ — the same content as the HTML page, a fraction of the bytes.
> Every page of this site has one: append `.md` to any URL, or `index.md` to a directory URL.
> Site structure and the full page list for agents: https://moa.giglabo.com/llms.txt

Category: Ease · Role: Holds · Depth: 2

Gist: few points of failure, minimal design

## Moats

- [#13 Execution polish](https://moa.giglabo.com/moats/13/) (direct, depth 1 · Shovel) — Every part removed removes its bugs, its docs and its edge cases, and what remains looks finished because nothing is half-done. That polish is real, but a rival can match it in a release cycle.
- [#25 Habit](https://moa.giglabo.com/moats/25/) (direct, depth 2 · Excavator) — A tool that does one thing needs no decision to use; the decision-free reach, repeated, is the habit, and it outlasts the rival that later adds the same simplicity.

## Summary

Simplicity is a decision about what the product will not do. Every part left out takes its failures, its explanations and its support load with it — and leaves the user with fewer things to think about, which is what lets the product become automatic. As a finishing discipline it is shallow; as the thing people reach for without deciding it is deeper.

## How it works

The edge is subtractive. Each component removed takes its failure modes, its documentation and its interactions with every other component away in one move, so a product with five parts has fewer bugs, a shorter manual and a smaller support queue than one with fifteen — not proportionally, but combinatorially. A product that does one thing also needs no decision to use: there is one reason to open it and one thing to do, and that decision-free reach is what turns into a reflex.

The hard part is not building simple; it is staying simple. Every reasonable request, every enterprise deal and every roadmap review pushes toward adding, and a large rival is worse off here than you are: its sales team, its backlog and its customers all vote for more. That organisational asymmetry is where the edge actually lives. Against a rival who has the same restraint, though, a clean minimal build is cheap now, and the design alone lasts a cycle.

## Why it holds — or only takes

It holds, but stays shallow unless the product is used daily. Execution polish (#13, a shovel) is the direct output: the discipline of removing is the polish, and a product with no half-done parts looks finished — but a rival with taste digs that in months, and AI tooling now makes a clean minimal build cheap. Habit (#25, an excavator) is where it deepens: a tool with one obvious use gets used without a decision, and the reflex survives the arrival of a richer rival. The asymmetry that lasts is organisational — a large rival can copy the design but rarely the restraint, because everything inside it pushes toward adding.

## Do you have it

- You can say what the product is in one sentence, and that sentence is also the onboarding.
- The settings page is one screen or does not exist, and nobody has asked for more.
- The bug tracker is short because there are few interactions between parts to go wrong.
- Users who leave for a richer rival come back citing the clutter.
- Most feature requests are for things you already decided not to build, and you keep saying no.

## How to dig it

- Write the one sentence the product is, then remove every feature the sentence does not require.
- For each request, ask what it costs the users who did not ask; add it only when the answer is nothing.
- Kill options by choosing a default that is right for most; the choice is the product's job, not the user's.
- Keep the stack as small as the surface; fewer moving parts is the reliability the user feels.
- Audit the product every quarter for accretion and cut what crept in.

## How it erodes

- Every accepted request adds a part; the product drifts back to complexity one reasonable yes at a time.
- A rival ships equally minimal; the design is copyable in a cycle and AI tooling makes a clean build cheap.
- The baseline of what counts as simple moves, and yesterday's minimal reads as bare.
- Growth demands enterprise features — roles, audit logs, integrations — and each one is a seam.
- Simplicity without frequency never becomes habit, and a tool used rarely is replaced without regret.

## Solo, without capital

The best fit for one person: both moats are open to a solo builder, and restraint costs nothing but nerve. You can ship a one-purpose tool this quarter, keep it to one screen and let the small surface hold support near zero. What you cannot rely on is the polish holding, since it is under attack from AI-generated builds — the goal is to be the tool used daily before a rival matches the look. And small is not the same as simple: a rough small product has neither moat.

What the matrix says of its moats:

- [#13 Execution polish](https://moa.giglabo.com/moats/13/) — Solo: ✓ solo-reachable · Capital: ○ low · AI: ↓ under attack · Rent: ✗ not for sale
- [#25 Habit](https://moa.giglabo.com/moats/25/) — Solo: ✓ solo-reachable · Capital: ○ low · AI: → eroding · Rent: ✗ not for sale

## In nature, in business

Nature: —

Business: hammer, MUJI

- **MUJI** — MUJI sells household goods with the label and the ornament stripped off; the plainness and the resulting price are the whole offer.
- **Craigslist** — Craigslist has kept the same text-only listing pages since the 1990s and outlived a generation of better-designed rivals.
- **iA Writer** — iA Writer gives the writer a surface with almost nothing on it, and its users stay because there is nothing to fiddle with.

## Combines with

- [Reliability](https://moa.giglabo.com/strategies/reliability/) — Fewer parts is where reliability comes from; Simplicity and Reliability are one discipline seen from two sides.
- [Intuitiveness](https://moa.giglabo.com/strategies/intuitiveness/) — A small surface is the cheapest route to needing no manual; Intuitiveness is what simplicity looks like to a new user.
- [Efficiency](https://moa.giglabo.com/strategies/efficiency/) — Fewer parts cost less to build, run and support; Efficiency is the same subtraction measured in money.
- [Specialization](https://moa.giglabo.com/strategies/specialization/) — A product for one niche can stay small because the niche's needs are known; Specialization gives simplicity a reason to say no.

[This strategy on the map](https://moa.giglabo.com/strategies/?view=lanes&hl=simplicity)
[Map this combination](https://moa.giglabo.com/strategies/?view=lanes&hl=simplicity,reliability,intuitiveness,efficiency,specialization)

## Fights with

- [Completeness](https://moa.giglabo.com/strategies/completeness/) — The all-in-one product is the opposite decision; every capability Completeness adds is a new seam and a new thing to explain.
- [Versatility](https://moa.giglabo.com/strategies/versatility/) — General competence across many tasks needs modes and options; Versatility multiplies the parts that Simplicity removes.
- [Malleability](https://moa.giglabo.com/strategies/malleability/) — Customisation multiplies configurations, and every configuration is a point of failure; Malleability and Simplicity cannot both win.

[Map this tension](https://moa.giglabo.com/strategies/?view=lanes&hl=simplicity,completeness,versatility,malleability)

## Source

Strategy taxonomy © kepano (Steph Ango), paraphrased with attribution. Role and moat mapping © Moat Atlas. https://stephango.com/

## Related

- HTML version of this page: https://moa.giglabo.com/strategies/simplicity/
- Русский: https://moa.giglabo.com/ru/strategies/simplicity/
- Previous: Fun — https://moa.giglabo.com/strategies/fun/
- Next: Low-friction — https://moa.giglabo.com/strategies/low-friction/
- Atlas: https://moa.giglabo.com/
- Catalogue: https://moa.giglabo.com/moats/
- Calculator: https://moa.giglabo.com/calculator/
- Strategies: https://moa.giglabo.com/strategies/
- Site map for agents: https://moa.giglabo.com/llms.txt