Designing for First-Run Versus Returning Users

Two users, one screen

The same screen is seen by someone opening the product for the first time, who needs to understand what to do, and by someone who has used it daily for a year, who knows exactly what they want. These two have opposite needs. The newcomer benefits from explanation, prompts, and guidance. The regular finds those same elements an obstacle between them and their goal. Designing a single interface for an imagined average user serves neither well.

The better frame treats first-run and returning use as distinct states the same surface moves through, rather than as a compromise to be split down the middle. The interface should present the guidance a newcomer needs and then let it recede as the person no longer needs it.

Guidance that fades

First-run guidance should be prominent when it is useful and absent when it is not. Tips, prompts, and explanatory text that help on the first few uses become noise once the person has learned the pattern, and an interface that keeps showing them treats every returning user as if they were new. Guidance that fades, triggered by first use and retired as competence is demonstrated, keeps the help available exactly as long as it serves.

• Show orientation prominently on first use, when it is genuinely needed.
• Retire guidance as the person demonstrates they no longer need it.
• Never make first-run help a permanent fixture for returning users.

Respect the returning user’s fluency

The returning user is the one who matters most over the life of the product, because they are the one who stays. Their experience is degraded by anything that assumes they are still learning: re-explaining what they know, prompting them through steps they have automated, or cluttering the path they take many times a day. The design should let a fluent user move quickly and quietly, with the scaffolding that helped them begin gone from view.