Tasks and success criteria
Interactive tasks tell participants what to do on the prototype. Success criteria define how FromUsers evaluates whether a goal-based attempt succeeded.
Task types
Section titled “Task types”| Type | Participant experience | Typical success signal |
|---|---|---|
| Goal-based | Complete a defined outcome | Reach a screen or success URL, or meet configured criteria |
| Free exploration | Browse without a single required outcome | Time spent or completion of the exploration step |
| First click | Click where they would start for a prompt | First click location |
| Five-second | Brief exposure, then questions | Answers after the timed view |
| Preference | Compare options and choose | Selected option |
Write clear task instructions
Section titled “Write clear task instructions”Good instructions:
- State the goal in one or two sentences.
- Avoid giving away the exact click path unless you are testing comprehension of labels only.
- Mention constraints (desktop only, use search, do not use the back button) when they matter.
- Keep tone neutral. Do not coach the happy path.
Example: “You want to update your billing email. Find where to change it and save a new address.”
Define success criteria
Section titled “Define success criteria”For goal-based and website tasks:
- Open the task in Build.
- Choose how success is detected for your prototype type.
- For URL tests, set the success URL participants should reach.
- Preview and confirm detection works.
Success criteria should match a real completion state, not an intermediate page that people hit by accident.
First click and five-second setup
Section titled “First click and five-second setup”First click
- Show the prompt and the starting view.
- Capture where they click first.
- Optionally ask why they chose that control.
Five-second
- Configure the brief exposure.
- Follow with recall or impression questions.
- Avoid packing other interactive tasks on the same page.
Preference tasks
Section titled “Preference tasks”- Provide the options you want compared (designs or labeled variants).
- Ask for a choice and a short reason.
- Randomize order when bias is a concern (use logic or presentation options available in the builder).
Free exploration
Section titled “Free exploration”Use free exploration when you want qualitative browsing before structured tasks. Limit time in the instructions if you need comparable sessions, then follow with rating questions.
Mix with questionnaire content
Section titled “Mix with questionnaire content”Recommended pattern:
- Screener page.
- One or two interactive tasks.
- Difficulty and open-text follow-ups.
- Ending.
Too many tasks in one study increases drop-off. Prefer multiple shorter studies when scenarios diverge.
How results appear
Section titled “How results appear”Results Studio shows task-level outcomes, first-click data, preference distributions, and linked recordings when enabled. Failed tasks are as useful as successes when you review paths.
Related
Section titled “Related”Common questions
What is a success URL?
A URL that indicates the participant reached the goal on a website or URL prototype. FromUsers can use it when judging task success, especially with the website testing extension.
Do all tasks need success criteria?
Goal-based tasks should. Free exploration often does not. Preference and five-second tasks usually rely on the participant response rather than a destination URL.
Can I add questions between tasks?
Yes. Use standard questions for difficulty, confidence, or open comments between interactive tasks.