Verify v3
Revamp of our Verify feature in Playbooks
Verify v3
Revamp of our Verify feature in Playbooks
Verify v3
Revamp of our Verify feature in Playbooks
Verify v3
Revamp of our Verify feature in Playbooks
Verify v3
Revamp of our Verify feature in Playbooks
Verify v3
Revamp of our Verify feature in Playbooks
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Michael Murff - Data Science Product Manager
-
Brayden - Product Design Manager
​
Project Brief
Revamp the Verify feature within our Playbooks product.
​
What is the problem?​
​
There are 2 hovers for the information Verify provides and the information is not straightforward.
​
What is our goal?​
​
We needed to combine them and make the data easy to understand.
​
Feature Overview​
​
There are two parts to the Verify feature within Playbooks. One was showing the status of a number or email, whether we have verified that it was a good form of contact or not. The second part was not in production yet, but it was to show 3 data points to explain why the number/email is verified or not.
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Michael Murff - Data Science Product Manager
-
Brayden - Product Design Manager
​
Project Brief
Revamp the Verify feature within our Playbooks product.
​
What is the problem?​
​
There are 2 hovers for the information Verify provides and the information is not straightforward.
​
What is our goal?​
​
We needed to combine them and make the data easy to understand.
​
Feature Overview​
​
There are two parts to the Verify feature within Playbooks. One was showing the status of a number or email, whether we have verified that it was a good form of contact or not. The second part was not in production yet, but it was to show 3 data points to explain why the number/email is verified or not.
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Michael Murff - Data Science Product Manager
-
Brayden - Product Design Manager
​
Project Brief
Revamp the Verify feature within our Playbooks product.
​
What is the problem?​
​
There are 2 hovers for the information Verify provides and the information is not straightforward.
​
What is our goal?​
​
We needed to combine them and make the data easy to understand.
​
Feature Overview​
​
There are two parts to the Verify feature within Playbooks. One was showing the status of a number or email, whether we have verified that it was a good form of contact or not. The second part was not in production yet, but it was to show 3 data points to explain why the number/email is verified or not.
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Michael Murff - Data Science Product Manager
-
Brayden - Product Design Manager
​
Project Brief
Revamp the Verify feature within our Playbooks product.
​
What is the problem?​
​
There are 2 hovers for the information Verify provides and the information is not straightforward.
​
What is our goal?​
​
We needed to combine them and make the data easy to understand.
​
Feature Overview​
​
There are two parts to the Verify feature within Playbooks. One was showing the status of a number or email, whether we have verified that it was a good form of contact or not. The second part was not in production yet, but it was to show 3 data points to explain why the number/email is verified or not.
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Michael Murff - Data Science Product Manager
-
Brayden - Product Design Manager
​
Project Brief
Revamp the Verify feature within our Playbooks product.
​
What is the problem?​
​
There are 2 hovers for the information Verify provides and the information is not straightforward.
​
What is our goal?​
​
We needed to combine them and make the data easy to understand.
​
Feature Overview​
​
There are two parts to the Verify feature within Playbooks. One was showing the status of a number or email, whether we have verified that it was a good form of contact or not. The second part was not in production yet, but it was to show 3 data points to explain why the number/email is verified or not.
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Michael Murff - Data Science Product Manager
-
Brayden - Product Design Manager
​
Project Brief
Revamp the Verify feature within our Playbooks product.
​
What is the problem?​
​
There are 2 hovers for the information Verify provides and the information is not straightforward.
​
What is our goal?​
​
We needed to combine them and make the data easy to understand.
​
Feature Overview​
​
There are two parts to the Verify feature within Playbooks. One was showing the status of a number or email, whether we have verified that it was a good form of contact or not. The second part was not in production yet, but it was to show 3 data points to explain why the number/email is verified or not.
Reports 2.0
Revamp and moving our reports platform to new software
OVERVIEW
Roles
-
Me (Jade) - Product Designer
-
Neil - Product Design Manager
​
Project Brief
Moving our reports feature to PanIntelligence software and need to revamp the design and flow.
​
What is the problem?​
​
Our reports feature in Playbooks Manager doesn't provide enough information for our clients to use.
​
What is our goal?​
​
Provide a better experience for our clients when they need to look at the numbers for their team and their usage of Playbooks.
​
THE PROCESS
Map Out Flow
​
With PanIntelligence, they allow us to design custom reports for our clients to use. We initially built a reporting feature within our own product, but it wasn't as customizable as we wanted it to be for our clients. We wanted it to be bigger and better for clients to really dive into the data, such as finding out how well an individual team or even person is doing, or how many calls have been placed in a specific timeframe?
​
Our whole team started working on this project before I took over the rest of the design. We started out by mapping out the flow of how we wanted clients to be able to use this feature, and what graphs best showed the data they wanted to see.
​
Report Layout & Data​
​
Once we had an idea of what reports our clients would want overall, I wireframed each individual page. My manager and I came up with the questions they would want answered, and my goal was to figure out which graphs would answer the questions the best.
​
Revise & High Fidelity Designs​
​
After multiple critiques and revisions, we were confident in moving forward with high fidelity designs. It might seem confusing to do this when we are creating these reports through a program that generates them for us, but engineering still needed screens to know not only the UI for our specific reports, but the graphs that will be specifically generated on each page.
​
