Problems before features
A feature is a proposed answer. The work starts with the question: whose problem is this, how often does it happen, and what does it cost them today?
Writings on product thinking and strategy: how problems get framed, bets get made, and products earn their place.
Not a methodology, and not a framework to sell. Just the beliefs that keep showing up whenever a product decision goes well, or badly.
A feature is a proposed answer. The work starts with the question: whose problem is this, how often does it happen, and what does it cost them today?
Opinions are cheap and confidence is not evidence. Decisions get better when bets are small, observable, and honest about what would prove them wrong.
Shipping is an event. A product earning its place is a habit: watching what changed for the people who use it, and letting that change the next decision.
A few writings that set out how I think about problems, bets, and the distance between shipping something and it mattering.
All writingsA roadmap is a set of claims about why these problems, in this order, with these trade-offs. When it becomes a delivery calendar, the reasoning disappears and the promises take over.
Treating discovery as a stage before delivery assumes uncertainty is front-loaded. It isn’t. Discovery works better as a recurring spend that every cycle pays into.
Product work is a sequence of judgements, each one narrowing the next. Pick a stage to see what it asks of you, and the question that keeps it honest.
Signal
A signal is rarely a request. It is a support ticket that keeps recurring, a workaround somebody built for themselves, a metric that moved for reasons nobody can explain. The job here is to notice before you interpret.
Question to ask
“What did we actually see, before deciding what it meant?”
A small, deliberately unfinished collection of things that sharpen product judgement: books, writings, tools, and the occasional argument worth having.
Open the shelfTeresa Torres
The clearest writing anywhere on continuous discovery and opportunity solution trees.
Marty Cagan
Writing on empowered teams and the difference between discovering and delivering.
Lenny Rachitsky
Practitioner interviews and teardowns, useful for how teams actually operate.
Lenny Rachitsky
Long conversations with people who have shipped real products and can explain the trade-offs.
06 · Why this exists
“Most product failures are not failures of effort. They are failures of framing, of evidence, or of the courage to choose.”
This is a place to think in public about that gap: between the work of building and the work of getting the decision right. Observations from the practice of understanding products and the people who use them.
Why this publication existsThe reading list
One note when something new is published, plus the two or three things worth reading that month. Written by a person, sent to people.