Process ✦ 17 Jul 2026 ✦ 5 min read
Shipping in slices
A feature that is half live is not half done. It is a smaller, better thing.
The worst way to build is to decide everything first. Six weeks of decisions, a great plan, and then the code lands and half of it is wrong in ways nobody could have known.
Slicing it differently changes what that week is worth. A slice is a thing a person can actually use — not a layer, not a service, not a component in isolation.
The goal is not to ship the whole thing. The goal is to ship something that can be used, and then to be honest about what is missing.
What a slice is
If the slice cannot be used, it is not a slice. That rules out most of what gets called incremental delivery, which is usually a stack of layers waiting for permission to be a product.
A slice has a beginning and an end that a person can feel: the invoice can be sent, the post can be published, the file can be downloaded.
Being honest
The other half of slicing is being honest in the interface. A page that says it is still collecting data is better than a page that pretends to be finished.
Because the second one costs you the user's trust twice: once for the gap, and once for the surprise.
How we work
This is easier to do in a small team, where the person who knows the shape of the work is also the person writing it. The gap between what was planned and what was wanted shrinks to nothing.
I still plan whole features. I just do not build them in one piece.
Next note