how I think
The Product Lens
I apply product thinking to whatever I am learning. I go deep on a field, build something real in it, and show what changes when you treat it as a product.
- 01Learn the field deeply
- 02Build something real in it
- 03Look at it through the lens
- 04Share what I see
the six questions
Who is it really for?
A specific person in a specific moment, not a market or a persona deck.
What job are they hiring it to do?
Often not the job the field assumes. The gap is where the opportunity is.
What does "working" mean?
The measure, decided before building, in the customer's terms rather than the builder's activity.
What is the trade-off?
Every real decision gives something up. Naming it is how you know a decision was made.
What would make people rely on it?
Trust, fit with how people already work, and the moment it becomes the default.
What has to be true for it to win?
Why now, what is missing, who pays, and what would prove the bet wrong.
an example: security as a product
Security for a small business is usually sold as a service: an expert scans everything and hands over a long report. Look at it through the lens and it changes shape.
- Who it's really for: a five-person business owner, not a security expert.
- The job: "don't let me get hurt, and tell me in words I understand," not "scan everything."
- What "working" means: the top risks fixed within a month, not the number of findings.
- The trade-off: fewer, verified findings instead of an exhaustive, noisy list.
- What makes people rely on it: a plain-language fix plan that fits how an owner already works.
A service sells effort. A product sells an outcome the customer can see. That is the idea behind Cyber Agents.
I don't use the lens as a checklist. I reach for the one or two questions that matter most for the thing in front of me, whether that is AI, security or whatever I'm learning next.