Time to value is how long a new user waits before getting a real result. The site uses it for quick first wins ("send a test email to yourself"), starting small (pick two tables, not all), and for its failures: empty states after a long permission flow, or setup steps that only a data team can complete.
Nielsen (1998), drawing on Carroll and Rosson (1987), describes the paradox of the active user: people skip manuals and tutorials because they want to get their task done now, so products must be useful before they are learned. The foot-in-the-door studies support starting small. Freedman and Fraser (1966) found people who first agreed to a small request were much more likely to agree to a larger one later, and Burger's 1999 review found the effect holds under some conditions and not others. NN/g's Kate Kaplan (2021) recommends using empty states to show status, teach and offer a next step rather than leaving a blank screen.
Most trial users decide within the first session whether the product is worth more effort. If the first screen after signup is empty or blocked on someone else's work, the paywall arrives before the value does.
How to use it
- Define the first useful result for each segment and remove or defer every step not needed to reach it.
- Fill empty states with sample data, a template, or one clear action that produces a result in under a minute.
- Make the first step small (connect one source, invite one teammate) and say that the rest can be done later.
Watch out
- Faking value with demo data the user cannot tell apart from their own creates a letdown when the real setup begins.
- Rushing to a quick win that is not the product's core value can lift activation numbers without improving retention.
