Tag: data visualization

I drive a Tesla Model Y and love it. They’re not for everyone and not for every situation, but I think it’s the best car I’ve owned. My wife feels the same way, and if we had a need for two cars, we’d likely get another one. The car is fun, and I look forward to getting in and moving around town. If you have questions about owning an EV or a Model Y, please feel free to ask.

The car isn’t perfect, and there are things I wish I could change. There have also been a few recalls on the car, which is interesting for a Tesla. A few of these recalls meant that I got a software update a few days or weeks later and something changed. There was another recall recently, which affects most Tesla vehicles in the US. I’m sure that by the time you read this, I’ll have a software update applied and the issue will be resolved.

This particular recall was because a font was too small. That might seem like a minor thing, but as someone who needs reading glasses all the time, I do think this is an issue. In fact, I appreciated that Tesla sent an update in 2023 that let me set all font sizes larger on all screens. I wish they were slightly larger, and I wish they’d check the UI for a few things as the text is cut off in minor places, but I can usually squint while driving and make out what’s there.

I also keep reading glasses permanently in the car in case I really need to grab them and see something.

Many of us work with data, and we may build reports (or edit them) to help our customers consume data and make decisions. Hopefully, some of you have learned how important good visual design is to creating an impact with your reports. Even if you report on something as simple as uptime, the way you showcase the data makes an impression on those who consume it. In case you’re sending your boss a message, I hope you want to ensure he or she receives the same impression you want to send. Remember, communication is what is heard, not said.

There are lots of resources out there about visual design, and lots of places where you can ask questions about what you’ve done and see if someone has hints or ideas to create a better presentation for your data. Even if you aren’t designing for safety, you’re often designing for impact and you want to do that well.

We’re lucky in the digital world in that we can adjust the way things appear easily, and relatively cheaply. Imagine if Tesla had created a dedicated sensor or physical light to let us know about a brake issue. If that were too small, the recall wouldn’t be a software update. It would likely be hundreds of thousands of hours lost by them and customers on a simple design correction.

Update: A couple of days after I wrote this, I got an over-the-air update, which fixed this.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

I’m not a visual designer, and I find that as I learn a bit more, many of my previous reports contain lots of silly mistakes. They’re often full of data, which I like, but which can be hard for others to follow and understand.

I need to do better, and I do ask for help at times from friends. I also need to get a better process for evaluating if I’m doing a good job. I was thinking about that as I saw a makeover article from storytellingwithdata. It gives a short process of things to consider when building reports.

With most of our software, we go through iterative approaches, either by ourselves, or with others, to try and build something that meets the needs or a client. Reports involve the same process, but I know that often the report process is my showing them something very raw and them asking for changes.

What can be more time consuming is that the numbers are often the thing a client is concerned with early on. Are we calculating things correctly and including enough data. We might go back and forth quite a bit on this part of the report process.

Once we agree, and they are happy, I think I’m done and can move on. However, often this is where they start to now care about the visual appear. The layout, colors, etc., and I am drawn into another report writing session, spending more time on something that is far, far less interesting than writing queries or other software code.

I can see why tools like Power BI, which let the client mess with the visual design, have a lot of appeal. As a software developer, I’m out of the loop here, or more out of the loop. Let them decide they want a vertical or horizontal bar chart, or a stacked line chart. What do I care?

I know visualization, layout, colors, etc. are important. They’re not enough of my job to care, but I do think someone needs to. I’m lucky in that my company has artists, so I can send over slides, reports, etc. and get hints about what I should change. It’s certainly something I wish I’d have had in the past at other jobs, since anything beyond a simple graph or table is well outside my wheelhouse.

Steve Jones