Day one, in public.
This is the build log. What's done, what's next, and the things I haven't figured out yet. It'll get longer as I go, and it will include the mistakes.
-
October 21, 2026
I picked a name
After a long list of options built around tea, chai, clubs, and product-market fit, I landed on Why That Product. It's a question, and "why" is what I'd ask a user and what I ask about every teardown. WTP is also short for willingness to pay, which is a nice accident.
-
October 21, 2026
I claimed the handles
YouTube, Instagram, X, LinkedIn, and an email inbox are set up under the same name, so you can find me in one guess. This site is the home base that ties them together.
-
October 21, 2026
I wrote the openers
Every series needs a first line people can recognize. I wrote the ones I'll start with, and one closing line I'll repeat every time: "That's the why. See you in the next product."
-
Coming up
The first teardown
One product, one screen, five questions. The goal is a video that makes someone look at an app they use every day a little differently.
-
Coming up
My first discovery calls
I'll talk to real people about real problems, record what I learn, and share the bad questions along with the good ones.
-
Coming up
An interview prep series
Short, repeatable practice on product sense questions, built around the three whys.
What I'm still unsure about
Learning in public means admitting these out loud.
Does the name read as product?
"Why that product" could sound like shopping reviews to a stranger. I'm testing whether the bio and first few videos make the product thinking obvious fast enough.
Teardowns or journey first?
I don't know yet which one people want more. I'll make both and watch what you actually stay for.
What should I teach?
I have a list of topics, but your questions should shape it. If you're stuck on something, tell me.
Help me answer one of those.
Tell me which product to break down, or what you'd like to learn. Your answer might decide what I make next.