All issues
Ship Notes · SN #02·4 Jan
Saying no to scope
Most product delays aren't technical — they're decisions that never got made. A couple of notes on keeping scope honest.
1. Every feature has a tail
The build is the cheap part. Each feature carries support, docs, edge cases and a maintenance cost that compounds forever. Before adding one, ask whether you're willing to own it in two years. If not, don't ship it.
2. Default to the smaller version
When a feature could be big or small, ship the small one and watch how it's used. Real usage is a better designer than any planning meeting, and the small version is far cheaper to undo.
Previous issue
SN #01 — Weekly engineering signal, without the noise