Do Not Start With the Product
The product is not the starting point. Human difficulty is.
Start With the Human — Do not begin with the product. Begin with the person.
Features often appear before problems
Many products begin with something already in the maker’s head: a new technology, a trending feature, a competitor launch, or simply the feeling that “we should add something.”
At that point, the product is no longer looking for a problem. It is looking for justification.
A feature looking for a problem is still a problem.
“What can we build?” is not the first question
Technical possibility is seductive. It makes teams ask what a technology, model or framework can do.
But the ability to build something does not automatically make it something people need.
Technical possibility is not human necessity.
Product should begin with a person trying to do something
Before product, there is a human intention: someone trying to complete, understand, share, decide or protect something.
When that intention is clear, product finally has a real anchor.
Start with the human trying to do something.
A worthwhile problem must exist before the solution
If a solution appears first and the team later searches for pain points to justify it, everything is interpreted through the thing they already want to build.
When the problem is understood independently, the answer may be a feature, a new flow, a process change — or no new build at all.
A real problem remains real even when your favorite solution disappears.
Human difficulty is the source material of product
Where do people lose time? What do they repeat? What must they explain again? Where do they lose clarity or control?
These frictions are the real raw material of product thinking.
Product begins where unnecessary human difficulty becomes visible.
Not every inconvenience deserves a product
Some friction can be solved by clearer language, better defaults, removal, light automation or process change.
If every difficulty automatically becomes a feature, the product grows while the human burden may not shrink.
Not every problem deserves more software.
Product should appear only after the problem is clear enough
Observation first. Then behavior. Then friction. Clarify need. Choose principle. Only then move toward system and product.
This order creates discipline so solution does not outrun understanding.
Human → Behavior → Friction → Need → Principle → System → Product.
To me before I decide to build something
If I become excited about a new idea, I want to ask: who is struggling, with what, and what are they actually trying to do?
If I cannot answer, maybe I do not lack a product. I lack understanding.
And if understanding reveals that nothing new needs to be built, that can still be a good product decision.
Do not ask what else we can build. Ask what no longer needs to be difficult.