My work at ThoughtSpot

ThoughtSpot is an AI-powered analytics software company based in Sunnyvale, CA. Their mission is to “create a more fact-driven world with the easiest-to-use analytics platform.

I served as a UX Writer on their content team, working to distill complex data vocabulary and principles into clear, informative copy that could successfully guide data dummies (I say that being one myself) through the software. Have you ever tried to explain a Chasm Trap to a data nonprofessional? 😣

Tooltips

The image depicts the experience before my work: while “undefined” is incredibly helpful and chock full of helpful information, my goal was the provide accurate and succinct information about each column property.

ThoughtSpot’s AI-driven analytics software “should be as intuitive as your favorite consumer app”, according to their mission statement. Users can leverage natural language, like a Google search, to explore their company’s data.

To make your data searchable, you need to first configure your data into tables, which naturally contain columns. These columns have specific properties, which any data scientist could define for you.

But with usability as a guiding principle, it’s important to have helpful microcopy accompanying the data configuration process. Thus, I wrote tooltips that define/describe column properties when users hovering over them.

Challenge

Provide succinct microcopy for tooltips that accurately describes the properties and configurations of columns in ThoughtSpot users’ data tables.

Audience

Mostly data scientists and data managers, but with the goal of being able to break through to the most novice of data users.

Approach

  • Use language that is approachable and understandable, while simultaneously describing the column property with razor-sharp accuracy

  • Implement ‘action-first’ language that describes what the column property does and how it affects that rest of the table

  • Make tooltips consistent in syntax, length, and depth of information

  • Use as many common words as possible to keep the cognitive load low

  • When possible, give users instructions on how to interact with the column property

Pardon the unceremonious presentation! I’m working on getting screenshots of my work in context, but hopefully this gives you an idea of my approach and execution.