Participant studies
Add process tracing and cognitive tasks
Collect interpretable timing and task-performance diagnostics without invasive surveillance.
The basic idea
Process data should be proportional to the scientific question. Stage duration, focus loss, response latency, trial accuracy, and false starts can test attention or cognitive load without capturing raw keystrokes, cursor trajectories, network identity, or device fingerprints.
After an AI interaction, run five choice-reaction trials and compare browser-timed response latency and accuracy across council and solo-AI conditions while retaining focus-loss counts as a sensitivity diagnostic.
How to do it
- 1
Choose simple reaction time when speed alone matters or choice reaction when speed and response selection matter.
- 2
Use enough trials for a stable summary without making the study exhausting.
- 3
Treat browser timing as client-recorded and inspect device or environment sensitivity in analysis.
- 4
Export raw trials and report exclusions, trimming, and aggregation rules.
What to watch for
- Browser and device differences add measurement noise.
- Focus loss has many benign causes and should not be treated as proof of inattention.
- Do not add invasive tracking merely because the browser permits it.
What a useful result looks like
The study exports trial-level latency, accuracy, false starts, stage events, and privacy-preserving focus diagnostics tied to participant and condition.