Test Library
Reduced go live time from 2 months to weekly.
Led design-engineering and QA collaboration to understand our capabilities, priorities of different teams and see what can be leveraged.
Background
Let's say you want a personal loan from Florence Bank, you will go to their site to apply, you will find this page.
This web application appears very simple at the surface, but it's much more complex as it is dynamic and driven by decisioning engine and policy.
Policy
Third Party Data
Drives the experience and decision
Third party Data
Input
Policy = a massive collection of logical expressions
Decision
Testing the product is basically adjusting input and checking if the decision is the intended one.
Business Problem
01
Clients can view only 2 end-to-end application flows using 2 test profiles provided in doc portal.
02
Lack of confidence and dependency on Amount for testing.
03
Even for seasoned testers, it takes multiple attempts and avg 25 mins to test the policy and build confidence.
04
A month to go live despite building being complete in days.
Solution & Impact
01
Out of the box test library to view end to end applications and test basic scenarios.
Business KPI
Go live frequency
Monthly
->
Weekly
UX Benchmark
Avg Test Time
25
mins
->
5
mins
02
Anticipating 1000s of test profiles being loaded via backend on MVP launch, included affordances for faster browsing and finding the right profile.
UX Benchmark
Finding Test Profiles
hours or days
mins
->
30
seconds
03
Edit test variables, track them visually. Progressive disclosure of information and complexity to manage learning curve.
UX Benchmark
Edit Time
OOTB Profiles
->
5-10
seconds
New Profiles - Credit
->
2.5
mins
New Profiles - Fraud
->
1
min
My role & responsibilities
Sole designer working with a team of 4 engineers and a PM.
Designed and carried out workshops to understand testing, policy, created proof of concepts to evaluate value and get stakeholders feedback, and buy-in.
Led design, engineering and QA collaboration to understand our capabilities.
Cross functional collaboration to understand priorities of different teams and see what tech developments can be leveraged.
Defined release scope for Testing Common Scenarios using OOTB Test Profiles.
Lessons
Only way to rapidly test and iterate on interaction design problems is to have fully functioning prototypes. We might thing we can test smaller pieces of interactions but when stitched together, these interactions affect each other in unimaginable ways.
The speed with which user is performing the tasks starts surfacing issues in the interaction design. It's very much like movie making.
This was one of the projects that I had to test and iterate quite a lot during build while playing with the components in storybook locally.
Reflecting back this would have been so much faster if we had something like Cursor.
Today I can easily test some of the hypothesis related to interaction by building working prototypes in Cursor.