Optimizing AI

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

Product flow

Illustrative study · synthetic data

COMPARING When to ask for calendar access

CommonspaceSETUP 02 / 03

Connect your calendar

Bring your meetings into one place.

Calendar access
Connect calendar
Skip for now
Original fictional interfaceVARIANT A
Illustrative viewer artwork; not a study participant or signal readingIllustrative viewer artwork

0:50 · Calendar access

Paused at the calendar request

0:50
0:000:301:001:30
Example data · fictional

“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

70758085bpmStartAccountCalendar accessWorkspaceDone0:000:301:001:30
Variant A. Example data · fictional. Estimated pulse trend for participant P4 starts at 72 bpm, peaks at 80 bpm, and is 80 bpm at the selected moment, 0:50 · Calendar access. 6 of 10 participants completed the task. Signal quality: Good, Stable lighting, face in frame for the whole segment. Illustrative study · synthetic data.
Estimated pulse, P4 (optional signal) Selected moment

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
Estimated pulse for participant P4, Variant A, with task events. Illustrative study · synthetic data.
TimeEst. pulse (bpm)Event / quality
0:0072Start
0:0572
0:1073
0:1572
0:2073Account
0:2574
0:3074
0:3575
0:4077
0:4579Calendar access
0:5080
0:5580
1:0078
1:0577
1:1076Workspace
1:1575
1:2075
1:2574
1:3074Done

More on what this preview does with data: Privacy and sample data.

Side by side

What changed between A and B

Comparison of variant A and B. Illustrative study · synthetic data.
MeasureVariant AVariant B
DesignSingle long form, calendar access requested before the workspace is shownThree short steps, workspace preview shown before calendar access
Completed task6 of 109 of 10
Median time2:411:52
At calendar access6 of 10 paused for more than 10 s2 of 10 paused for more than 10 s
Signal quality (P4)Good — Stable lighting, face in frame for the whole segmentPartial — 0:38–0:44 excluded — participant moved out of frame

Using a result like this

How a team could act on it

  1. 01

    Start from behaviour

    The clearest evidence is the task outcome: more people finished B, faster, and fewer paused at calendar access.

  2. 02

    Read what people said

    Comments explain the pause in A — the purpose of the access request wasn’t clear yet.

  3. 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.

  4. 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