How to Master the Art of Storytelling in Analytics

Did you hear the one about the moth?  A moth goes to a podiatrist, and the podiatrist asks, “What brings you in today?”  It’s a joke kindergarteners tell each other, but we can make it better.   In fact, Norm MacDonald did just that.  It’s the same thing we have to do when we’re presenting data.  

Pie charts are a joke

The setup of the joke is a lot like a pie chart:  It begs more questions than answers it provides.  You look at a pie chart and ask yourself, what is this trying to tell me?  What is the context here?  What came before?  What is the rest of the story?  How did we get to this point?  What conclusions should I draw?  

XKCD: Menu -> Manage -> [Optimize space usage, Encrypt disk usage report, Convert photos to text-only, Delete temporary files, Delete permanent files, Delete all files currently in use, Optimize menu options, Download cloud, Optimize cloud, Upload unused space to cloud]

Well-told data is an unforgettable story

Data storytelling makes data more relatable, simplifies complex subjects, and imprints on the audience’s memory through emotion.  IBM’s Bee School teaches that there are five elements to a story.  Using this formula, you should be able to craft a narrative that is entertaining, compelling, and actionable.

  1. The Protagonist

Every story worth remembering has a memorable main character.  The moth, for example.  Your data story needs to feature a relatable character.  Consider creating an “Everyman” persona, a composite of real people.  Maybe the hero of your story will be a product personified, a project team, or a lonely accountant.  Give your audience someone to relate to, to care about.  Introduce him or her and give them a name.  You’re creating a connection.  “Know” this character.

  1. The Scene

The moth in our story walks into a podiatrist’s office.  Weird, yeah, but we do want to know what’s next.  In the same way, a data story needs a well-defined setting that the audience can visualize.  Notice what we’re doing here.  We’re visualizing data by painting a verbal picture.  We’re providing color to the data.  We’re giving the data context that the hearer can imagine.  Answer some of the questions you know are in the air.  What happened last year?  What is the competitive landscape?  What is the status quo?  What is the atmosphere?  What’s the mood?  What are the constraints?

  1. The Problem 

Like an unclosed parenthesis, there’s tension.  The problem is lurking.  What brought the moth to the podiatrists office?  Similarly, your data hinges on a pressing problem.  Why else present it?  Include the dirty laundry.  It’s more compelling.  Perhaps the analysis of the podiatrist’s patient satisfaction surveys shows a problem related to wait time in the office.  Or, 3 of 10 financial dashboard KPIs are moving in the wrong direction.  Call out the emotional or financial stakes behind the numbers.  We’re at risk of losing patients.  Are we at risk of meeting the budget?  This section is where your audience leans forward and says, “tell me more.”

  1. The Action

The moth sought out a podiatrist.  In a data story, you follow the problem with the steps needed to address it.  Sometimes, it will be steps you or the business has already taken.  Sometimes, it will be a plan of action.  Is the problem in the data?  Is it a process that’s broken?  Talk to your audience about the details related to a quest for a solution.  Engage them.  Reveal the path, whether it’s additional analysis, research, or a change in direction.  It is here where you present how the protagonist responds to the challenge. 

  1. The Resolution

What changed when the action was taken?  Did patient wait time decrease?  Did profits improve?  Or, what needs to change?  Do you recommend creating a committee or task force to address the problem?  Close with your punchline – the key insight, the moral of the story, and next steps.  Remind the audience why it matters.

A simple story in the hands of a master storyteller

The late Norm MacDonald took the simple children’s riddle of the moth and made it his own.  He made the audience wait for the punchline as he filled in every element a well-told story needs.  He introduced us to the protagonist, the moth.  He set the scene in a well-lit doctor’s office.  He defined the moth’s problem as told by the moth.  He added detail and color.  He drew his audience in.  The moth’s depression and personal problems made it compelling that he should seek help.  “You obviously need help, but, Moth, I’m a podiatrist,” the doctor says, “why did you come to see me?”  The moth says, “Your light was on.”

Learn from the master; the next time you need to present data, tell a story.  Use Norm’s formula to hook the audience, keep them emotionally invested, and help them visualize the data with your words.  

Scroll to Top
As the BI space evolves, organizations must take into account the bottom line of amassing analytics assets.
The more assets you have, the greater the cost to your business. There are the hard costs of keeping redundant assets, i.e., cloud or server capacity. Accumulating multiple versions of the same visualization not only takes up space, but BI vendors are moving to capacity pricing. Companies now pay more if you have more dashboards, apps, and reports. Earlier, we spoke about dependencies. Keeping redundant assets increases the number of dependencies and therefore the complexity. This comes with a price tag.
The implications of asset failures differ, and the business’s repercussions can be minimal or drastic.
Different industries have distinct regulatory requirements to meet. The impact may be minimal if a report for an end-of-year close has a mislabeled column that the sales or marketing department uses, On the other hand, if a healthcare or financial report does not meet the needs of a HIPPA or SOX compliance report, the company and its C-level suite may face severe penalties and reputational damage. Another example is a report that is shared externally. During an update of the report specs, the low-level security was incorrectly applied, which caused people to have access to personal information.
The complexity of assets influences their likelihood of encountering issues.
The last thing a business wants is for a report or app to fail at a crucial moment. If you know the report is complex and has a lot of dependencies, then the probability of failure caused by IT changes is high. That means a change request should be taken into account. Dependency graphs become important. If it is a straightforward sales report that tells notes by salesperson by account, any changes made do not have the same impact on the report, even if it fails. BI operations should treat these reports differently during change.
Not all reports and dashboards fail the same; some reports may lag, definitions might change, or data accuracy and relevance could wane. Understanding these variations aids in better risk anticipation.

Marketing uses several reports for its campaigns – standard analytic assets often delivered through marketing tools. Finance has very complex reports converted from Excel to BI tools while incorporating different consolidation rules. The marketing reports have a different failure mode than the financial reports. They, therefore, need to be managed differently.

It’s time for the company’s monthly business review. The marketing department proceeds to report on leads acquired per salesperson. Unfortunately, half the team has left the organization, and the data fails to load accurately. While this is an inconvenience for the marketing group, it isn’t detrimental to the business. However, a failure in financial reporting for a human resource consulting firm with 1000s contractors that contains critical and complex calculations about sickness, fees, hours, etc, has major implications and needs to be managed differently.

Acknowledging that assets transition through distinct phases allows for effective management decisions at each stage. As new visualizations are released, the information leads to broad use and adoption.
Think back to the start of the pandemic. COVID dashboards were quickly put together and released to the business, showing pertinent information: how the virus spreads, demographics affected the business and risks, etc. At the time, it was relevant and served its purpose. As we moved past the pandemic, COVID-specific information became obsolete, and reporting is integrated into regular HR reporting.
Reports and dashboards are crafted to deliver valuable insights for stakeholders. Over time, though, the worth of assets changes.
When a company opens its first store in a certain area, there are many elements it needs to understand – other stores in the area, traffic patterns, pricing of products, what products to sell, etc. Once the store is operational for some time, specifics are not as important, and it can adopt the standard reporting. The tailor-made analytic assets become irrelevant and no longer add value to the store manager.