Defining Accuracy in Communication – Interpreting Beyond the Chart
She came in the room with great authority. She, a qualified interpreter, introduced herself while I watched, still a student and there only for support. Her signs were clear, crisp, and technically accurate. She conveyed what the medical provider said, navigating terms like tumor, malignancy, and benign. As quickly as she came, she left.
You can be technically right and still miss. My friend looked at me, lost and confused, not from the news, but from a lack of understanding. The words floated past, technical and without meaning.
What did she say?
And so, I was the one to break the news: they were looking for cancer. And, realization landed with a sharp jab.
Our dashboards are rarely this dramatic or life-altering. Our targets are farther away, rarely faces that we see. But, we still hunt for accuracy. Yet accuracy is more than a chart-level decision.
No, bear with me…
As interpreters, we learned numerous signs for concepts, finding 20+ ways to sign love, for example, or playing with idioms. Language is a proxy for our thoughts, which can encompasses all of our senses. The words we select may come pretty close, but they’re not always precise. And in the height of emotions, we may find no words meet our needs.
As interpreters, we debated about the use of words – was this sign better than that for this concept? We kept coming to the same answer no one likes – it depends. It depends on the context, the mood, the other words surrounding it, the place, and speakers themselves. Yes, we had to factor all that in to be accurate.
Accuracy beyond the chart
So, this is where we get to dashboards. We know our chart choices depend on various factors, such as the goal of the dashboard, the type (infographic, dashboard?), the story, the business environment, and the audience. This isn’t much different than interpreting. Except, we rarely consider our charts in relation to the dashboard.
Consider these:
OR
This difference is small, a matter of a minor chart change and some space. In the first, this dual axis is not synchronized, allowing profit to fill the full space. Some people argue this is the right way to show this chart. It emphasizes the how profit and sales dovetail – is the pattern the same? It has an unintended consequence, though, within the dashboard – it forces an extra bit of space at the end. The axes’ numbers are colored to give an idea which belongs where (some people would encourage going so far as to shade the entire area of the axis) and a legend is also needed. Some people might shade the numbers at the side in lieu of a legend. Within the context of the entire dashboard, the more we do, the more this one chart stands apart. Is this chart really worth all that attention? Is it that profound?
The second iteration looks at profit as part of sales. You can still see the dips, but they’re more understated as the axes are synchronized. We can use placement as a legend, telling people bigger things are sales and smaller things are profit. This allows us to recoup some space and explore this chart in relation to other charts.
Does one flow better to you?
Our audience looks at this differently than we do. Charts are highly abstract forms that rely on standard literacy (look ma, I can read!) and moderate numeracy skills (what do these numbers mean to me?). If that’s not enough, they ALSO require people to sift through the visual chaos. Depending on their exposure, this may all be too much. We spend all our time on this, kids. We obsess over nuances and love the complexity, just as writers love playing with words and artists push the medium.
People using this have a whole different approach to reading this.
- First pass view
- Digging deeper into parts
- Using to get info
I’m only going to look at the first part of this. Remind me and I’ll do more.
End User Perspective
Our users make a first pass judgement view. They try to answer the most important question within about 2 seconds: Is this thing worth my time? Just like with meeting people, first impressions matter.
Our unsynchronized view introduces a lot of complexity from the get-go. The jagged lines, parts where profit pops above sales, and dual acts a bit like that breathless person who rushes through hello and proceeds right into a tirade about the party. We have multiple legends, which end users love hate. In short, we’re not even past the top and we already need that martini.
Compare that to this:
When we communicate visually, that first look matters. Our end users immediately start translating clutter and complexity into calculations about how much effort and energy they have to put into this. It better be worth it.
Within the dashboard, I may make choices around accuracy. The chart may be less textbook, because it alone is not the message. Nope, I need the entire dashboard to come together as a unified message. It’s not a collection of charts. It’s a composition using charts as a medium with various other shapes and pieces interspersed to help support its message. Certain pieces are the pauses, the flicks, and the tones that guide us. It’s the charts, the way we link them, and everything that ties it together that comprise a visualization or dashboard. Without this, you’ve just made a pile of charts. People will read a dictionary and they will read a pile of charts. Narrative, tone, and creativity are what make conversations like dashboards worth engaging.
We do this with our spoken communication. We choose softer words, because we realize the harshness or the perception a word may have. We turn sentences around, making them passive if we don’t want to point the finger (“the glass was broken”). Many times, we choose to be less accurate technically to be more clear or heard overall. Or, in the interpreting example, we choose words our audience understands (cancer and not cancer vs malignant and benign) to meet them where they are. You see, accuracy isn’t defined by the interpreter – no, it’s the people getting the message. Even the Americans with Disabilities Act sees it that way. It’s incumbent on us to understand our audience.
Is accuracy the measure of the precision of our charts or the ability for the end user to understand what the chart is saying?
Hi Bridget, I somehow came across your blog — probably because I was googling things like “tableau training” and “ASL.” I’m Deaf, trying to learn Tableau, and feeling frustrated. I work at MIT and have gone to a couple of training classes here on campus, but it’s super hard to follow with an ASL interpreter, who is, of course, at least two sentences behind the action on the screen and the instructor’s explanation of what we’re supposed to be doing on our own laptops. I’ve started working through the training videos on the tableau.com website, and I can follow along with the action, but I’m not sure I’m getting the “why” in a way that is going to allow me to extrapolate to other data. I have a strong background in statistics and data analysis, but data visualization of this sort is something new for me. But it’s also something I could really use in my job. Do you have any tips for me? Do you know of a tableau class for deaf people, anywhere in the country? Some online resources that might be more helpful than those I’ve found so far? Anything? Tableau is SO cool, and it does so much, but it’s also really overwhelming. Would appreciate any advice you might have. Thanks in advance!
Kim,
I replied directly via email, but wanted to put some comments up here as well, in case others are struggling with this (if this is you, I’d love to chat!). I don’t know of any Tableau resources in ASL (yet). I’d love to see this change.
I think knowing ASL is a superpower when it comes to Tableau. Tableau favors a visual approach to communicating our data. It’s also unique in how it approaches data.
1. When we come from traditional stats / analysis backgrounds, we’re used to a particular shape with our data. Usually, if we open our data in Excel or other programs, we see a wall of numbers and use our columns to divide the data. Tableau works wonders when have a lot of words and a few columns of numbers in our data. If you look at most examples from training, the data looks like this – lots of words (including dates) and some numbers – usually 1 column per concept. I know I struggled with this in the past.
2. There’s some training before the training that I think is helpful – what is a Tableau dashboard (vs other dashboards)? To me, what makes Tableau special is the ability to really explore data. It changes the dashboard when you explore the data first. I’m not sure this is highlighted in trainings. I do an exercise when I train called “Explain the room.” Signers know there’s rules to how space gets explained in a language like ASL. You set the tone, THEN go around in an organized fashion explaining the room. To me, dashboards are a bit like this. When you explore the data, it changes how you build. I also think you can mirror certain ASL constructs in the dashboard design process itself.
3. There’s certain (deceptive) similarities between Excel and Tableau, but the paradigm is very different. When we think of Tableau with the idea of using small multiples as a guide, I think it gets easier.
4. I’m probably going to take some of these questions and address them in more long-form answers. These are fantastic questions.