Categories
Design

Data Viz lessons I learned in art school

I didn’t have my start in analytics. Honestly, when I was a college student, analytics, data science, and data visualization majors weren’t a thing, and analyst was not one of the jobs that were introduced as a possible career path (maybe I’m aging myself). I don’t know if 20-year-old me would have picked the major, anyway.

No, I started my undergrad time as an art major. For a long time, I thought my way to my data viz career was a bit roundabout and happenstance. As I reflect on it, though, so many of the things I learned in art school have helped me be a better data visualization designer, and, believe it or not, a better analytics professional in general. This is not to say I’m the best artist (I’m not) or the best data viz designer (not that either), but I think anyone can use these lessons to help their creative process and improve their designs.

I want to share some of the most important lessons that have stayed with me. These lessons aren’t learned in a book or in lectures. These are learned through hours of studio time, sketching, critiques, and discussions. And, they are lessons that I use (or at least try to remind myself of) regularly. Without further ado…

Constraints help you to be MORE creative, not less

I clearly remember this day in class, and I don’t even have a great memory 😉 — we were, for the first time, given very specific requirements for the size, medium, and topic of the piece that we were to deliver at the end of 2 weeks. We could do anything we wanted as long as it met these requirements and it could be done on time. Everyone grumbled, and there were many questions.

You want me to do what!? meme

At this point, our professor gave a wonderful speech. I’ll badly summarize it here:

“Now that you don’t have to think about these things, you are free to do anything. We waste a lot of our creativity and brain power on these small decisions. If you can get that out of the way, your time and energy can be directed toward making the piece more meaningful and effective. Plus, if you want to do this for a living, you’re going to need to get used to constraints.”

You don’t have to take my word for it. As I’m getting ready to publish this post, I listened to the episode of Data Viz Today where the amazing information designer Stephanie Posavec discusses the same thing. If you haven’t listened to the episode, you should!

If you don’t have the constraints provided to you in the form of requirements and style guides, you can create it for yourself before you start design or development. It will be time well spent.

Sketch. Make a lot of bad stuff.

It takes making ugly stuff to improve your skills. You improve by practicing and experimenting. Some of that stuff will be bad, and that’s ok. Necessary, even.

You discover your own style, and voice by doing the work. As you do, you will also find more confidence and creativity.

It also takes making a lot of stuff to get to the good ideas. So build bad stuff. And sketch, so that you can make more bad stuff faster. That’s how you’ll get to the good one.

“When we say we need to teach kids how to “fail,” we aren’t really telling the full truth. What we mean when we say that is simply that creation is iteration and that we need to give ourselves the room to try things that might not work in the pursuit of something that will.”

Adam Savage, Every Tool’s a Hammer: Life Is What You Make It

Find your inspirations

Look everywhere, and if you can, capture it. I used to keep a sketchbook full of magazine clippings, quotes, sketches, ideas, and pieces by my favorite artists.

Just the act of paying attention for these things will feed your creativity. And, most importantly, collecting things that you want to emulate or that inspire you will come together in unique ways because nobody else has the exact same set of inspirations as you. Think of it like finding the stars in the sky so you can make a constellation — something completely different from the source.

Plus, it’s interesting to have something of a time capsule of things that piqued your interest at a moment in the past. And you may just re-discover something that you weren’t ready to run with at the time, but now inspiration strikes.

“Don’t just steal the style, steal the thinking behind the style. You don’t want to look like your heroes, you want to see like your heroes.”
― Austin Kleon, Steal Like an Artist: 10 Things Nobody Told You About Being Creative

Thinking and planning are part of the work

This is one of my biggest challenges to remember. These things don’t feel as productive as just doing the thing. But, it is. In fact, it’s like super-powering productivity later.

Will the observer know what went into the piece? No, ideally, they will have no idea. They may not know why, but they will see that thought and preparation went into the work.

Thinking about the outcome, possibilities, and potential issues. Using reference materials, sketching, iterating, prototyping, and planning. Exploring the data and the topic to understand the source data and the way that Tableau uses that data. These will all show in the final product. You will be better prepared to build a well-functioning, performant, and meaningful dashboard. But know when to stop preparing and start building… at some point, it can become a tool for procrastination.

Understand the principles

Having an understanding of the principles of data visualization and of design, and the study of work from those that came before you will make your work better.

Not because you will follow all of the “rules”. There is no one gold-standard design. It will always depend on the data, context, and audience, among other things.

You learn the rules so you can break them — consciously and artfully. The principles exist for a reason, and if you understand why a “rule” exists, you can decide when breaking it may be appropriate, and can defend that decision.

“Learn the rules like a pro, so you can break them like an artist.”

Pablo Picasso

The only way to really learn is to get your hands dirty

You have to do the work to get better. You can’t study your way to a deep comprehension of the lessons you are learning. You won’t really know the discipline or the tools you use unless you are out there working with the real deal.

Practice with different subjects, formats, materials, and techniques. See what’s out there, what you enjoy, and what you’re good at (they aren’t always the same). Learn about the challenges and the gotchas of your craft.

And then hone your craft in one or two to get better. (Don’t worry — You can still do the other ones later if you feel like it, they are still there.) This part may be controversial to some folks, but I believe using the same toolbox over and over allows you to discover your style and strengths.

If you aren’t busy trying to figure out how to do it, then you can figure out what works best. You can take your knowledge to any other set of tools you like, but you will grow more by pushing the limits of one toolset.

Less is definitely more

Give enough information to convey the story to the audience, not so much to distract or overwhelm. Does this element make the story more clear? Is it important for making another element work? No? Get rid of it.

If the viewer has a lot to take in visually, you have lost the ability to guide them to the story. It can make the viewer feel overwhelmed or confused, and people don’t like to feel this way — Especially if they aren’t an “art person” or, in our case, a “data person”.

Take away visual noise. Take away extraneous information. Take away until it makes it less effective. Put that one back, and then leave it alone.

Share your work. Get and give feedback.

Critiques are an integral part of the formal study of art. When you regularly have to hang your work on the wall for a whole class of peers and professionals to look at and give feedback on, it’s scary and humbling. But, everyone in the room is feeling the same way. It’s very vulnerable, sharing your work with others and being prepared to hear what they don’t like about something you’ve stayed up for days working on.

Then show it to your mom or your friends, just to build your ego back up enough to go back 😉 But seriously, the input of “laypeople” can give you a peek at what your viewers may struggle with.

You also have to give feedback. You feel like an imposter a lot of the time, but this peer-to-peer feedback is just as important as getting feedback from professors and professionals.

Learning to both give and receive feedback with the pure intent of helping someone to stretch themselves, learn, and improve… This was one of the most helpful aspects of formal study of art (Even if I didn’t feel like it at the time). It’s still something I struggle with but it is always valuable.


Thanks all for today folks! Thanks for reading. In my next post, I will talk about the Principles and Elements of art and design and how we can use them to make better data visualizations.

Header image credit: Photo by Martin de Arriba on Unsplash

Categories
Design Figma It Depends

It Depends: Using design tools in your dashboard design process

You may have heard people talk about Figma or Illustrator, or maybe you’ve heard people talking about wireframes or prototypes. Perhaps you’ve seen dashboards with custom backgrounds. Some questions seem to come up often: What do you use Figma for? What are wireframes? Do I need prototypes? Should I use background images in my dashboards? Are these tools just something to use for flashy dashboards for Tableau Public? Why wouldn’t you just do your mockup in Tableau?

These are all really good questions to be asking, especially if you haven’t used these tools in your work before. In this installment of the “It Depends” series, I’ll unpack how and when I use design tools in my dashboard development process.

Just a quick note to say, I might talk about Figma a lot here, but this post isn’t about Figma specifically. There are other tools that you can use to accomplish similar things to varying degrees. Plenty of people use PowerPoint, Google Slides, and Adobe Illustrator just to name a few. Autumn Battani hosted a series on her YouTube channel that demonstrates this very well (link). If you want to see how different tools can accomplish the same task, give them a watch!

Why would I use design tools?

In my mind, it boils down to two reasons to use a design tool like Figma in your process:

  1. Create design components such as icons, buttons, overlays, and background layouts, or
  2. Create wireframes, mockups, and prototypes

So, let’s get into when and why you might use these…

Design Components

For business dashboards, it’s usually best to try to keep external design components to a minimum, but when used effectively, they can improve your dashboard’s appearance and the user’s experience.

Icons and Buttons

Icons can be a nice way to draw the user’s eye or convey information in a small space. Custom buttons and icons can add polish to your dashboard’s interactivity. But, they can also be confusing to the user if they’re not well-chosen. So, what are some considerations that can help ensure your icons are well-chosen?

Is the meaning well understood?

While there are no completely universal icons, stick to icons that commonly have the same meaning across various sites, applications, operating systems, and regions.

For example, nearly every operating system you use will use some variation of an envelope to mean “mail”. They might look different, but we can usually figure out what they mean.

iOS mail icon, Microsoft mail icon, and Google mail icon
iOS mail icon, Microsoft mail icon, and Google mail icon

Are they simple and easy to recognize?

Avoid icons with a lot of details and icons that are overly stylized. Look for a happy medium. Flat, lower detail icons are generally going to be easier to recognize and interpret. Once you’ve chosen an icon style, use that style for all icons.

In this example below, the first icon is a very detailed, colorful mail icon, the second is a stylized envelope, and the third is a simple outline of an envelope. The third icon is going to be recognizable for the most people.

colored mail icon, stylized mail icon, simple mail icon
detailed, stylized, and minimal icon (From Icons8.com)

Is there a text label or will you include alt-text and tooltips?

Text labels and alt-text are not only important for accessibility, they can help bridge any gaps in understanding and clarity.

Does it improve the clarity or readability of the visualization?

Avoid icons that distract or are unnecessary. Using icons strategically and sparingly will ensure they draw the eye to the most important areas and reduce visual clutter.

This quote from the Nielsen Norman Group is a good way to think about using icons in your designs:

“Use the 5-second rule: if it takes you more than 5 seconds to think of an appropriate icon for something, it is unlikely that an icon can effectively communicate that meaning.”

Nielsen Norman Group

Some places to use icons:

  • Information:
    • Including an information icon can be a great way to use a small amount of real estate and a recognizable symbol to give users supplemental information about a dashboard without cluttering the dashboard
  • Filters:
    • Hiding infrequently used filters in a collapsible container can reduce clutter on the dashboard while still providing what is needed
  • Show/Hide alternate or detailed views:
    • An icon to allow the user to switch to an alternate view such as a different chart type or a detailed crosstab view, or to show a more detailed view on demand

Background Layouts

Background designs can help create a polished, slick, dashboard. Something you might use for marketing collateral, infographics, and executive or customer-facing dashboards. A nicely designed background can elevate a visualization but they do come with trade-offs.

Does it improve the visual flow of information?

Backgrounds can be used to add visual hierarchy, segmentation, and to orient or guide the user.

Does it distract from the information being presented?

When backgrounds are busy or crowded, they take away from rather than elevate the data being visualized.

Does it affect the maintainability of the dashboard?

Custom background images need to be maintained when a dashboard is changed, so they should be included thoughtfully.

Does it adhere to your company’s branding and marketing guidance?

Background images that are cohesive with other areas will feel more familiar to your users which can make your solution feel more friendly

Does it have text?

Whenever possible, use the text in Tableau as it will be easier to update and maintain, and is available to screen readers. If you need to put the text in the background image for custom fonts, you can use alt-text or hidden text within Tableau.

Find Inspiration

If you’re looking for a place to start with designing layouts, I suggest checking out Chantilly Jaggernauth’s blog series, “Design Secrets for a Non-Designer“, and conference presentation of the same name.

Look at Tableau Public, websites you find easy to use, product packaging. Take note of what works well (and what doesn’t).

This Viz of the Day by Nicole Klassen is a great example of using images that set the theme, elevate the visualizations, and create visual flow and hierarchy.

Of course, it’s not just the data-art and infographic style dashboards that can benefit from this. If you peruse Mark Bradbourne‘s community project #RWFD on Tableau Public, you’ll see plenty of examples using the same concepts to improve business dashboards. Don’t underestimate the impact of good design on usability and perception… It matters.

*Tip: When you use background layouts, you usually have to use floating objects— Floating a large container and tiling your other objects within that container can make it easier to maintain down the line #TeamFloaTiled

Overlays

Overlays can be used to provide instructions to users at the point where they need them. They provide a nice user experience, allow users to answer their own questions, and can save a lot of time in training and ad hoc questions.

Example overlay

Can instructions be embedded in the visualization headings or tooltips effectively?

Overlays are fantastic for giving a brief training overview to users, but they are not usually necessary. Instructions are usually most helpful if 1) the user knows they exist and 2) the information is accessible where it will be needed.

Does the overlay improve clarity, and reduce the need for the user to ask questions?

Overlays should help the user help themselves. If the user still needs training or hands-on help, then it might not be the right solution, or it might need to be changed to help improve the clarity. Sometimes the users just need to be reminded of how to find the information.

Is your dashboard too complex?

Sometimes dashboards need to be complex or they have a lot of hidden interactivity, and there’s nothing wrong with that. However, if you feel like you need to provide instructions it’s always a good idea to step back and consider if the solution is more complex than necessary, or if you can make the design more intuitive. Sometimes complexity isn’t a bad thing, but it’s always worth asking the question of yourself.

Will it be maintained?

Similar to background layouts, overlays will need to be changed whenever the dashboard is changed. Make sure there is enough value in adding an overlay, and that if needed, it will be maintained going forward.

Wireframes, Mockups, and Prototypes

Wireframes, mock-ups, and prototypes are a staple of UX design, and for a good reason. They help articulate the requirements in a way that feels more tangible, they force us to ask questions that will inevitably arise during the development process, and they help solidify the flow and structure. In dashboard design, they can get early stakeholder buy-in, ownership, and feedback. They also help us get clearer requirements before investing in data engineering and dashboard development (and having to rework things later — Tina Covelli has a great post on this subject here). You can talk conceptually about what they need to see, how it needs to work, and the look and feel earlier so it can save time on big projects. I’m a big fan of this process.

So, what’s the difference between wireframes, mockups, and prototypes, and when might you use them?

Wireframes

Wireframes are rough sketches of the layout and components. They can be very low fidelity — think whiteboard drawings of a dashboard. These are great very early on in your process.

Hand drawn wireframe

They can also be a slightly higher fidelity wireframe that starts to show what the dashboard components will be. These are the bones of a dashboard or interface, but can help articulate the dashboard design and move forward the requirements discussion.

Digital wireframe

Even if your stakeholders never see the wireframe, sketching out what your dashboard and thinking about what the layout, hierarchy, interactivity will look like helps organize your thoughts before you get too far or get locked in on a specific idea.

There’s really no reason not to start any project with a wireframe of some sort. This is a tool for the beginning of your process, but once you’ve moved on to mockups or design there’s no reason to do a wireframe unless a complete teardown and rebuild are needed.

Mockups

Mockups are a graphic rendering of what the dashboard might look like. These are high (or at least higher) fidelity designs that allow the user to see what the final product might look like. Exactly how high-fidelity to make the mockups will depend on the project and level of effort you want to invest. You don’t want to spend more time on this process than you would to just do it in Tableau.

Mockup

I think it’s worth noting here: the mockup should be done by the Tableau developer or someone who is very familiar with Tableau functionality. Otherwise, you run the risk that the mockup shows functionality that isn’t going to work well or appearances that aren’t accurate.

If a lot of data prep is required or you are working on a time or resource intensive project, a good mockup is worth its weight in gold. If you jump right into Tableau and find out that it’s more complicated than you initially thought, it’s not too late to pivot and come up with mockups.

Mockups can save you quite a bit of time in the development process. I will use mockups to think about the right data structure and level of detail, and think about how metrics will be calculated or what fields will be needed. And, if your users see a preview of the result and have an opportunity to get involved in feedback early, you are less likely to end up delivering a project that dies on the vine.

Prototypes

As soon as you need to demonstrate interactivity, prototypes come into play. These can be low-fi or high-fi but are useful whenever there is a lot of interactivity to demonstrate. To build interactivity, you’re going to need a prototyping tool. You can get creative and mark up your wireframes and mockups with arrows and comments to show how a user will interact, but prototypes make it feel more real.

The goal of prototypes isn’t to fully replicate the dashboard. A sampling of the interactivity can be included for a demonstration to better convey the idea without spending a lot of time.

You may not need prototypes on many projects, but similar to mockups, if you’re working on a large, complicated project where the stakeholders and users won’t get their hands on a fully functional product for some time, a prototype can be very helpful.

Some things to consider:

  • Is there interactivity that can’t be demonstrated by describing it?
  • Are your users unfamiliar with the types of interaction?
  • Is the user journey complex or multi-stepped?
  • How much functionality needs to be demonstrated?

To sum it up

I believe that involving your stakeholders and user representatives early in the process yields better requirements and a sense of ownership and buy-in. Your stakeholders and users are more likely to engage with, adopt, and encourage the adoption of your solution if they feel ownership.

Knowing that time isn’t an infinite resource, these steps can also take time away from other aspects of the solution or extend the timeline. Sometimes mocking up or iterating right in Tableau will be faster and produce the same result. If you start in the tool, presenting rough versions and getting feedback early is still valuable for the same reasons. Consider if these steps are taking more time than the build itself, or when they add a step that’s not needed to clarify or establish the end goal.

Bonus: Diagrams

Most design tools can also be used to create diagrams. While diagrams aren’t “dashboard design” per se, they are often an important part of documenting or describing a full data solution. What kinds of diagrams might you use in your data solution process?

  • Relationships
    • The good old entity relationship diagram, whether it is a detailed version used for data engineering, or an abstracted version to present to stakeholders
  • User journeys
    • Map out the ways a user can enter the solution, and how they progress through and interact
  • Process flows
    • Flow charts… whether it’s mapping out the process that creates the data, the process for how the solution will be used, or the steps in the data transformation process

Thanks for reading!