Journal — Product
The difference between building a feature and building a product.
Features answer requests. Products answer jobs.
Requests are evidence, not instructions
A feature request tells you a job exists. It rarely tells you what the job actually is. The mistake is building the request literally and calling it progress. The better move is finding the job underneath and designing for it.
Coherence is the product
Products feel like products when every part agrees with every other part. Features feel like features when they don't. The invisible work of product is keeping that agreement intact as the roadmap grows.
The MVP is a promise, not a cut
A focused first version isn't a smaller product. It is the whole product, expressing its promise in the narrowest way that proves the job. That distinction is what separates a launch from a demo.
A product is a promise held together by a system of decisions.
Related Work
Next Article
Studio