Hello Reader,

Happy 4th of July to my fellow Americans -- glad you're with me today. 🎇

I'm planning out newsletters for the rest of the year and want to start incorporating more Python, Tableau, and Agentic Analytics. Can you take this short survey for me? Thanks!

If you've been working as an analyst, you'll be familiar with a request like this:

You know how to write the query. That part takes you ten minutes. Not a problem. But...the chart, the schedule, the email? Right now, your only option is to do all of that by hand—every Monday, forever and ever until the end of time. Ugh.

Over the past several months, we've built a serious SQL foundation together: filtering, joining, aggregating, window functions, data quality checks, export formatting. You've seen how a single well-written query can answer an executive question and drive a real decision.

And you've probably also started bumping into the edges.

SQL won't build a dashboard that refreshes itself. It won't send an alert when revenue drops below a threshold. It won't loop through 500 messy CSV files and clean them before lunch. Those jobs belong to other tools, and knowing exactly where SQL ends and the next tool begins is one of the most valuable things you can understand as an analyst.

Here's the map I wish someone had handed me ten years ago.

Layer 1: SQL Teaches You to Think in Data

Everything starts here, and there's a reason we spent months on it.

SQL is how you pull data out of databases, reshape it, connect it across tables, and answer specific business questions. But the deeper value is what it does to your thinking. Every technique we've covered (e.g., JOINs, window functions, CASE WHEN, the Mister Rogers exploration process, the So What Framework) trains the same underlying habits:

• What tables exist?
• How do they connect?
• What question am I actually answering?

These mental models and skills transfer to every tool you'll ever touch. Which is exactly why the next two layers come so much faster than the first one did.

Layer 2: Python Multiplies What You Already Know

Python picks up where SQL stops: automating repetitive work, cleaning messy files, calling APIs, running statistical analysis, and connecting your database to everything else in the business.

If Python has ever felt intimidating, here's some good news. Its core data library, pandas, works on concepts you already know cold:

Same thinking, new syntax. You won't be starting from scratch with the new skills. You'll just be translating what you've been learning here each week into a new layer in the modern analytics tech stack.

Remember last week's running total query?

In Python, you could run that exact query against the database, generate the chart, and email it to your team every Monday morning while you're still on your first coffee. The SQL does the analysis. Python handles the automation and delivery.

That's the Monday-morning request from the top of this email, solved once and never touched again.

Layer 3: Tableau Turns Your Findings Into Stories

The third layer is communication: taking what you found and making it visible to people who will never read a table of numbers.

My tool of choice is Tableau, and here's why: I've used it for over ten years, and it's the tool that pushed me past the six-figure mark in my career. Plenty of tools can render a bar chart. Tableau taught me to think visually about data in a way nothing else did. (I've written about the six-figure analytics tech stack if you want the full argument.)

Tableau runs on SQL under the hood. Every dashboard you build is sending queries to your database behind the scenes.

And because you understand SQL, you'll understand what your dashboards are actually doing...which means you can troubleshoot them, optimize them, and trust them. Analysts without that foundation are just dragging and dropping pills around and hoping for the best.

Remember the monthly revenue trend we analyzed with window functions? In Tableau, that becomes a line chart with a moving average overlay your VP can explore directly. The seasonal decline that took us a query to uncover is visible in about three seconds.

The Order Matters More Than the Tools

I've watched analysts learn this stack in every possible order, and the order shows up in their work.

The analyst who starts with Tableau builds beautiful dashboards that answer the wrong question, because nobody taught them how tables connect or what a GROUP BY actually does. The analyst who starts with Python writes thirty lines of pandas to do what a five-line query handles better, because they never learned that the database does aggregation natively.

The sequence that works is the one you're already on (congrats!)

SQL teaches you to think in data. Python extends that thinking...how to automate it, scale it, connect it to other systems. Tableau communicates it to everyone else. SQL alone is powerful. Add Python and it runs without you. Add Tableau and anyone in the company can see what you see.

Where You Stand After Months of Weekly Emails

If you've been reading along and practicing the queries, take stock of what you've actually built: you can explore an unfamiliar dataset from scratch (Mister Rogers Blueprint), filter and organize with intent (Marie Kondo Blueprint), run multi-table investigations (FBI Evidence Board Blueprint), find what's missing (Empty Stadium Blueprint), analyze trends with window functions, spot data quality problems before they burn you, and frame all of it for business impact (So What Framework).

That's a real foundation. The next layers build on it directly.

Three Questions Worth Asking This Week

Run through these quickly and be honest:

1. Do I run the same analysis more than once a month? If yes, Python automation would buy back real hours.
2. Am I pasting results into slides or emails by hand? If yes, a dashboard or automated report is your next move.
3. Does my analysis end its life in a report nobody acts on? If yes, the missing piece may be what I call Agentic Analytics — turning analysis into systems that act, instead of documents that collect dust. It's a model I've been developing, and I'll have much more to say about it soon.

Even one yes means you already have a live use case for the next layer.

What's Coming From Business Analytics Academy

Later this year I'm building out the next layers of this stack: Python for automation, Tableau for data storytelling, and Agentic Analytics for turning analytical ideas into business value.

Before I build, I want to hear from you. Reply and tell me: Tableau, Python, or Agentic Analytics -- which one matters most to your work right now? Better yet, can you take this short survey for me? Your answer directly shapes what I make next.

In the meantime, keep sharpening your SQL. It accelerates everything else. (For the full picture of the progression, I've written about the modern data analyst skill stack.)

This Week's Action Item

This week:

1. Open your most recent analysis or report
2. Ask: "What part of this workflow is manual that could be automated?"
3. Write it down and keep it handy.

This will become your first use case and we'll come back to it in the coming weeks!

Stay tuned!

Brian Graves, creator of Analytics in Action Say 👋 on X/Twitter, LinkedIn, or book a call with me. You can always reply to these emails. I check them all.

​

P.S. Everything in Layer 1 -- the frameworks, the SQL skills, the analytical thinking --- is what SQL for Business Impact covers from start to finish. If you haven't built that foundation yet, now is the time: sqlforbusinessimpact.com.