Read this before starting any new product.
1. I don't start from market—I start from memory
If I can't recall a specific scene, I won't build it.
2. I only solve problems people have learned to endure
If users are already used to tolerating it, it's worth solving systematically.
3. There must be a counter-intuitive insight
If the answer is obvious, the product would already exist.
4. I can pinpoint exactly where users curse themselves
Not the system. Not others. Themselves.
5. I only solve the part of the chain I can think through clearly
I'd rather do 10% right than 80% "good enough."
6. AI should disappear, not be seen
Users don't need to understand tech. They need results.
7. My products don't educate
No teaching discipline. No teaching standards. No teaching growth.
If users need to be as diligent as you to use it well, the product shouldn't exist.
8. Payment happens at "I never want to do this again"
Not before hope—after regret.
9. I prioritize "action-based relief" over "cognitive change"
Action sells itself. Cognition needs long-term nurturing.
10. If I have to keep explaining "why it's useful"—I don't build it
Good products speak for themselves.
These ten rules aren't methodology. They're my bottom line.
Reading them before each build stops 80% of self-indulgence.
