Recursive Evidence Arrays and Loop Test

Description

Participant × episode arrays exposing failure cascades (Mistake → extra clicks → frustration → lapse), re-run after a fix to confirm the mechanism itself changed.

Across the forward-thinking loop, qualitative rigour is kept auditable with 'triangulation hooks'. In Stage 1, a recursive evidence log captures the order a participant describes (e.g. Settings → Back → Markets) and flags expected loop points as risk loops. In Stage 2, an evidence array has rows as participants and columns for first click, path nodes, error code, quote, time to first click and SNR snapshot, sorted by first misroute node then error type so clusters emerge (e.g. a Mistake cluster at Notifications). A compact relationship sketch shows cascades such as an early mistake leading to extra clicks, a frustration spike and a later lapse at a timed OTP step. In Stage 6 the loop test re-runs the small array on a fresh sample and confirms the typical loop is absent or vastly reduced, alongside a QCA truth-table re-check. This verifies mechanism repair, not merely metric movement.

Attributes

Loss type
Community-proposed
Stage
Evaluation
Effort
Days

Steps

  1. During early interviews, record the sequence each participant describes and mark expected backtrack or loop points as risk loops.
  2. During diagnosis, build an evidence array: rows participants; columns first click, path nodes, Slip/Lapse/Mistake code, quote, time to first click, SNR snapshot.
  3. Sort by first misroute node, then by error type, and note clusters.
  4. Sketch recursive relationships between episodes (e.g. Mistake → extra clicks → frustration → lapse risk).
  5. After the fix, re-run the array on a fresh sample and check whether the loop is absent or vastly reduced.
  6. Rebuild the QCA truth table to confirm the previous sufficient path no longer holds, and write a concluding note on mechanism fixed or not fixed.

Sources

  • Vivek Gopinath (2025), Forward-Thinking UX Research Playbook: A Mixed-Methods, Decision-Ready Approach from Prediction to Validation

Also known as

  • Recursive relationship mapping
  • Qual triangulation hooks
  • Did we break the recursive loop?

Categories

  • Community-Proposed Frameworks