The Tableau Fundamentals That Actually Matter (And Why Getting Them Wrong Is Costing Your Team)
I've spent the last year conducting market research calls with analytics leaders across a wide range of organizations. They came from different industries, manage teams of different sizes, and have made different levels of Tableau investment. But the same key themes emerged across those calls.
Their analysts don't have all the skills the organization needs to truly get the most value out of their Tableau investment.
When I ask how that happened, the answer is almost always the same: nobody ever properly taught them. They were handed a Tableau license, pointed at some documentation or a YouTube playlist, and left to figure it out. Some of their IT departments even block YouTube!
The analysts eventually figured out enough to get by. But they never built the solid foundations that would help them grow into irreplaceable analysts fast.
These are not people who failed to develop. They are people who were never given the right conditions to develop.
The results become visible when a dashboard gives the wrong answer, a data question takes three days to resolve, or a leadership presentation falls flat because nobody could explain where the numbers came from.
I've been working with Tableau for 19 years. I've built analytics practices at Meta and Coca-Cola. Over the course of my career, I've trained more than 10,000 analysts, and Next-Level Tableau is where that work continues today. I know that the skills gap in most enterprise analytics teams comes back to the same missing fundamentals.
What are those fundamentals?
The Data Model
Tableau's data model is the foundation for everything. Before you build dashboards to share with your stakeholders, you need to understand how Tableau reads and relates data. That means understanding the difference between a logical layer and a physical layer. It means knowing when to use relationships versus joins versus blends, and why the choice matters for your analysis.
Trusting Tableau to simply figure things out when you work with data will only take you so far. At some point you will inevitably get row duplication, aggregation errors, and numbers that look right but aren't. In an enterprise context, those errors can erode trust in the entire analytics function.
When your team really understands the data model, they can work with data faster and more reliably. Dashboard performance improves, logic becomes cleaner, and analysts can confidently answer the question "where is this number coming from?" and iterate on the spot.
Calculated fields and the logic behind them
Calculated fields are incredibly powerful and it’s essential to understand how they work.
They are not hard to use, but a lot of analysts learn about them by copying formulas they find on AI. They assume the syntax is right (it often isn’t) AND they don't understand the logic. You can get away with that for a little while, but not if you want to build more advanced analyses and dashboards to show your results.
Row-level vs. aggregated calculations, level of Detail expressions, table calculations, and order of operations are critical concepts that analysts need to understand for their analyses. Otherwise, they end up working around problems instead of solving them, and those workarounds can break when the data changes.
In a team, this can lead to problems when every person builds their own version of the same calculation in a slightly different way. It’s a maintenance nightmare and a consistency risk.
The Marks card and how Tableau builds visualizations
I ask analysts in my training: do you know what the Marks card controls? Most people can use it. Very few can explain it.
That gap matters because the Marks card is how Tableau encodes data into visual form. Understanding it means understanding why a chart looks the way it does, how to change it intentionally, and what goes wrong when it doesn't behave as expected.
When analysts really get it, they can completely change their approach to dashboard and chart design. Instead of pulling things around until the chart looks approximately right, they build with intention and troubleshoot quickly. And they can explain their choices to stakeholders in a way that builds confidence in the output.
Dashboard design as communication, not decoration
A dashboard is a communication tool and understanding how to communicate with data gets left out of most training. A dashboard’s job is to answer a specific question for a specific audience in a specific context. When analysts don't understand this, they build dashboards that are technically impressive and practically useless. Too many charts, too much information, no obvious answer.
This is the fundamental that leadership cares about most, even when they can't articulate it. They look at a dashboard and feel uncertain. They ask follow-up questions that the stakeholder could answer themselves if the dashboard was designed to guide them.
That’s a huge time saver for analytics teams. It frees them up to work on more projects, more quickly, with better quality.
Teaching analysts to think about audience before they think about charts changes the quality of the output and the perception of the entire team.
What success looks like
Sean Trout saw this exact problem at Nutanix. His team was handed specs and built accordingly. Crosstabs with filters across the top and no visualisation.
So he changed the approach. His rule:
“If someone asks you a question and all you do is answer it, you've failed them. Answer what they asked, plus the next three to five questions they'd have asked anyway, including ones they didn't know they had.”
Nine months later, a senior leader saw Sean's team's latest dashboard and asked if it was a mockup, something they were still working toward. It was a week from release.
That's what Next-Level Tableau did for Nutanix in only nine months.
Why this matters for your team
These four fundamentals underpin every piece of work your team produces. When they are solid, everything is faster, more consistent, and more trustworthy. When they are shaky, you feel it in every review cycle, every data question, every dashboard that needs to be rebuilt after the source changes.
At Next-Level Tableau, we build these fundamentals deliberately and systematically through structured learning, applied practice, live expert instruction, and a cohort of analysts who hold each other to a higher standard. Teams see measurable skill progression within 90 days, and the compounding effect on analytics quality and team confidence is significant.
If your team is producing technically complex work that still doesn't land with leadership, or if you're seeing inconsistent methods and duplication across analysts, the answer is almost always the same: go back to the fundamentals and build them properly.
That's what we do.
