How to use the Onboarding Flow Planner.
Onboarding should ask for information when it becomes useful. Identify the smallest path to an actual result before adding optional configuration.
Make the workflow fit your task.
Identify the smallest sequence that produces a useful first result, then request information only when that sequence needs it. Separate required setup from optional preferences and define what successful completion looks like.
- What you provide
- Product activation goal and user constraints.
- What you get
- Step sequence with progressive information requests.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
New users need to compare one pair of files.
Completed example
Start with file selection and a sample comparison; introduce reusable settings after the first reviewed result.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should onboarding collect every preference before the first task?
Delay optional choices until they help the user. Early configuration should support the first useful outcome rather than postpone it.
Why do users complete setup but never experience value?
Check the transition from configuration to the first task. Add a clear example or action that produces a reviewable result.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑