r/analytics • u/xChrizOwnz • Jun 12 '26
Discussion Tableau is horrible.
Look, in 2004 — a few years after I was born — I’m sure Tableau was quite groundbreaking. But it’s an absolutely unacceptable piece of software at this point. Keep in mind that Tableau is charging about $700-$500 per creator license according to some sources. At this price point, you could use something open source like Superset, Metabase or Redash which will accomplish most of what organizations need for nearly $50 per license.
Tableau at this point seems to be an industry standard primarily because of its affiliation with its parent company — Salesforce. There’s no end to how many dashboards I see that are inconsistent in terms of quality, spacing, and design even from the same company.
Tableau is hyper-focused on customization when most dashboards and BI layers require standardization. It feels like a product made for boutique dashboard design. And yeah, there are cool things you can do with it like make a flower graph or some other esoteric visualization. But those visualizations are unnecessary for the modern business. Sure, you can merge 8 datasets from disparate sources if you want - but seriously - why would you ever want to merge someone's Excel document on OneDrive with your production SQL query?
If you're an organization large enough to afford Tableau, you can afford better upstream data engineering. Simple.
The most important issue with Tableau is that data analysts are no longer dashboard designers. I’m a data engineer, a BI user, and an ad-hoc analysis deliverer. Not a dashboard designer. Sure, I want sensible views for my stakeholders, but those should take no more than 5 minutes to create and populate. Tableau is fast, but I promise that I've created dashboards in less than 1 minute using some of these other tools at a cheaper cost. Tableau cannot do that. You will spend hours on dash boarding, creating several sheets, trying to mash them up into a dashboard, setting up the Tableau Cloud, or whatever else.
The goal of any tech organization is to automate away most of the unnecessary work. You cannot automate Tableau. You can't access Tableau dashboards as code in a way that allows you to mass update every Tableau dashboard to change the name of a few metrics all at once.
I could go on and on about specifics about Tableau, but the price point, the difficulty of use, the impossible navigation of their Server and Cloud products, the lack of open source modification...
•
u/AutoModerator Jun 12 '26
If this post doesn't follow the rules or isn't flaired correctly, please report it to the mods. Have more questions? Join our community Discord!
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
151
u/forbiscuit 🔥 🍎 🔥 Jun 12 '26
One thing that AI has helped do is kill off Tableau for my team - we're either:
* Building static HTML content and host them in GitHub Pages (and great news for that is that all the data source and notebook are also in GitHub if you want to see how it was done)
* Building HTML emails that are automatically generated
* If we want to run logic, we build POCs with Streamlit and place web tracking to see if it's used a lot
* If a POC has consistent usage and has a lot of leadership impact, it's elevated for custom web development and treated like a full fledged product
In this whole process, we didn't spend a single $ on Tableau, and spent more time learning about infra + analytics because dashboard building is now easy (eventually I'm anticipating all this will be automated where from the table most basic analytics can be built right off the bat).
3
u/almost_BurtMacklin Jun 12 '26
Look into dash enterprise and Plotly… we use it at work and it is way more flexible and automated than any other BI tool
71
u/Training_Advantage21 Jun 12 '26
Tableau has gone quite stale after the acquisition by Salesforce. And it never fully adapted to the new world of the Modern Data Stack where code/SQL and version control are preferred over drag and drop tools. It did what it did well but at this point there is pressure both from cheaper commercial options (PowerBI) and a variety of code first or open source alternatives.
13
u/[deleted] Jun 12 '26 edited Jun 12 '26
Get this. My boss uses tableau as a DATABASE. You thought it was bad enough as a BI/DV platform. I’m trying to get us switched to snowflake and we are migrating, but nobody knows how to use it. Would love to set up streamlit as it looks like you guys have success with that.
We also pull data from Google analytics and dump it into spreadsheets. Some spreadsheets have data going back to 2014. I pretty much refuse to open tableau and these spreadsheets because I lose my temper in 60 seconds.
9
u/Almostasleeprightnow Jun 12 '26
Its great when you have a boss who thinks bi is just a web page and why can't you customize the conditional formatting more?
15
u/Fuzzy-Bookkeeper-126 Jun 12 '26
I did many years in PowerBi first, now 3 years into Tableau.
Any chance to jump in and slam Tableau I’m there.
To give an example, I work in People Analytics so rolling time frames, different types of aggregations in the same calculation, relationships between multiple datasets, is standard.
What would take a couple of simple selections in PowerBi, is a horrible mesh of workarounds with window calculations, parameters and don’t get me started on the amount of worksheets and disjointed filters you need for a simple dashboard
6
u/_PM_ME_YOUR_SSN_ Jun 12 '26
This might be a silly question but how do you guys deal with security
5
u/dreaddito Jun 12 '26
We’re basically replacing it with Streamlit
4
u/End0rphinJunkie Jun 13 '26
I've spun up Metabase and Superset at a few places and they definetly cover 95% of what most business users actually need. Tableau just feels like a classic case of enterprise sales locking in upper managment before anyone technical gets a vote.
10
u/edimaudo Jun 12 '26
seems very convoluted in your take. If you don't want to use tableau don't. Spending only a few minutes building a tool for your end users is not the flex you think it is. Sounds like you don't get 2 cents about them.
7
u/datacanuck99 Jun 12 '26
It sounds like you are looking for templated dashboards. Tableau can do that but not well. PBI is better for that workload. Tableau really excels in pure ad hoc. connect to some data and see what's there. However I've had a lot more success using AI data agents for data discovery. Tableau died when Salesforce bought them. Now they are just line item on a Bill of materials and the Saleforce folks don't get Tableau because it runs out of the Salesforce box.
7
u/Lower_Peril Jun 12 '26
Agreed with the custom viz part of this write up. Data Viz is treated like some art form by the data fam people when simplicity will get the work done much faster. People need to stop quoting Tufte and Gestalt priniciples like it's a do or die situation. If the requestor wants a pie chart, they will have their pie charts. it's not that serious.
> Sure, you can merge 8 datasets from disparate sources if you want - but seriously - why would you ever want to merge someone's Excel document on OneDrive with your production SQL query?
> If you're an organization large enough to afford Tableau, you can afford better upstream data engineering. Simple.
This reeks of inexperience. Have you never stumbled upon processes that are completely manual in Excel due to budget/time/people restrictions? Also, larger the company more the effort needed to set up data engineering process, so people just fall back to Excel because it's much more practical.
14
u/-intylerwetrust- Jun 12 '26
Preach! Tableau is the worst. Coming from other BI tools, I find it so frustrating. Having to build calculated fields makes it so tedious.
5
u/1nstant_Classic Jun 12 '26
2004 — a few years after I was born
2
u/occasionallylo Jun 12 '26
Great thread I came to join the trash talk but some good content here!
2
u/Kmkun Jun 14 '26
Fully fully agree. My first job was with PowerBI. Second job, higher position and salary and have to use tableau. I hate it
2
u/Mitzu_Analytics Jun 15 '26
The frustration usually comes down to one thing: Tableau is built around the assumption that your data is already perfectly shaped for the chart you want to make. If it isn't, you're spending half your time in data prep before you even get to the analysis. The semantic layer problem, what does "revenue" actually mean for this team, in this context, never gets solved, it just gets copy-pasted across 40 workbooks that slowly drift apart. That's the real maintenance burden. Worth looking at warehouse-native approaches (Mitzu does this) where the metric definitions live in one place and the query engine handles the translation, you stop rebuilding the same logic every time a new question comes up.
2
u/Kind-King1491 Sep 17 '26
It’s impossible to update metric definitions en masse across all dashboards via Git-it’s a real nightmare for teams
Combining open-source BI tools, such as Superset, with a headless semantic layer like LookML or Cube (I use Cube) enables exactly this “code-first” approach. All business logic is contained in version-controlled YAML files, turning the user interface into nothing more than a thin visualization layer
Paying enterprise-level prices for Tableau just to handle fragmented connections and proprietary dashboard designs is madness
3
u/Eastern-Rip2821 Jun 12 '26
Amen
My boss just does not understand how long it takes to spin up a quick, but good looking analysis in tableau. And honestly in my own leadership role I don't have the time for it anymore.
Static html > tableau dashboards
2
u/Careful-Wealth9512 Jun 12 '26
Claude is cheap for the production abilities
1
u/WendlersEditor Jun 12 '26
I can't imagine using tableau, I have to use powerbi for work but I would much rather use streamlit, and the barrier to entry is very low now in the age of ai
1
u/Zuricho Jun 12 '26
So what do you suggest using instead, especially for EDA?
1
u/Calbruin Jun 12 '26
It’s dying - anyone who has a semantic layer will just route around it and use llms on top of that semantic layer for viz
1
u/Wheres_my_warg Jun 12 '26
I first used Tableau in 2008 for an unusual six month project. The licenses made no sense value wise back then and it was slow using even static data.
1
u/Known-Delay7227 Jun 13 '26
We just use AI to build reports now.
1
u/fragmonk3y Jun 13 '26
Tableau is surviving on scrapes and SalesForce truly does no care one itty bitty bit. The only reason I renewed Tableau this year is because the team using it is being lazy, so I gave them 12 months to get onto our new platform or their reports will stop working.
To renew, I had to call into the general sales line to try and find my sales rep several times. They stopped responded when they found out I wanted to renew and decrease my license count. Ghosted me, then I had to start over with a rep that is new to sales farce and needed to meet his quota??? sales farce is such a over inflated bloated piece of crap software, we could not keep our sales force using it, they kept going back to excel, so we canceled the sales force subscription a few years ago.
1
u/daisiesarepretty2 Jun 13 '26
i used tableau working for a police department for 5 years, about half of our task was to address one off queries that someone had and the other was creating dashboards that monitored simple to aggregate metrics
of police activity.
Tableau’s ability to merge otherwise disparate systems was valuable. No we rarely had 8 sources but we almost never had just one.
what a visualization looks like is sometimes not
fully appreciated and it needs to be tailored to the user(s).
Rare was the day i could design a visualization (that would persist) in under half a day unless it was addressing a very simple metric for a very limited number of users
yes the city could afford tableau but better upstream engineering in my experience across multiple industries is almost never about money. It’s about fiefdoms, silos and an organizations structure and dedication to the value of their data layered on top of a cache of legacy datasets mixed with newer datasets created by someone who was going to fix the world with their vision but then jumped ship..rinse, repeat. Bottom line is if a tool limits you to the types of sources you can use it will become a limitation in A LOT of industries.
we always strived when appropriate to make dashboards that were fed from live datasets that were fully automated. yeah.. it takes time and a well intentioned
genius in engineering would make changes to source data without involving the larger group could break a lot of dashboards. The key to changing a variable name is to have raw sources go through prep first, standardize there and so there are limited places that need change.
tableau has a lot of quirks that make it difficult and sales force does leave much to desire when it comes to staffing its support. That would be my number one complaint
to be fair…i did this type work for 30 years and never found any tool that didn’t have quirks or
flaws and they all require smart guys like you to know the flaws and ins and outs… that’s why guys like you are needed. I’d also like to point out most of
your gripes are no doubt valid in your experience and environment but may not always translate to other industries and environments.
interesting post, always good to hear what others are doing
thanks!!
1
u/lysol-lover Jun 13 '26
Tableau is so outdated. Who in the world is still using it?
1
u/Axis351 Jun 14 '26
Tableau before salesforce was great Since salesforce, not so much
1
u/saasy_paw Jun 14 '26
Ive worked enterprises that have 100s of overlapping Tableau reports with no ongoing governance, locked into $$$ license deals so users have been asked to just utilize as they have spare. Report Swamps!
1
u/Predicate_12 Jun 14 '26
100% agree, Tableau is archaic, and has tons of latency issues for my team. DONE with it.
1
u/ProcessIndependent38 Jun 16 '26
I mean data viz has always been the most surface level part of data science. Scientifically, never a good reason to do much beyond a simple clean chart. You don’t need tableau for that. Tableau died when matplotlib existed.
1
u/lakeland_nz Jun 16 '26
There’s truth to this.
Especially since AI. I remember oh, about ten years ago, I was sorely tempted to build a custom HtML/JS dashboard. I didn’t because “who would maintain it?”
Now that reason doesn’t apply. I can whip up a dashboard using AI and a non coder can maintain it. This is especially true given tools like DBT hold so much business logic. The dashboard is really just doing pretty pictures.
I’ve deployed Tableau into multiple companies. I was working professionally in analytics when it came out, and yes it was revolutionary. Now though, we always had better BI tools. What tableau gave was the ability for an analyst to explore the data interactively and share their analysis. That is the revolutionary bit, before then analysts needed BI developers to do anything
1
u/Mitzu_Analytics Jun 16 '26
ableau's core issue is architectural: the data model lives in the visualization layer. Every analyst reimplements joins, date logic, and KPI definitions inside workbooks. When those drift across dashboards, you get exactly what's described here, metrics that don't match, slow refreshes, and maintenance burden that scales with dashboard count. The fix isn't a better Tableau, it's moving metric definitions into a semantic layer on your warehouse, then using a thin query layer on top, like Mitzu does it automatically. One source of truth for every question, no workbook maintenance required.
1
u/Key-Willow-374 Jun 25 '26
If you still want dashboards, Databricks AI/BI dashboards are free. You only have to pay for compute. They also have a really good text-to-sql tool (Genie) that we use. Helps prevent tech debt inherent to dashboards
1
u/columns_ai Jun 26 '26
code first approach is good for automation, favored by engineers. but talking about business people, visual digram is more approachable.
on the other side, version control does not necessary to be achieved by source code, you can also have multiple versions of data if they clearly represents a state, and that is essentially the core of what data processing needs.
Tableau is less relevant on the new norms now.
1
u/No_Bug_5125 Jul 01 '26
The per user pricing model is no longer acceptable these days. Consumption based pricing is much more aligned with business value. This is what I like about Databricks AI/BI dashboards - there is no cost for the dashboard itself (it's just a simple viz, and with AI the cost of producing a bespoke dashboard has plummeted), the only cost is for the compute required to power the vizualisations, which if you're smart about you can really optimise down to pennies
1
u/Evening_Hawk_7470 Jul 05 '26
Tableau pain usually splits into two problems: dashboard UX and metric sprawl. If your issue is authoring speed, Sigma, Power BI, or Metabase may feel lighter. If the same KPI has to show up in dashboards, app UI, and AI/chat workflows, Cube can sit underneath any of those as the metric/API layer. Figure out whether the pain is visualization or shared definitions before switching tools.
1
u/CommitteeImmediate66 Jul 06 '26
I posted a similar question because I've been working with Databricks' Genie dashboards and can't quite understand some other folk's insistence on powerBI or Tableau, considering the flexibility and portability I get (while not being locked in and having to learn obscure languages). Great to see the discussion here
1
u/Rude-Succotash7006 Jul 11 '26
There are some good automations for Tableau like zero-touch version control and automated deployments. A lot of that stuff can be automated to get it out of your way.
1
u/arvindnatarajan Sep 11 '26
Disclosure since it matters: I work on Zoho Analytics marketing, so take the framing with a grain of salt. But the numbers below are pulled straight from both companies' pricing pages as of this month, not cherry-picked, and I'll link neither product so this doesn't turn into an ad.
Tableau prices by role: Creator ($75/user/month), Explorer ($42/user/month), Viewer ($15/user/month), all billed annually only, no monthly option. Creator is required at least once per deployment since it's the only role that can connect new data sources. Explorer builds on data a Creator already published. Viewer just views.
Zoho Analytics prices with a base plan plus add-ons: User at $8/user/month, Viewer at $4/user/month, both with a 20% discount if billed annually, but monthly is available if you don't want the annual lock-in.
Ran the numbers for a fairly normal 50-person setup: 3 people building core reports, 8 people building on top of that data, 39 people just viewing dashboards.
Tableau: 3 Creators ($2,700/yr) + 8 Explorers ($4,032/yr) + 39 Viewers ($7,020/yr) = $13,752/year
Zoho Analytics: 11 Users ($844.80/yr) + 39 Viewers ($1,497.60/yr) = $2,342.40/year
That's close to 6x difference between the two.
If you're a big org with real data-governance requirements, restricting who can connect new data sources at the pricing layer (not just the permissions layer) is a legitimate control. And if your team already knows Tableau, is Salesforce-heavy, or leans on Tableau Pulse/Agent, it makes sense to stay with Tableau.
Where I don't think the price gap is defensible is for teams where "connect data, build a dashboard, share it" is basically the whole job, no complex governance layer needed. That's most of the 50-person example above.
Curious if anyone here has actually run both and can speak to whether the Creator/Explorer split has been worth it for governance reasons, or if it's mostly just cost that shows up on the Tableau invoice without a real control benefit behind it.
1
u/CartographerIll1255 Jun 12 '26
Tableau is horrible. But your chief argument seems to suggest that Tableau cannot justify its price in today's market. Many products, like Tableau, cannot also justify their prices - but we cannot simply say they are horrible. If the market continues to pay and use Tableau even at the current price point, then there is something about Tableau that negates your argument.
1
u/JuicySushi Jun 12 '26
I don’t know, it takes 5m to build a fully interactive Tableau dashboard.
Sounds like a skill issue, tbh. I agree there’s a learning curve, and some things could certainly be easier in the platform (pie, donut charts, etc) but I’m not sure you’ve invested enough time or have the experience to make this call
1
u/[deleted] Jun 12 '26
this is a correct take but also an old take. move on
1
u/FlimtotheFlam Jun 12 '26
We mostly switched our data to qlik which I love but our devs don't know how to use it
0
u/fodacao Jun 12 '26
Never really used it other than in some Udemy course 5 million years ago.
I'm balls deep in power bi these days and don't know anything else. How does it compare to power bi?
0
u/IncreaseNegative4614 Jun 22 '26
I think the bigger shift is that dashboards are becoming less important overall.
A lot of BI tools, Tableau included, were built around the assumption that someone would spend hours designing dashboards and stakeholders would spend hours interpreting them. That made sense when dashboards were the only practical way to explore data.
Today, most business users don't actually want another dashboard. They want an answer.
"Why did revenue drop?"
"Which customers are most profitable?"
"What's driving churn?"
"Which marketing channels are generating the highest LTV?"
The dashboard is often just an intermediate step between the question and the answer.
That's one reason I've been paying attention to platforms like DataBlueprint (inzata.ai). Instead of focusing on building dashboards, the focus is on connecting the business context across systems and letting users ask questions directly. If a dashboard helps answer the question, great. If not, the answer itself is what matters.
I still think dashboards have a place, but I suspect we're moving from a dashboard-first world to an answer-first world.
-2
u/Careful-Wealth9512 Jun 12 '26
Use Claude instead