Three Moderated Sessions Across the Two Primary Personas and One Scale-Comparison Participant
| Property | Value |
|---|---|
| 📅 Project | OmniRisk · Financial Workflow Dashboard |
| 🔖 Phase | Test & Iterate |
| 🛠️ Method | Moderated remote sessions · Think-aloud · Post-task survey |
| 👥 Sessions | 3 — hedge-fund analyst (Operational Optimizer) · fintech analyst (Scale Comparison) · FX trader (Strategic Decision-Maker) |
| 🎯 Coverage | Sequential CTA logic · AI Recommendation modal · Compliance override flow |
Three moderated sessions tested the sequential CTA logic, the AI Recommendation modal, and the compliance override flow against the three operator personas. The head of IT's systems vantage shaped research, but the prototype serves the people doing fund administration — testing was scoped to the operator personas who actually navigate the workflow.
Each session was moderated and think-aloud. Each participant was given task prompts without UI guidance. Sessions covered four core missions: First-Run Orientation, Sequential Workflow Orchestration, The Decision Moment, and The Compliance Override. No session participant saw another session's results before their own.
🖼️ Visual: See the Usability Testing Debrief visual embedded below — three full session cards with action, think-aloud quotes, observations, key insights, and post-task feedback for each participant, plus the four cross-session findings.
8 years experience · Session focus: Sequential Logic and Compliance Override Coverage: 2 tasks · 4 think-aloud quotes · 5 observations
The hedge-fund analyst navigated to the FX Repatriation widget and saw the three buttons: Fetch FCM, Run Analysis, and View Insights.
"Okay, getting started for the week. I see the three steps. 'Run Analysis' is grayed out, which makes sense — I haven't pulled the balances yet. I'm clicking 'Fetch FCM'."
He waited for the loading state to finish without frustration. The disabled states matched his mental model of the repatriation cycle. After the data populated and Run Analysis activated:
"Balances are in. Now the 'Run Analysis' button is active. Clicking that. I actually like that it forces this order — at my last fund, someone ran a macro on Tuesday's data on a Thursday and it caused a massive reconciliation break."
Sequential enforcement landed cleanly. The forced ordering read as orchestration matching real workflow dependencies, not as constraint imposed by the design.