On this page
Start from the user’s reason for arriving
A new user usually has a purpose beyond learning the interface. Identify the first useful result and make its route visible.
Do not ask for every possible preference before the person understands why it matters. A short introduction can provide context, but it should not become a compulsory tour of features that will not be relevant until much later.
Explain a request where it is made
When information is needed, say what it supports and what will happen next. Keep optional choices recognisable.
A person should not have to leave the task to decode a label or discover whether an action can be reversed. Clear language is part of the product’s functionality, especially when the interface introduces a concept the audience may not already know.
Let an early mistake remain recoverable
The first attempt is a learning period. Give people a way to review an entry, correct a choice and understand an error without losing unrelated work.
Make empty states helpful rather than decorative. A good empty screen explains what belongs there and offers an appropriate next action, instead of leaving a new user to infer how the entire product is meant to work.
Review the first useful result
Observe whether people can reach the intended outcome and describe what they have done. The completion of a tour is not the same as understanding a task.
Use the questions and hesitations that occur in actual attempts to refine the next version. A clear beginning builds confidence through a useful result rather than a promise that familiarity will eventually solve the confusion.
