Featured Product
This Week in Quality Digest Live
Customer Care Features
Leah Chan Grinvald
Independent repair shops are fighting for access to vehicles’ increasingly sophisticated data
Gad Allon
Aligning timing, leadership, and strategy is complicated
Delivering quality to the health industry
Mike Figliuolo
Globalization is an unstoppable trend, so why not take advantage of it?

More Features

Customer Care News
A tool to help detect sinister email
Developing tools to measure and improve trustworthiness
Manufacturers embrace quality management to improve operations, minimize risk
Scaling operations to reduce plastic waste in oceans
Survey shows 85% of top performers rely on it to achieve business objectives
Educational offerings available in Santa Clara in December 2023
Precision cutting tools maker gains visibility and process management across product life cycles
A Heart for Science initiative brings STEM to young people

More News

Paul Laughlin

Customer Care

What Tools Should Data Analysts Have in Their Toolbox?

Part 1: The technical stuff

Published: Tuesday, November 5, 2019 - 12:02

What tools should data analysts have in their toolbox? It’s a broad question and one with diverging views. So, I am delighted to welcome back a guest blogger who doesn’t shy away from controversy.

Martin Squires is a very experienced znalytics leader, whom I’ve previously interviewed in our audio series. He has also posted before on why he disagrees with the use of business partners (a view I countered here).

I hope this post might be the start of a series of perspectives. But, for now, over to Martin to share his wisdom on what should be in your toolbox.

Getting caught up in comparison

With the plethora of new kit that seems to come out every year (or even month), it’s easy to get lost in the depths of debates about R vs. Python and Azure vs. AWS. When asked about my favorite tools, I was reminded that I don’t have the pleasure of being “hands-on” for a living anymore.

But what I do have to do is to try and make sure teams I lead have the right tools, competency frameworks, and development plans. So I thought I’d take it back a step or two and try and look at what I’d still want to learn if I was setting out on the development path today. What I’d recommend for someone thinking of starting that journey.

The ideal toolbox I think needs to enable an analyst to do three main things:
1. Get their data and prep it for analysis
2. Explore and analyze the data and unearth the insights
3. Present the findings in a way that drives action

Stuff your toolbox with these evergreen tools

So, what’s the stuff I’d fill the toolbox with to achieve those objectives?

Structured Query Language (SQL)
Yes, I know it’s not as fashionable or as new or sexy as some other languages. But if you just look on LinkedIn at job postings, the old workhorse isn’t being put out to grass anytime soon. It seems that most companies still have big relational databases, and SQL is still the best way to learn how they work and to get data out of them.

Plus, once you’ve learned SQL, then moving on to learn other stuff like R or Python is a lot easier. SQL... the gateway drug for coders! Check out the “Top 20 technology skills in 2019 data science job listings” chart in this Uplist blog post (spoiler: SQL is third).

Exploratory data analysis (EDA)
Not sure if it’s a tool as such, but John Tukey’s book should still be compulsory reading. For all the “data science is the sexiest job in the 21st century” stuff, just having a great grounding in how to explore a data set is still “Analysis 101.”

How do analysts visualize and explore their data to understand the patterns in it? Even if you are going on to build complex models with the data, understanding the materials you are building with is a vital first step.

As far as software tools go, I rather like tools like Alteryx, which make the task a lot, lot simpler and more efficient than it used to be. But here is a link to this vital EDA guide.

Data visualization
This one also depends on just what exactly you need to do. For some this is simply about how to present data to end users once you’ve got the analysis in place; for others it’s a tool that helps with the exploratory data analysis. Helping analysts to drill down into the data and carry out train-of-thought analysis.

The two are very different, differences which have driven more than one BI project onto the rocks. Here, I’m sticking to the “present the data” option. Again, I’m almost tempted to include books as well as tools per se, and I’d certainly recommend reading works by Alberto CairoAndy Kirk, and Stephen Few before touching software. Check out Paul’s recommended reading list, too.

In terms of kit, then all the main players in this space do a good job, and it really just comes down to personal taste. Tableau and Qlik are both good tools, and both have free versions with lots of useful online training material, so either would tick the box as a great place to start.

Geographical information systems (GIS)
GIS is a big hobby horse of mine. Geography is key to understanding customer behavior in lots of areas. For example, in healthcare, how much customer choice of pharmacy is driven by proximity to a GP? (Answer, a hell of a lot).

So, I’m glad to see that fellow guest blogger Tony Boobier has also championed the priority of thinking about location and maps in his posts.

Learning a mapping tool for me is essential. There are deeper and more powerful tools than QGIS out there (most of the real experts I know are fans of ArcGIS), but again QGIS has a free version with good training resources, a good place to start.

Which do your analysts have in their toolbox?

Thanks to Martin for that list of recommendations. Very useful and clearly grounded in practical experience.

Do you agree? Any others you would recommend that should be essentials for good analysts to have in their toolbox?


About The Author

Paul Laughlin’s picture

Paul Laughlin

Paul Laughlin is a speaker, writer, blogger, CustomerInsightLeader.com enthusiast, and the founder and managing director of Laughlin Consultancy.