Plan connected tasks across discovery, learning, first use, everyday work, and leaving a product.
An experience includes the steps before and after a person operates a control. Plan how people find a task, understand its requirements, complete it, and recover when something goes wrong. Liquidify provides interface primitives; the application connects them to routes, data, and services.
Describe what the person needs to accomplish and how they will recognize completion. For example, “Create a saved filter and use it again” includes discovery, configuration, confirmation, and a return path. A successful button activation is only one part of that task.
Record the information people need at each transition. Keep names, selected items, and expectations consistent when moving between pages or temporary views. Do not require people to repeat information that the application can safely retain.
People may enter through a shared link, return to an unfinished task, or seek help before trying a feature. These stages organize design questions; they are not a compulsory sequence.
| Stage | Design question |
|---|---|
| Discover | Can people identify a relevant capability and its entry point? |
| Learn | Can they understand how a task works? |
| Try | Can they evaluate an action with clear consequences? |
| Onboard | Can they complete necessary setup and reach a first useful result? |
| Use | Can they complete recurring work and recover from interruptions? |
| Get help | Can they resolve a problem in context? |
| End use | Can they leave with a clear understanding of what happens to their work? |
Buy and Expand remain pending because their product offerings and service policies are unverified.
For each task, identify its starting state, available actions, pending state, outcome, and recovery path. Decide which information persists and where people return after cancelling or completing it. Make those decisions before choosing a modal or adding a progress indicator.
Use Patterns for interaction sequences and the component catalog for supported APIs. A component callback requests application work; it does not establish an account service, save policy, or support process.
Walk through the same task as a first-time visitor and a returning user. Include direct links, empty data, rejected requests, keyboard input, narrow layouts, and enlarged text. Verify that instructions match the visible interface and that completion messages reflect confirmed results.
Product-specific policies and services remain pending until their owners define them. Document a missing dependency explicitly rather than presenting a planned service as available.