How to run the review
Pick one workflow
- Understand an account and its holdings
- Create or review a transfer
- Review a request or workspace change
- Find and understand an asset
- Get help when something is unclear
While you test
- Say what you expect before you click
- Use a realistic customer scenario
- Capture the exact step where something goes wrong
- Separate product problems from personal preferences
▸
For every issue: include the workflow, what happened, what you expected, the customer role affected, and a screenshot or recording when possible.
1. Set the context
Tell us whose job and workflow you are testing.
01
Which customer role are you testing as?
02
What customer workflow did you test?
03
What would success look like for that customer?
2. Work through the task
Focus on what happened, not general impressions.
04
Were you able to complete the workflow? If not, where did you get stuck?
05
What behaved differently from what you expected?
06
Was any terminology, instruction, or action unclear?
07
What information or functionality felt missing?
3. Check enterprise readiness
Look for gaps that would matter in a real customer environment.
08
Does the workflow reflect how enterprise customers actually work?
09
Are the roles, permissions, and approval steps appropriate?
10
Where could a user make a serious or difficult-to-reverse mistake?
11
What would prevent you from confidently demonstrating this to a customer?
12
What would prevent a customer from using this in a real pilot?
4. Prioritize the feedback
Help the product team separate blockers from preferences.
13
Which customer role or type of organization would be most affected?
14
Is this a blocker, a source of friction, or a preference?
15
What worked particularly well and should remain unchanged?
16
What is the single most important improvement we should make next?
17
Is there anything else we should know about the experience?
Feedback format
- Workflow attempted: the task you tried to complete
- What happened: the observed behavior
- What you expected: what you thought would happen instead
- Customer affected: role and organization type
- Severity: blocker, friction, or preference
- Evidence: screenshot or recording