Teach a task through relevant instructions and examples that people can revisit.
Learning helps people understand a task before or while they perform it. Start with the outcome, explain the next useful action, and show how to recognize the result. Keep instruction close to the work it supports.
A familiar action may need only a clear label. An unfamiliar concept may need a short explanation beside the relevant control. Reserve a separate tutorial for a sequence that benefits from guided practice.
Explain product-specific decisions rather than teaching standard browser controls. For a saved filter, describe which records it includes and when it updates; there is no need to explain how to press every button.
Use a small, realistic task with an observable result. Explain whether the example changes sample data, a local draft, or a real account. Follow Try when people need a safe environment to practise.
Keep optional instruction skippable and easy to find again. Do not replay a dismissed tutorial at every visit. The application must decide how to store learning progress, associate it with an account or browser, and handle missing storage; Liquidify controls do not track this history.
Use the same labels in instructions and controls. Describe actions with input-neutral language such as “Choose Save filter.” Include the outcome in text so an illustration is not the only source of information.
For technical teaching material, use captures of the actual components and states. An image should support the task explanation rather than imply an unsupported variant. Keep detailed APIs and interactive examples in the component catalog.
Give the person a clear route into the task after the explanation. Use Onboard for required first-use setup and Get help for an interruption or error during work. Keep these purposes distinct so returning users can reach the information they need directly.