Speeding up bank data by 75%
company
Cardlytics (CDLX)
Role
Sr UX Designer / Researcher
Problem
Users (data scientists)were manually seeking out sources of truth when checking transaction data
Users were waiting (up to) 3 weeks for validation of their effort
project type
CDLX Service Design (Back Stage)
Desktop only
Outcome
Increased task efficiency by 75%
Decreased backlog items by 45%
Speeding up bank data by 75%
company
Cardlytics (CDLX)
Role
Sr UX Designer / Researcher
Problem
Users (data scientists)were manually seeking out sources of truth when checking transaction data
Users were waiting (up to) 3 weeks for validation of their effort
project type
CDLX Service Design (Back Stage)
Desktop only
Outcome
Increased task efficiency by 75%
Decreased backlog items by 45%
Speeding up bank data by 75%
company
Cardlytics (CDLX)
Role
Sr UX Designer / Researcher
Problem
Users (data scientists)were manually seeking out sources of truth when checking transaction data
Users were waiting (up to) 3 weeks for validation of their effort
project type
CDLX Service Design (Back Stage)
Desktop only
Outcome
Increased task efficiency by 75%
Decreased backlog items by 45%
During PI Planning I was responsible for running a prioritization exercise where all of our Design, Product, and Development teams (~7-8 people) would categorize our future endeavors.
My primary role was to make sure our users' needs were balanced with business and development goals as we determined a path forward.
During PI Planning I was responsible for running a prioritization exercise where all of our Design, Product, and Development teams (~7-8 people) would categorize our future endeavors.
My primary role was to make sure our users' needs were balanced with business and development goals as we determined a path forward.
During PI Planning I was responsible for running a prioritization exercise where all of our Design, Product, and Development teams (~7-8 people) would categorize our future endeavors.
My primary role was to make sure our users' needs were balanced with business and development goals as we determined a path forward.
I structured our research in two parts: first, understanding their daily lives (user interviews), and second, observing them clean transaction strings in real-time (contextual interviews). The output from these activities was shared, discussed, and organized into a (current state) journey map by all of the key stakeholders.
This exercise was crucial to get cross-functional agreement on the key pain points (and emotional response) in the experience. It also helps as a reference for future design reviews and critiques.
I structured our research in two parts: first, understanding their daily lives (user interviews), and second, observing them clean transaction strings in real-time (contextual interviews). The output from these activities was shared, discussed, and organized into a (current state) journey map by all of the key stakeholders.
This exercise was crucial to get cross-functional agreement on the key pain points (and emotional response) in the experience. It also helps as a reference for future design reviews and critiques.
I structured our research in two parts: first, understanding their daily lives (user interviews), and second, observing them clean transaction strings in real-time (contextual interviews). The output from these activities was shared, discussed, and organized into a (current state) journey map by all of the key stakeholders.
This exercise was crucial to get cross-functional agreement on the key pain points (and emotional response) in the experience. It also helps as a reference for future design reviews and critiques.
How did we prevent feature overlap and ensure each tool serves a distinct purpose? The solution came through a card sorting activity with our users.
From this exercise we were able to:
prioritize user needs statements for each product
create clear boundaries between overlapping tools
How did we prevent feature overlap and ensure each tool serves a distinct purpose? The solution came through a card sorting activity with our users.
From this exercise we were able to:
prioritize user needs statements for each product
create clear boundaries between overlapping tools
How did we prevent feature overlap and ensure each tool serves a distinct purpose? The solution came through a card sorting activity with our users.
From this exercise we were able to:
prioritize user needs statements for each product
create clear boundaries between overlapping tools
If you would like to see the entire case study, email me and let's schedule a walk through!
If you would like to see the entire case study, email me and let's schedule a walk through!
If you would like to see the entire case study, email me and let's schedule a walk through!