Sharing findings with anyone using storyboards

Objectives

Background

You've been busy creating visualizations and metrics to communicate your Pcard program exceptions. Sharing this information with Pcard program and compliance stakeholders is critical, but not everyone in your organization has access to Results and Storyboards. You also don't think navigating to each visualization and metric is the most effective (or time-saving!) way to tell the story of your data.

You need a way to share your findings in a consolidated, accurate view with all the necessary people across your organization. If you could find a way to do this and ensure these reports are always up-to-date so everyone can make decisions based on the same, current data... well, that sounds like a sure way to stand out from the crowd - for all the right reasons.

Overview

Storyboard, you say?

So you're now a pro at creating pretty nifty visualizations and metrics, and you want to be able to share them with the powers that be. You'd like to incorporate a few visualizations and metrics in one location to create a meaningful story that will convey all the important information you've gathered from your analysis: Enter the aptly named storyboard to the rescue.

A storyboard that you've carefully crafted will display your visualizations and metrics. On top of this, you can add text to provide a bit of context so that anyone who looks at your storyboard can read your story. You could create the nicest looking visualizations, but they won't be of much use if your audience doesn't understand what they're intended to communicate!

Why should I use storyboards?

Storyboards can be applied in many different contexts and across a wide range of industries and even departments. The possibilities for what stories you could tell are limitless. What all these possibilities have in common is the underlying reason for creating any storyboard: making your message hit home so that you have the buy-in to enact change. It also doesn't hurt that sharing this kind of key information will help make you the most sought-after player in your organization.

You step back a moment from your audit and jot down a number of potential storyboard uses because that's how much of a visionary you are!

Potential story to tell with your storyboard

Recommendation or change you'd want to enact

Lack of IT security certifications for your third-party vendors

Increase security certifications for third-party vendors and protect confidential company information

Suspicious travel and expense transactions by merchant, date, and amount

Automate travel and expenses policy education and follow-up procedures in order to separate false positives from actual violations

Control deficiencies in financial processes

Provide training for the Finance Team on potential control failures and measure impact or success of training initiative

Internal controls testing and manual processes related to SOX compliance

Automate SOX and control testing to decrease manual workload and save time and money

Adding visualizations, metrics, and text

Once you start working on your new storyboard, you have the option of adding visualizations and metrics (that you created in Results) to a storyboard. You can add up to three of these items per row along with an unlimited number of rows, so you have plenty of ways to tell your story about your latest security review.

Watch the video below to see how to get started with creating your first storyboard:

Sharing your storyboard with anyone

Once you've created a storyboard, you have the capability of sharing it with anyone! That's right - anyone! You can even share it with folks who don't have a Diligent software subscription.

Tip
Save your storyboard before you share it.

After you've named, designed, and saved your storyboard, you can generate a link that can be sent to and viewed by anyone. Even if you make changes to your storyboard, the initial link you generated will still be up to date with ALL your latest changes.

Approach

  1. It's time to get noticed across your organization for all the right reasons. Start building your first storyboard so you can effectively communicate the story of your data.
  2. You want to make sure your storyboard communicates information around employee Pcard violations and how these exceptions are being remediated.
  3. You also want to present total Pcard transactions data. It would be enlightening for key stakeholders in the Pcard program to visualize data, such as:
    • the location where most Pcard transactions are occurring
    • the most-purchased-from merchants
  4. Save your work and then share it with anyone, regardless if they're a HighBond user or not.