[Image]
This experience sits at a handoff moment, where users finish a task and rely on the system to take it from there. People are trying to get data out of the product so they can analyze it, share it, or use it elsewhere. For the business, this moment supports trust in the platform’s reporting and data infrastructure, especially for teams that depend on exports to do their work.
We tested Customer.io’s broadcast data export flow, focusing on what happens after a user initiates an export. Participants were asked to imagine downloading data from a recent newsletter and respond to the interface and system message shown during that process. The test used Success, Comprehension, and Satisfaction to understand whether users could take the right actions, interpret what the system was telling them, and feel comfortable with the outcome.
These moments often hide small breakdowns that don’t look severe but can quietly erode confidence over time. When people hesitate or double-check, momentum slows and trust gets tested. Understanding how users experience this handoff helps teams spot where clarity holds and where reassurance matters most, especially in workflows that people repeat and depend on.
User Needs & Business Goals
This experience balances the user’s need for clarity and reassurance with the business goal of supporting reliable data access without slowing the system down. Users want to know their export worked and what will happen next, while the business aims to deliver data asynchronously in a way that still feels dependable and intentional.
Audience
This concept was tested with product and marketing professionals in the United States who regularly work with email or campaign performance data. Participants reviewed Customer.io’s broadcast reporting interface and were asked to imagine exporting data from a recent newsletter. They interacted with the reports view, initiated an export, and evaluated the confirmation message shown after the export was triggered.
User Needs
In this moment, users are checking that an action they just took worked and deciding whether they can move on.
-
The experience should clearly explain what is happening so users don’t have to guess or double-check (intuitive).
-
The message should feel trustworthy, signaling that the system is doing what it says it will do (reliable).
-
Users should feel confident that their data will arrive without extra follow-up or effort (secure).
-
The experience should respect the user’s time and allow them to move on quickly (efficient).
-
The message should answer the most important questions without requiring more digging (useful).
Together, these needs ensure that a short waiting moment doesn’t turn into uncertainty or unnecessary friction.
Business Goals
From the business perspective, this experience supports confidence in the product’s core data workflows.
-
Support Data Trust – Reinforce that exports are handled correctly and predictably.
-
Enable Continued Work – Allow users to move on to other tasks without waiting or babysitting the system.
-
Reduce Support Overhead – Minimize confusion that leads to questions about missing or failed exports.
-
Strengthen Product Credibility – Show that background processes are intentional and well communicated.
-
Encourage Ongoing Use – Make repeat exporting feel safe and routine rather than risky.
Together, these goals help maintain long-term trust in the platform while keeping teams productive and self-sufficient.
Choose Metrics to Test Your Data Export
This concept examines a data export handoff where users rely on the system to complete work in the background. A focused design stack of UX metrics was selected to reflect the key moments of action, interpretation, and reassurance in this experience. The metrics used were Success, Comprehension, and Satisfaction, each chosen to map directly to what users need to feel confident and move on.
Intuitive → Success
In this moment, users are trying to take the correct action to get their data out of the system. Success captures whether people can identify where to click and initiate the export without second-guessing themselves. It reflects how clearly the interface supports forward progress before the system takes over.
Reliable → Comprehension
Once the export is triggered, users need to understand what the system is doing and what will happen next. Comprehension measures whether the message communicates the state of the export in a way that makes sense. This metric captures how well the explanation reduces uncertainty during the wait.
Useful → Satisfaction
After reading the message, users form a quick judgment about whether the experience feels acceptable or frustrating. Satisfaction reflects that emotional response to the handoff. It captures whether the interaction leaves users feeling confident enough to move on or uneasy about the outcome.
Establish Hunches to Direct Your Testing
Starting with hunches helps teams name uncertainty before it turns into opinion. These assumptions clarify where confidence might break down and shape focused questions that testing can actually answer. Each hunch reflects a moment where users could hesitate, misinterpret, or lose momentum.
Example: Customer.io Data Export
<table xmlns="http://www.w3.org/1999/xhtml" style="min-width: 75px;"><colgroup><col style="min-width: 25px;"><col style="min-width: 25px;"><col style="min-width: 25px;"></colgroup><tbody><tr><th colspan="1" rowspan="1"><p>Hunch</p></th><th colspan="1" rowspan="1"><p>Question</p></th><th colspan="1" rowspan="1"><p>UX Metric</p></th></tr><tr><td colspan="1" rowspan="1"><p>Users might miss or hesitate on the correct action needed to export newsletter data, especially if export options compete with other report controls. This could slow people down before the system even starts working.</p></td><td colspan="1" rowspan="1"><p>Where would you click to download a file with this email data?</p></td><td colspan="1" rowspan="1"><p>Success</p></td></tr><tr><td colspan="1" rowspan="1"><p>Even after starting an export, users may be unsure whether the process is complete or still running. This uncertainty could lead to waiting, refreshing, or repeating the action.</p></td><td colspan="1" rowspan="1"><p>How well do you understand what this message is saying?</p></td><td colspan="1" rowspan="1"><p>Comprehension</p></td></tr><tr><td colspan="1" rowspan="1"><p>A delayed, asynchronous export might feel risky or inconvenient to some users. That feeling could shape whether the experience feels acceptable or frustrating.</p></td><td colspan="1" rowspan="1"><p>How do you feel about what this message is saying?</p></td><td colspan="1" rowspan="1"><p>Satisfaction</p></td></tr></tbody></table>
Together, these hunches aim to evaluate whether users can take the right action, understand the system handoff, and feel comfortable trusting the process to finish without their involvement.
Turn Hunches into Test Questions
Turning hunches into concrete questions keeps testing grounded in observable behavior and clear responses. Pairing each UX metric with a specific question type makes it easier to see where confidence holds and where it slips during the experience.
**Success (First-click test)**
Question type: First-click test
Example: Click where you would go to download a file with this email data.
**Comprehension (Likert scale)**
Question type: Likert scale
Example: How well do you understand what this message is saying?
**Satisfaction (Likert scale)**
Question type: Likert scale
Example: How do you feel about what this message is saying?
Calculate UX Metric Scores from User Feedback
This test examined Customer.io’s Data Export experience, focusing on the moment after a user initiates an export and hands the work off to the system. In this context, users are trying to confirm that their action worked and decide whether they can safely move on. The design stack included Success, Comprehension, and Satisfaction, combining behavioral and attitudinal signals to show both what people did and how they felt about it.
-
Very Good = 90% and above
-
Good = 70%–89%
-
Average = 50%–69%
-
Poor = 30%–49%
-
Very Poor = below 30%
**Success (77% — Good)**
Most participants were able to identify where to go to export the data, but some hesitation appeared when choosing the correct action. A small portion of users paused or looked for alternative paths before committing. This suggests that the path forward is visible, though not immediately obvious to everyone.
**Comprehension (95% — Very Good)** Participants overwhelmingly understood what the export message was communicating. People correctly interpreted that the export was processing and that delivery would happen later via email. This indicates the system state and next steps were clearly conveyed.
**Satisfaction (87% — Good)**
Reactions to the message were largely positive. Users felt comfortable leaving the screen and continuing their work, even if the export was not immediate. A few expressed mild uncertainty, but it did not dominate the overall sentiment.
[Image]
Taken together, the scores describe an experience that is clear and dependable, especially in how it explains what’s happening. The main tension shows up between understanding and follow-through. People know what the system is doing, but a small drop in confidence appears at the moment they hand control over and wait.
Click here to check out the raw survey data and UX metric scores for Customer.io’s product.
Draw Signals from Your Design Stack
Here’s how signals were surfaced from Customer.io’s Data Export test results by following five steps:
1. Focus on poorly scoring or imbalanced metrics
[Image]
The overall test score landed at 86% (Good). Comprehension was the strongest signal, while Success was the weakest by comparison. Most people understood what the export message meant, but a smaller group hesitated earlier when deciding where to go or what action would actually get them the file. Signal: Understanding is high, but moments of uncertainty still appear around follow-through and confirmation.
2. Identify patterns across metrics
[Image]
Comprehension and satisfaction reinforce each other. When people understood the message, they generally felt fine about waiting and moving on. The tension shows up between interpretation and action. Users grasp what the system is saying, but some pause when translating that understanding into confidence that everything is handled. This reflects a common UX tradeoff between clarity of explanation and confidence in outcome.
3. Determine if user needs are being met
[Image]
-
Intuitive: Met — Most users quickly understood what the message was telling them.
-
Reliable: Partially met — A few users looked for extra confirmation that the export would actually arrive.
-
Secure: Met — The process felt safe and controlled, with no signs of concern about data loss.
-
Efficient: Met — Users felt they could leave the screen and continue working.
-
Useful: Met — The message answered the main questions users had in that moment.
4. Compare outcomes to business goals
-
Support Data Trust: Supported — Clear messaging reinforces that exports are being handled correctly.
-
Enable Continued Work: Supported — Users felt free to move on without waiting.
-
Reduce Support Overhead: Partially supported — Small pockets of uncertainty could still lead to follow-up questions.
-
Strengthen Product Credibility: Supported — The experience feels intentional and considered.
-
Encourage Ongoing Use: Supported — Repeating this flow does not feel risky or confusing for most users.
5. Surface signals & establish a direction
Signals derived from the data:
-
Users clearly understand that exports are processed in the background.
-
Most people feel comfortable leaving the screen after triggering an export.
-
A minority still look for stronger reassurance about where the data will appear.
-
Confidence dips slightly when users move from explanation to outcome.
Direction based on business context:
[Image]
The evidence points toward an experience that is fundamentally clear but still sensitive to trust at the handoff moment. Small gaps in certainty can matter when users rely on exported data for downstream work. Maintaining confidence through this pause is key to keeping momentum intact.
This is a calm, functional experience that largely does its job. The dominant signal is clarity with a slight trust gap at the moment users hand work over to the system and wait.
