Products are hypotheses
Every feature is a claim about what people will do. Treating it as a hypothesis is not a lack of conviction: it is a way to keep learning after launch.
About · The publication
I’m Shweta Sharma. I write about product thinking and product strategy: how problems get framed, how bets get made, and why some products earn a place in people’s lives while others quietly disappear.
01 · Why this exists
I started writing because the most useful conversations I’ve had about products were never really about frameworks. They were about a specific decision, the evidence behind it, and what somebody learned when reality disagreed.
Most product advice is written for the moment of certainty: the launch, the win, the retrospective where everything looks inevitable. The work itself is less tidy. It happens with incomplete information, under constraints, among people who want different things.
This publication is an attempt to stay with that messiness. Each piece takes one problem seriously: how to frame it, what evidence would change your mind, and what the decision costs. Some pieces are arguments. Some are notes from practice. None of them pretend to be a playbook.
The goal is not to sound certain. It is to become harder to fool, including by my own first answer.
02 · What I believe
Four convictions that show up, in some form, in almost everything published here.
Every feature is a claim about what people will do. Treating it as a hypothesis is not a lack of conviction: it is a way to keep learning after launch.
A strategy that does not say no to something is a wish. The interesting part is never the list of things you will do; it is what you are willing to give up.
Confidence is cheap to produce and expensive to be wrong about. Small tests, honest data and a written record of what would change your mind outperform certainty.
Ambiguity gets pushed downstream until it lands on someone with less context. Naming the problem, the trade-off and the decision is part of the work, not admin around it.
03 · How I think
Good product thinking is less a process to follow than a loop to keep running. The order matters less than the discipline of not skipping a step.
Start with the behaviour, not the request. What is actually happening?
Name who is stuck, at what moment, and what it costs them.
Make the trade-off explicit, then decide with the evidence you have.
Watch what changed, write it down, and let it revise the next call.
04 · What you’ll find
Start here