Documents before impressions
Start with current provider documents: regional terms, account protections, fee schedules, order disclosures and withdrawal conditions.
HOW WE INSPECT / METHOD 01
A feature is only useful
when you can operate it.
Probe organises platform research around actions, consequences and exceptions. The aim is not to crown a universal winner—it is to make a specific workflow easier to inspect.
Actions before labels
Follow a task from entry to exit. A feature name matters less than whether previews, confirmations and controls explain the result.
Exceptions before averages
Inspect the new bank account, the crowded screen, the paused rule and the delayed notification. Normal cases rarely reveal the whole experience.
Balance before verdicts
Strengths and limitations belong beside each other. A high-level score should never hide the conditions attached to it.
THE INSPECTION SEQUENCE
Six passes through
the same platform.
- 01
Set the scenario
Define who the user is, what they want to do and which constraints matter. Without a scenario, almost any feature list can look convincing.
- 02
Confirm the account
Check availability, ownership model, protections and eligibility before comparing interface details.
- 03
Price the whole journey
Estimate the total cost around a realistic entry, holding period and exit—including conversion and account-level charges.
- 04
Rehearse the controls
Inspect previews, confirmations, editing, cancellation and interruption. Record what each action leaves active.
- 05
Trace the money
Follow funding and withdrawal stages, verification triggers, timing estimates and the point where a bank becomes responsible.
- 06
Write both columns
Document what worked and what created friction. Preserve qualifications instead of compressing them away.
PUT THE METHOD TO WORK