Lessons on product sense, AI, the first mile experience, and the messy middle | Scott Belsky (Adobe)
Executive Summary
Scott Belsky joins Lenny Rachitsky to discuss product sense, empathy, first-mile experiences and feature focus. This selected coverage omits generative-AI, enduring-the-lows and later sections. His psychology shorthand is a design lens; company results are his account, unverified here. Untimed topics are editorial, not video chapters.
Key Takeaways
Build empathy before committing to a solution
Belsky says teams can become passionate about their preferred answer while missing the customer's actual problem. Understanding the person suffering the problem may lead to a different solution. Product sense starts with that understanding rather than only confident taste.
Make the first moments feel successful
His lazy, vain and selfish shorthand describes new users wanting quick progress, a good impression and early success. It is a product-design lens, not a universal psychological diagnosis. Reduce the learning burden before asking a user to care deeply about your mission.
Treat orientation and defaults as onboarding
He defines the first mile as more than a tour or signup sequence. It includes knowing where you are, how to get home, where to find help and what defaults appear. A functional flow can still leave a new person lost.
Revisit onboarding as the audience changes
Early customers may tolerate more friction than later, more skeptical customers. Belsky says a once-effective introduction may stop working for a new cohort. Review the experience for those arriving now instead of assuming past onboarding results settle it.
Optimize for the problems you want to have
He prefers customers reaching value and then asking for more capabilities over a broad launch that prevents them reaching value at all. For an MVP, prioritize obstacles on the path to caring. This is sequencing advice, not a reason to ignore safety or essential customer needs.
Remove brick walls and distracting options
He names signup, account connection and login as potential blockers. His Behance retrospective describes removing secondary features and seeing more core publishing activity. Those effects are his account, unverified here, and removal should be tested rather than assumed to help every product.
Preserve time to explore before narrowing
Belsky describes strong designers and product leaders exploring many possibilities, selecting a smaller set, getting feedback and refining further. The team then sees a few considered options rather than every first idea. This selected point does not cover his later generative-AI discussion.
The Conversation Breakdown
Build empathy before committing to a solution
⏱ Untimed topicBelsky says teams can become passionate about their preferred answer while missing the customer's actual problem. Understanding the person suffering the problem may lead to a different solution. Product sense starts with that understanding rather than only confident taste.
Make the first moments feel successful
⏱ Untimed topicHis lazy, vain and selfish shorthand describes new users wanting quick progress, a good impression and early success. It is a product-design lens, not a universal psychological diagnosis. Reduce the learning burden before asking a user to care deeply about your mission.
Treat orientation and defaults as onboarding
⏱ Untimed topicHe defines the first mile as more than a tour or signup sequence. It includes knowing where you are, how to get home, where to find help and what defaults appear. A functional flow can still leave a new person lost.
Revisit onboarding as the audience changes
⏱ Untimed topicEarly customers may tolerate more friction than later, more skeptical customers. Belsky says a once-effective introduction may stop working for a new cohort. Review the experience for those arriving now instead of assuming past onboarding results settle it.
Optimize for the problems you want to have
⏱ Untimed topicHe prefers customers reaching value and then asking for more capabilities over a broad launch that prevents them reaching value at all. For an MVP, prioritize obstacles on the path to caring. This is sequencing advice, not a reason to ignore safety or essential customer needs.
Remove brick walls and distracting options
⏱ Untimed topicHe names signup, account connection and login as potential blockers. His Behance retrospective describes removing secondary features and seeing more core publishing activity. Those effects are his account, unverified here, and removal should be tested rather than assumed to help every product.
Preserve time to explore before narrowing
⏱ Untimed topicBelsky describes strong designers and product leaders exploring many possibilities, selecting a smaller set, getting feedback and refining further. The team then sees a few considered options rather than every first idea. This selected point does not cover his later generative-AI discussion.
Core Frameworks & Ideas
First-mile experience
Review onboarding, orientation and defaults through the perspective of someone arriving for the first time.
Problems you want to have
Prioritize reaching value before later requests for additional capabilities.
Explore, narrow, test, refine
Preserve time for possibilities, then use feedback to develop a few strong options.
Actionable Next Steps
- ✓Observe a new user and note every point where they lose orientation.
- ✓List signup, connection and login obstacles before planning extra features.
- ✓Check whether later customer cohorts need a different introduction.
- ✓For each new feature, ask what can be removed or replaced and test the effect.
Notable Quotes
“to me, it's all about psychology.”
“I always tell them to optimize for the problems they want to have.”
“Only do the things that prevent people from getting to the point where they care enough to ask you for anything.”
The One Thing to Remember
Help a new customer reach value before adding all the capabilities they might ask for afterward.