profile

Next-Level Tableau

Join 10,000+ analysts getting weekly Tableau tips, tutorials, and strategies to design better dashboards, speed up workflows, and stand out in your career. Always free, always clear, always practical.

Featured Post

I’m earning about 5p an hour (and I love it)

This past summer I took six weeks off. I needed the head space, I was burning out, and I needed to give myself the freedom to be with my family and myself. I got back into a hobby I had many years ago, woodworking. I find it incredibly therapeutic and one of those things that makes time fly by. Let me go back to how all of this startd back in summer 2025. Eva found a picture of a mud kitchen in a magazine and asked if I could build it. She had no idea I had done tons of woodworking back when...

I've seen too many analytics managers review work in one of two ways: 1. They either review everything themselves, becoming the team’s bottleneck. Or 2. They wait until a stakeholder complains, then provide feedback after the damage is done. Neither scales. Your analysts need a repeatable feedback process that improves their judgment before work reaches the stakeholder. The fix: use a three-stage review loop 1. Review the question before the dashboard Before an analyst starts building, ask:...

A dashboard can be accurate and still fail. The design can look professional.The calculations can be correct.The data can be refreshed. But if the analyst cannot explain what matters, why it matters, and what should happen next, the dashboard becomes another report people ignore. This is where many analytics teams lose trust. Stakeholders do not experience your team’s technical skill directly. They experience: If analysts understand the problem How quickly they answer questions How...

Two analysts can receive the same business request and produce completely different results. One creates a focused dashboard with clear actions. The other creates twelve charts, inconsistent metrics, and a filter panel nobody understands. Both may be technically competent. The difference is often not effort. It is the absence of a shared quality standard. Without one, every analyst decides independently: Which metrics matter How much context to include How much validation is enough When the...

A technically strong analyst can still produce work the business does not use. Why? Because Tableau skill is only one part of the job. If an analyst does not understand how the business makes money, what leaders are trying to improve, or which decisions matter most, they are forced to treat every request like a reporting assignment. The results are predictable: Analysts build what was requested instead of what is needed Stakeholders ask for dashboards instead of decisions Managers spend time...

Most analytics teams do not struggle because they lack Tableau skills. They struggle because they produce dashboards that are technically correct but operationally useless. The dashboard loads.The filters work.The colors look professional. And nobody changes a decision because of it. That is the real gap between an average analyst and a high-performing one: Average analysts build reports. High-performing analysts create clarity for decision-makers. If you lead an analytics team, review every...

Hey Reader, 3 years ago Eva and I had our first child together. Then something crazy happened. I suddenly felt I had less time! Crazy, I know. You’d think I’d be ready since Annika is my 5th child. I have learned lots of tips to help maximize my time learning Tableau, but the reality is how I saw my time needed to change. Here are some thoughts on time: 1. The 20-minute viz session is real. You don’t always need a long chunk of time to build that cool dashboard or catch up on that class. A...

Hey Reader, When someone asks what you do, avoid saying: “I build Tableau dashboards.” That describes the tool. It doesn’t describe your value. Try this instead: “I help [team or business] make better decisions about [important business problem] by turning data into clear, actionable insights.” Compare the difference: Weak: “I built a sales dashboard.” Stronger: “I helped the sales team identify which regions were falling behind target and focus their attention where it mattered most.” The...

Hey Reader, Strong Tableau analysis usually moves through three levels. Level 1: Overview Start with the big picture. What is the overall result? Is performance up or down? Are we above or below target? Which metric needs attention? Level 2: Diagnosis Next, investigate what caused the result. Break the metric down by useful dimensions: Region Product Customer segment Sales channel Time period The goal is to find the areas driving the movement. Level 3: Detail Only then should you show the...

Hey Reader, Your dashboard should guide the user’s eyes in the same order they should think. A simple layout usually works best: 1. Start with the headline Put your most important KPI or conclusion at the top. Examples: Revenue is 12% below target Customer churn increased this month The West region drove most of the growth 2. Show the trend Next, show how that number changed over time. This gives context. A number by itself rarely tells the full story. 3. Explain the movement Use a breakdown...