First Mile Experience
A concept from Scott Belsky describing the first thirty seconds a new user spends with a product — and the design principles that follow from taking those thirty seconds seriously.
The core observation: new users enter in a particular psychological state. They are lazy (want immediate value, will not work for it), vain (want to look good, want to feel capable), and selfish (care only about their own needs, not the product’s intended use cases or long-term design). These are not character flaws; they are universal human conditions under the cognitive load of novelty.
The implication: the first mile of the user experience must be designed explicitly for this state — not for the sophisticated user who has lived with the product for months.
The asymmetry in how teams work
‘Most teams spend the final mile of their time building the product, considering the first mile of the customer’s experience using the product.’ Product teams invest heavily in features and depth because that is where their users’ conversations are richest, where the roadmap debates are most energetic, and where engineering effort is most visible. The first thirty seconds gets less attention precisely because it is brief and the users in that state are not yet in any feedback loop with the team.
Design implications
- Reduce the number of decisions required before the user reaches their first moment of value.
- Make the user look and feel capable immediately — the vain user needs to feel successful before they earn success.
- Do not require the user to understand the product before they get value from it.
- Remove friction between signup and the core action.
Relationship to onboarding
The First Mile Experience is narrower than onboarding (the full journey from signup to activation) and more specific. Onboarding frameworks typically address activation milestones over days or weeks; the First Mile focuses on the immediate sensory and cognitive experience of the first encounter.