Journal
Preparing for a fintech controls walkthrough
Datalinkbox field note · ~8 min
Walkthroughs go sideways when a product manager treats them as a feature tour. Your job as facilitator is to keep every screen tied to a control claim: who can act, what is blocked, what is logged, and who reviews the log.
Before the meeting
Send a one-page script: control objective, systems involved, roles required in the room, and the exact scenario you will execute (including a deliberate fail path). Ask engineering to prep a non-production environment that still mirrors privilege rules.
During the demo
Narrate the control, not the UI. Pause at decision points: “Here the second approver must be a different user.” Capture screenshots with timestamps and user IDs visible. If something cannot be shown live, schedule a follow-up instead of accepting a verbal assurance.
Afterward
Write the walkthrough memo the same day. Include who attended, what was demonstrated, and any gaps. Module 3 of the Assurance Lab practices this memo under time pressure because delayed notes quietly invent details.