UX Writing: Empower Non-Data Scientists to Clean Data
Problem
Data Prep is part of Salesforce’s Analytics product that simplifies the complex task of cleaning data. We added a feature to reduce the cognitive overload of joining one dataset to another by letting customers select their main dataset and the dataset(s)-to-be-joined on the same screen. Previously, customers needed to know which datasets had relationships to the initial one they selected. In practice, they spent a lot of time searching through datasets to figure out which ones they could join. The recommended datasets feature takes out the guesswork by showing the relevant ones from which to choose.
Scope
Ensure our user base of non-data scientists can effectively clean data through providing context and brief explanations, while maintaining consistent technical vocabulary.
Stakeholders
Product management, design, engineering
Solution
Though I don’t have feedback on the tooltips specifically, based on discussions with the product manager and solutions engineers, customers are very appreciative of the feature and weren’t confused by an initial demo from product management.
Before
This panel displays when the user picks one of the recommended Salesforce objects to join.
The heading Select Columns (Account) is unclear.
The label Select right key for your join doesn’t provide much information and is sloppy text.
After
Preserves how the interface mimics the underlying database language, but adds more information.
Clarifies the relationships between the input and to-be-jointed objects by renaming the tab Related Objects.
Keeps the focus on objects across the UI by renaming the header with the name of the first selected object. “Selected Columns (Object Name)” was cluttered and unclear.
Process Details
I collaborate on product text with designers, engineers, product managers, and our UX writing review team in a Google Doc.
Engineers or designers sometimes write placeholder product text, which goes in the Current Text column. I write the Recommendation column.
The UX writing review team and I edit/discuss the recommended text via Google Doc comments. Together, we establish the final text, which goes in the Final Text column.
Conversation with engineer and product manager where I push to add further details in the UI.
Outcomes
From a solutions engineer: “Previously, I don’t think [Data Prep] did a terribly great job. Before, I really had to search. What is super nice now is how when you select a dataset, you can check for related Objects—that is gold!!! So, for a related join node, it finds the join keys automatically. That is SWEET. It’s so much better!!”