ROI Dashboard

“Are these trustworthy?” shouldn’t be a question when you’re showing your customers the analytics and balance of their ROI influenced by your company, but when it happens, instead of making it just “simpler”, you must give them the whole picture and drilldowns options to connect all the dots, to make it a whole that answer all their questions.

Company:

DRIFT

Role:

Product Designer, UX Researcher

Date:

Oct 2023

Tools:

Figma, GreatQuestion, LogRocket

Conversation summary UI

Trust the data, trust the company

Since detecting a significant downgrade on the visits in the Reporting section of Drift’s Management Platform and the increase of tickets for Customer Support related to Pipeline and Revenue reports, we decided to research more about the core problem.

Inaccurate or unreliable data can lead to poor decision-making, financial losses, and compromised business integrity.

Old chat data versions UI
Old chat data versions UI
R E S E A R C H
R E S E A R C H

We might empathize with our customers, understand their workday and how did they use and expected from our platform, also if they didn't trust our data, how did they find the right information they need for their daily basis and reports?. After multiple rounds of discovery calls, we figure out their main pain points , information architecture and other back-end problems that we might be facing by updating this section.

“I’d figure out my own way to make the reports work for what I need, but something that still not clear to me is how Drift is helping us to close the deals. Sometimes the people just came into our website and talk with the bot but other times I manually enter the information of potencial customers in Salesforce”
“I’d figure out my own way to make the reports work for what I need, but something that still not clear to me is how Drift is helping us to close the deals. Sometimes the people just came into our website and talk with the bot but other times I manually enter the information of potencial customers in Salesforce”
“Obviously I care about the ROI but I need more specific data to justify to my manager Drift’s integration and the bot costs”
“Obviously I care about the ROI but I need more specific data to justify to my manager Drift’s integration and the bot costs”
P A I N · P O I N T S
P A I N · P O I N T S

B A C K - E N D

Unreliable information, the information had different amounts and metrics across the platform.

A R C H I T E C T U R E

Lack of information’s traceability / drilldowns to find the origin of the data and Drift’s impact.

U X · D E S I G N

Complex UI not user-centered that also didn’t follow the new Design System.

Design challenges

How might we empower our users to trust our data?

How might we create a cohesive experience for our users?

How might we design a solution that also aligns with our DDS?

Design challenges

How might we empower our users to trust our data?

How might we create a cohesive experience for our users?

How might we design a solution that also aligns with our DDS?

Design challenges

How might we empower our users to trust our data?

How might we create a cohesive experience for our users?

How might we design a solution that also aligns with our DDS?

Design challenges

How might we empower our users to trust our data?

How might we create a cohesive experience for our users?

How might we design a solution that also aligns with our DDS?

·

My biggest challenge during this project, was to give our users the guarantee that the information we’re showing them is trustworthy and all the same across the platform.

To achieve this, we had to close the gap between diverse stakeholders that had different perspectives of the problem and the solution. I achieved the moderation of multiple dialogues and brainstorm session between the team to finally align in to a MVP proposal: Redesigning the dashboard and fuse the current 3 pages (Pipeline, Sales cycle, Closed won) into once that we’re named “Opportunities”.

·

My biggest challenge during this project, was to give our users the guarantee that the information we’re showing them is trustworthy and all the same across the platform.

To achieve this, we had to close the gap between diverse stakeholders that had different perspectives of the problem and the solution. I achieved the moderation of multiple dialogues and brainstorm session between the team to finally align in to a MVP proposal: Redesigning the dashboard and fuse the current 3 pages (Pipeline, Sales cycle, Closed won) into once that we’re named “Opportunities”.

·

My biggest challenge during this project, was to give our users the guarantee that the information we’re showing them is trustworthy and all the same across the platform.

To achieve this, we had to close the gap between diverse stakeholders that had different perspectives of the problem and the solution. I achieved the moderation of multiple dialogues and brainstorm session between the team to finally align in to a MVP proposal: Redesigning the dashboard and fuse the current 3 pages (Pipeline, Sales cycle, Closed won) into once that we’re named “Opportunities”.

·

My biggest challenge during this project, was to give our users the guarantee that the information we’re showing them is trustworthy and all the same across the platform.

To achieve this, we had to close the gap between diverse stakeholders that had different perspectives of the problem and the solution. I achieved the moderation of multiple dialogues and brainstorm session between the team to finally align in to a MVP proposal: Redesigning the dashboard and fuse the current 3 pages (Pipeline, Sales cycle, Closed won) into once that we’re named “Opportunities”.

V I S I O N · A L I G M E N T
V I S I O N
A L I G M E N T

A T T R I B U T I O N

Critical for multiple reasons. Primarily, it allows businesses to understand the source and effectiveness of their marketing efforts, enabling them to allocate resources more efficiently and optimize their strategies for better return on investment.

It was an issue that we didn’t focus at the beginning, after the research became a key feature that must be in the redesign, and the impact of it, change completely the initial idead that we had.

B A C K · E N D

As a team, we worked together to understand what’s happening and we finally figure out that the break point was in our Salesforce API, causing a discrepancy in the data. Some of the reasons were:

01 · SYNCHRONIZATION ISSUES
If the backend and frontend do not synchronize data properly, it can lead to inconsistencies. This might happen due to network delays, caching problems, or missed updates.

02 · API MISMATCHES
Differences in API versions or incorrect API calls can result in the frontend displaying outdated or incorrect data. Inconsistencies in the data structure returned by the backend can also cause frontend display issues.

03 · ERROR HANDLING
Improper error handling in either the frontend or backend can result in partial updates or data losses. For example, if the frontend fails to process an error response correctly, it might display incorrect information.

As a team, we worked together to understand what’s happening and we finally figure out that the break point was in our Salesforce API, causing a discrepancy in the data. Some of the reasons were:

01 · SYNCHRONIZATION ISSUES
If the backend and frontend do not synchronize data properly, it can lead to inconsistencies. This might happen due to network delays, caching problems, or missed updates.

02 · API MISMATCHES
Differences in API versions or incorrect API calls can result in the frontend displaying outdated or incorrect data. Inconsistencies in the data structure returned by the backend can also cause frontend display issues.

03 · ERROR HANDLING
Improper error handling in either the frontend or backend can result in partial updates or data losses. For example, if the frontend fails to process an error response correctly, it might display incorrect information.

As a team, we worked together to understand what’s happening and we finally figure out that the break point was in our Salesforce API, causing a discrepancy in the data. Some of the reasons were:

01 · SYNCHRONIZATION ISSUES
If the backend and frontend do not synchronize data properly, it can lead to inconsistencies. This might happen due to network delays, caching problems, or missed updates.

02 · API MISMATCHES
Differences in API versions or incorrect API calls can result in the frontend displaying outdated or incorrect data. Inconsistencies in the data structure returned by the backend can also cause frontend display issues.

03 · ERROR HANDLING
Improper error handling in either the frontend or backend can result in partial updates or data losses. For example, if the frontend fails to process an error response correctly, it might display incorrect information.

As a team, we worked together to understand what’s happening and we finally figure out that the break point was in our Salesforce API, causing a discrepancy in the data. Some of the reasons were:

01 · SYNCHRONIZATION ISSUES
If the backend and frontend do not synchronize data properly, it can lead to inconsistencies. This might happen due to network delays, caching problems, or missed updates.

02 · API MISMATCHES
Differences in API versions or incorrect API calls can result in the frontend displaying outdated or incorrect data. Inconsistencies in the data structure returned by the backend can also cause frontend display issues.

03 · ERROR HANDLING
Improper error handling in either the frontend or backend can result in partial updates or data losses. For example, if the frontend fails to process an error response correctly, it might display incorrect information.

I N F O R M A T I O N · A R C H I T E C T U R E

I N F O R M A T I O N

A R C H I T E C T U R E

In order to understand the whole picture, we trace down the information and how they relate to other.

By displaying the information this way, we notice that we didn’t show enough information to make our ROI Report meaningful or relevant to our customers, which together with the unreliable data, make our reports useless. But now the next steps were clear enough to start working on a solution.

Old chat data versions UI
Old chat data versions UI
D E S I G N & P R O T O T Y P E
D E S I G N &
P R O T O T Y P E
U P G R A D E : A C T I V I T Y · T I M E L I N E
U P G R A D E :
A C T I V I T Y
T I M E L I N E

During the first rounds of user testings, we faced a new setback: the attribution. The platform was also not allowing our customers to customize the attribution parameters according to their internal directions, DRIFT have their own rules for it and they didn't align to our customer's most of the time.

Stakeholders were hesitant about allow our customers to customize them, so we had to find out a middle point were our users are able to easily understand what parameter we're using to categorize an opportunity as influenced, sourced or no attributed.

Here's the parameters that we define:

I N F L U E N C E D

When Drift’s bot or Sales Rep. chat with the customer, capture the contact and create the opportunity.

S O U R C E D

When the contact was manually created and Drift may or may not chat with the customer.

N O · A T R I B U T E D

The opportunity was created, contacted and closed outside Drift.

Conversation summary UI
I M P A C T
I M P A C T

After 2 and a half months of hard work, we launched successfully this redesign and sunset the old one.


In the first week of implementation, we detected a growth in the section usage in a 25% and after a month the increase of site visitors were 38%.


We also receive a really positive feedback with minor adjustments, mostly copy changes since we modify and stablished new directions for the berviage across the platform.

After 2 and a half months of hard work, we launched successfully this redesign and sunset the old one.


In the first week of implementation, we detected a growth in the section usage in a 25% and after a month the increase of site visitors were 38%.


We also receive a really positive feedback with minor adjustments, mostly copy changes since we modify and stablished new directions for the berviage across the platform.

After 2 and a half months of hard work, we launched successfully this redesign and sunset the old one.


In the first week of implementation, we detected a growth in the section usage in a 25% and after a month the increase of site visitors were 38%.


We also receive a really positive feedback with minor adjustments, mostly copy changes since we modify and stablished new directions for the berviage across the platform.

After 2 and a half months of hard work, we launched successfully this redesign and sunset the old one.


In the first week of implementation, we detected a growth in the section usage in a 25% and after a month the increase of site visitors were 38%.


We also receive a really positive feedback with minor adjustments, mostly copy changes since we modify and stablished new directions for the berviage across the platform.

N E X T · S T E P S
N E X T · S T E P S
N E X T · S T E P S
The answer of our customers to this redesign was so well received that now the reporting
section itself asked for a redesign and improvements in different features.

This project was fully implemented on January 2024.

Transform problems
into solutions.

Transform problems
into solutions.

Transform problems
into solutions.

© ILSE MORA · 2024

© ILSE MORA · 2024