Note · 4 September 2026· 1 min read
Ship the smallest valuable slice
The smallest valuable slice is the one a real user can act on. Bigger than that is a promise, not a product.
Why we ship small
The smallest valuable slice is the one a real user can act on. Bigger than that is a promise, not a product.
We tend to ship the narrowest slice that proves one constraint against real data — usually telemetry, a real error path, or a real approval flow. If we can't find that slice, we don't have a project yet.
What we mean by 'valuable'
Valuable means someone can act on it. A dashboard that no-one opens is not valuable. An exception queue that a manager reviews weekly is.
What tends to go wrong
Two failure modes dominate: shipping a slice that's not actually narrow enough to test the constraint, and shipping one that's narrow but doesn't connect to a real user action. The fix for the first is more discipline; the fix for the second is more listening.