a few notes on building products, after years of shipping and rewriting my own opinions.
quality is a verdict, not a claim
steve jobs pointed out once that the companies with the best reputation for quality were the quietest about it.
the insight is simple and a little uncomfortable: you don’t get to decide your product is good. your users do, after they’ve used it.
so the question stops being “how do we say we’re great?” and becomes “what will they feel the first time they touch this?”
ship the proof, not the adjective
premium, seamless, world-class, effortless - every one of them asks someone who doesn’t trust you yet to take your word for it. nobody does. they try it, then they judge.
behind every adjective is a thing you could actually build. build that instead, and the adjective becomes unnecessary.
good depends on who it’s for
“good” isn’t one thing. an internal tool wins on speed and clarity, a consumer app on delight, anything touching money on trust. know which one you’re building, and don’t borrow someone else’s definition of good by accident.
finish before you announce
a feature isn’t done when the happy path works. it’s done when you’ve walked the edges - the empty states, the slow days, the person using it in a way you didn’t expect.
build it until it can speak for itself, then let it.
bottom line
stop telling people your product is good.
build it so they decide that themselves.
similar write-up for reference: the web is the product, not the pitch