The Clearly Podcast

Colour in your BI Reports

Summary

This week we talk about colour. 

Colour is generally a central element of branding, but we must also think about accessibility and the emotional response colour generates.  Red is frequently associated with stop or bad, whereas green with good or go.  Similarly, we may say we feel blue when we're a bit down.  At the same time, we need ensure our choice of colours are accessible to people with colour blindness, and not relying entirely on colour to tell your data story.

If you want to select an exact colour from an image, and get the RGB code, you can use a colour picker, such as this one.  You can use a theme generator to create a selection of complementary colours, and put these colours into a theme file.  If you don't want to create the JSON file from scratch (and let's face it, who does?),  you can use this handy tool from PowerBI.tips. 

Coloring for Colorblindness gives a reasonably simple  introduction to creating accessible colour schemes.

Finally, make sure the colour is included in the non-function testing - including testing the colours on different screens.  If you're not yet doing non-functional tests, you should be.

You can download Power BI Desktop from here.

If you already use Power BI, or are considering it, we strongly recommend you join your local Power BI user group here.

Transcript

Andy: Hello everyone, welcome to Clearly's podcast episode 17: "Using Colours in Your BI Reports," recorded on Thursday, February 4th. I'm Andy Clark, joined by Shailan  and Tom. Today, we discuss applying colour in BI reports, from choosing initial colours based on branding guidelines to selecting complementary colours online, and the importance of testing colour applications. How are we doing?

Shailan: Great, thanks Andy. Colour is crucial in BI reports because it defines a client's brand and ensures accessibility. For instance, many clients want red, amber, green (RAG) indicators for KPIs. However, with about 1 in 10 men having red-green colour blindness, RAG might not be suitable. Instead, we can use other colour spectrums like blue to orange.

Tom: Exactly, Shailan. Colour also elicits emotional responses. For example, red often means "stop" and green means "go". These responses are ingrained, but we must also consider biases. As a Chelsea fan, Andy might see blue as positive and red as negative.

Andy: Indeed, Tom. Biases and brand perceptions matter. I once worked with a drinks company that hated anything red due to competition. Understanding these nuances is essential when discussing colour with clients.

Shailan: Absolutely. When demonstrating to clients, incorporating their logo and colours helps them resonate with the visualizations. Tools like colour pickers can help match their exact brand colours if they haven't provided guidelines. Starting with their colours in pre-sales demos makes a strong impression and opens the conversation about their branding preferences.

Tom: Branding guidelines are a good start, but they often have limited colour options. It's crucial to ensure contrast for readability. Online tools can suggest complementary colours, but maintaining contrast is key to avoiding confusion.

Andy: Consistency in colour usage across reports is vital for user familiarity. For example, keeping slicers and filters consistent helps users quickly understand the report's functionality.

Tom: Exactly. Dashboards should be intuitive. Users should grasp key information at a glance without needing to read detailed explanations. Consistent colours for categories across visuals are essential, even if it requires manual application in some tools.

Shailan: Consistency extends to labels and text colours. For instance, using contrasting text colours for RAG indicators enhances readability. Testing on various devices and screens is crucial to ensure colours render correctly.

Tom: Also, consider users with tinted lenses or overlays for dyslexia, as these can affect colour perception. Non-functional testing should include different devices and printed versions to ensure readability and accuracy.

Andy: Testing is critical, especially for printed reports. Printed colours (CMYK) can differ from screen colours (RGB). Ensuring consistency across formats prevents costly mistakes.

Shailan: Indeed, testing colours on different devices and for various visual elements ensures overall accuracy and accessibility.

Tom: Remember, different printers may render colours differently. Always proof colours before final printing to avoid discrepancies.

Andy: Great points, guys. Let’s wrap up with our top tips for using colour in BI reports.

Shailan: Consistency is key. Align colours with your client’s branding and ensure accessibility.

Tom: Consider the semantics of colour. Colours evoke specific responses, so use them wisely.

Andy: Utilize online tools to find matching swatches, simplifying the colour selection process.

Tom: We'll include some useful links in the description.

Andy: Thanks, everyone. For more information, visit clearlycloudy.co.uk for the UK and Europe or clearlysolutions.net for North America. We'll be back on March 1st to discuss application lifecycle management. Stay safe and have a great day!