A Data viz point of view

Gathering and organizing a foundation for data visualization

What’s all this about?

As teams design and redesign how we display data, we need guiding principles that unite different contexts and types of charts to set common expectations. Today charts are created by disparate teams and alignment is an additional effort. Our foundational components and guidance are missing a starting point for displaying information in a rich and consistent way.
The Field team is collaborating with a couple product teams to develop data viz charts that will build on top of these guidelines in a consistent and Shield-ready way.

So, what do we do about it?
Our process starts with a quick look around to gauge consistency and broader application as it stands. We evaluate how current implementation works with our system. Please know that we will look at approved and delivered work. The intention is to uncover ways to improve consistency, not to call out project teams or shine a negative light on any of the work sampled. We want to create things that build on decisions in the wild and fit with our core system.
From that context, we look around outside the bank to uncover best practices in the design system industry. Some of these findings apply and some will not fit in with our design standards.

And what did you find?

We have a lot of inconsistency today which can negatively impact user experience and require re-learning of patterns from moment to moment. I can’t say this enough - this is a direct result of a gap in our system.

What’s a Point of View (PoV)?

Before we finalize and publish new guidance and components, we craft PoVs to get the conversation going and frame up our core approach to any given topic. PoVs usually take one sprint and lead in to design and dev stories to create final pieces (components, documentation guidance, design and code, assets, etc.). So, all content and designed examples are works in progress and open for feedback.

Step 1 : Understand Usage to Define

In partnership with one of our researchers, we surveyed 15 groups across the org to understand how teams currently use data visualization and to document needs and gaps.

Step 2 : Competitive Analysis

In partnership with one of our researchers, we surveyed 15 groups across the org to understand how teams currently use data visualization and to document needs and gaps.

Summary of findings

→ Most systems include a robust library of charts.
→ Color guidance is included to define categorical, sequential, diverging, and status data.
→ Color should carry a lot of power, but not as a sole communication tool.
→ We need guidance and templates with a strong PoV around color and complexity. Including pre-set but flexible color palettes.
→ Basic interaction guidance with core concepts that map back to the brand.
Examples from the wild are included:

Step 3 : The Point of View

The purpose of data viz is to communicate data in a way that is easy to understand and form ideas from. Highlight triggers for action and guide towards higher levels of financial health.