Optional retest · product mockup · Illustrative study · synthetic data
Workspace first. Or calendar first?
A product mockup tested with viewers, then retested after a suggested change. See what shifted at the same moment.
Illustrative product and creative research preview
Illustrative viewer artwork0:50 · Calendar access
Paused at the calendar request
“I wasn’t sure why it needed my calendar before I’d even seen the workspace.”
Synthetic participant feedback · P4
What to test next Researcher interpretation
Move the calendar request after the workspace preview and add one line explaining what access is used for. Re-run with the same task.
A study and report concept, not a verified production workflow. Optional pulse is secondary context, not evidence of an emotion. Confirm demo availability in the call.
The full onboarding evidence
Ten synthetic participants were asked to “create a workspace and connect a calendar”. The detailed example keeps observation apart from interpretation.
Illustrative study · synthetic data
Task: Create a workspace and connect a calendar
Single long form, calendar access requested before the workspace is shown
Selected moment · 0:50 · Calendar access
Researcher note: The pauses line up with the access request, and P4’s comment points to an unclear purpose. The pulse trend is consistent with effort or arousal, but on its own it cannot say which, or why.
- Task completed
- 6/10 · median 2:41
- Signal quality
- Good
Observed
- Task outcome6 of 10 participants paused for more than 10 s on the calendar access step; 3 scrolled back to re-read the plan.
- Participant comment
“I wasn’t sure why it needed my calendar before I’d even seen the workspace.”
— P4, after the session - Optional pulse trendP4’s estimated pulse trend rose by about 6 bpm over 15 s, then settled after the step.
- Signal qualityGood — Stable lighting, face in frame for the whole segment
Interpretation (researcher)
The pauses line up with the access request, and P4’s comment points to an unclear purpose. The pulse trend is consistent with effort or arousal, but on its own it cannot say which, or why.
What the team could do next
Move the calendar request after the workspace preview and add one line explaining what access is used for. Re-run with the same task.
Show example values for Variant A
| Time | Est. pulse (bpm) | Event / quality |
|---|---|---|
| 0:00 | 72 | Start |
| 0:05 | 72 | |
| 0:10 | 73 | |
| 0:15 | 72 | |
| 0:20 | 73 | Account |
| 0:25 | 74 | |
| 0:30 | 74 | |
| 0:35 | 75 | |
| 0:40 | 77 | |
| 0:45 | 79 | Calendar access |
| 0:50 | 80 | |
| 0:55 | 80 | |
| 1:00 | 78 | |
| 1:05 | 77 | |
| 1:10 | 76 | Workspace |
| 1:15 | 75 | |
| 1:20 | 75 | |
| 1:25 | 74 | |
| 1:30 | 74 | Done |
More on what this preview does with data: Privacy and sample data.
Side by side
What changed between A and B
| Measure | Variant A | Variant B |
|---|---|---|
| Design | Single long form, calendar access requested before the workspace is shown | Three short steps, workspace preview shown before calendar access |
| Completed task | 6 of 10 | 9 of 10 |
| Median time | 2:41 | 1:52 |
| At calendar access | 6 of 10 paused for more than 10 s | 2 of 10 paused for more than 10 s |
| Signal quality (P4) | Good — Stable lighting, face in frame for the whole segment | Partial — 0:38–0:44 excluded — participant moved out of frame |
Using a result like this
How a team could act on it
- 01
Start from behaviour
The clearest evidence is the task outcome: more people finished B, faster, and fewer paused at calendar access.
- 02
Read what people said
Comments explain the pause in A — the purpose of the access request wasn’t clear yet.
- 03
Use the signal as a pointer
The pulse trend helped locate the moment worth reviewing. It doesn’t, by itself, say what anyone felt.
- 04
Decide what to test next
A small study suggests a direction. Confirm with more participants before treating it as settled.
Have two variants you’re deciding between?
Book a demo