The drag-and-drop interface and its flexibility are the product's most valuable features.
Senior Analyst at a government with 501-1,000 employees
The drag-and-drop interface and its flexibility are the product's most valuable features.
What is most valuable?
How has it helped my organization?
It requires only a one-time effort to design worksheets and dashboards. New data can be appended or a whole new set in the same data structure can be loaded to existing working files without much effort to obtain the same results.
What needs improvement?
I would like to see more Excel-like functionalities, perhaps, e.g. the countifs function. It is quite a hassle to code this using query language.
For how long have I used the solution?
I have used Tableau for around one year.
Buyer's Guide
Tableau
March 2025

Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
What was my experience with deployment of the solution?
Hassle-free deployment for desktop version.
What do I think about the stability of the solution?
Initial versions crashed when large data sets were loaded. Subsequent releases were more stable.
How are customer service and support?
Technical support is excellent. Tableau consultants were eager to help.
Which solution did I use previously and why did I switch?
We chose Tableau for its simplicity and ease of use.
How was the initial setup?
For the desktop version, initial setup was straightforward.
What about the implementation team?
The straightforward installation can be performed in-house.
What's my experience with pricing, setup cost, and licensing?
A non-complicated licensing scheme exists for the desktop version. Buy, activate and use. Licensing was easily manageable with a license key that could be activated or deactivated on a system as required.
What other advice do I have?
Try it out to see if it suits your organisational needs. To make the product work as desired, know how it works and implement workaround solutions if that is not readily available.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Senior Business Analyst at a logistics company with 1,001-5,000 employees
It has simpler, cleaner and story-telling charts. Tableau requires less lead-time to develop charts and integrated dashboards for predictive analytics.
Valuable Features
Data visualization: Simpler and cleaner charts, easier for users to perform self-service, not so steep learning curve for non-technical users; good integration to big data Hadoop and predictive analysis, well integrated with other ETL tools. Less-technical maintenance cost compared to QlikView, which requires the developer to do more scripting.
Improvements to My Organization
It is easier for users to do self-servicing; simpler, cleaner and story-telling charts; and requires less lead-time to develop charts/dashboard integration with predictive analytics and big data platform Hadoop.
Room for Improvement
Enhance standard reporting like QlikView (scheduled reports, notifications etc.); for MNCs, the server version license is not cheap; and row-level security: every user needs a DB account, which can give a hacker more opportunity to attack via more DB accounts.
Use of Solution
I have used Tableau for two years.
Deployment Issues
I had a deployment issue: No version control means you can't roll back to earlier versions once overwritten/published.
Customer Service and Technical Support
I rate technical support 8/10.
Initial Setup
Initial setup was straightforward.
Implementation Team
An in-house team implemented Tableau.
ROI
Tableau seems to have easier user acceptance than QlikView because of the simpler charts and big data integration, increasing the possibility of helping an organization transform from reactive analysis to predictive analysis.
Pricing, Setup Cost and Licensing
Server versions are not cheap and pretty similar for both Tableau and QlikView in terms of price. I don't see a big difference; it really depends on your organization's need.
Other Solutions Considered
I also evaluated MS BI and QlikView. Compared with MS BI, I find Tableau and QlikView have stronger visualization; intuitive data insights; less development lead time - MS BI requires creating OLAP cubes, which takes more time; clearer and simpler charts; and intuitive data mapping/insights.
Other Advice
If you have more developers/technical people and want to do more standard reporting without Hadoop, go for QlikView; if you have more business users with some SQL knowledge and would like to do predictive analytics, and integration with big data platform Hadoop, go for Tableau.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Tableau
March 2025

Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: March 2025.
849,190 professionals have used our research since 2012.
Director with 501-1,000 employees
Scalable and flexible for producing visualizations.
What is most valuable?
- Flexibility producing visualizations
- Scalability
How has it helped my organization?
Anything and everything becomes fact-driven; we don't do a lot by gut feeling.
What needs improvement?
ETL functionality is limited, which is both a strength & weakness. It would be nice to have Alteryx & Tableau as a package, but I believe Tableau have deliberately stayed out of the "deep" ETL capabilities to "stick to the knitting", which they have done very well.
For how long have I used the solution?
I have been using it for eight years.
What was my experience with deployment of the solution?
Any issues we have encountered have been related to data preparation rather than the tool itself.
How are customer service and technical support?
Technical support is excellent.
Which solution did I use previously and why did I switch?
I have historically developed using SAP BusinessObjects and IBM Cognos for visualization and various tools for ETL. I have trialed Qlik and Power BI, but this has a much higher level of maturity at this stage.
How was the initial setup?
Initial setup was significantly easier than other products I have used.
What about the implementation team?
An in-house team implemented it. Your investment needs to be in data preparation, then the implementation of any of these analytics tools is much easier. Typically, I spend between 70 & 90% of project effort on data not the tool. If data is well prepared, the Tableau development is very quick and best handled by the business analysts, rather than any tech personnel.
What other advice do I have?
To get the best from Tableau you need:
- Data preparation suitable for analytics applications. (This is not Tableau specific, the same is required for pretty much all analytics apps.)
- People bouncing off each other to get the creative process going. Consider internal show & tells and take advantage of local user groups
- Subscribe to "Viz of the Day” to get exposure to as many viz's as possible
- Tableau is (I believe) the best tool for data visualization. Equally consider investing n the best tools for data preparation, such as Alteryx. The combination of best data prep with best analytics capabilities is MUCH more powerful than either without the other.
Disclosure: My company has a business relationship with this vendor other than being a customer: My company is a reseller, partner, trainer.
QA Manager at Tandicorp
The integration with R for more complex algorithms in analytical data is nice.
Valuable Features:
The most valuable feature is the ease of generating management reports on demand, and ease of generating incremental extracts live or work very quickly.
The integration with R for more complex algorithms in analytical data is also nice.
Improvements to My Organization:
We use it to generate intelligence reports core business of insurance we develop. It is also part of the business intelligence tools we recommend.
Room for Improvement:
Part graphical gauges compliance does not include the Balance Score Card style, however you can develop these graphics, another shortcoming in not having mondrian engines.
Use of Solution:
2 years
Deployment Issues:
We've had no issues with deployment.
Stability Issues:
We've had no issues with stability.
Scalability Issues:
We've had no issues with scalability.
Disclosure: My company has a business relationship with this vendor other than being a customer:
Consultant with 501-1,000 employees
Tableau is an excellent data discovery and visualisation tool, enabling intuitive data analysis without formal training.
What is most valuable?
Easy setup and intuitive drag and drop functionality. Easy connection to a range of different data sources. Range of visualisation models, constantly extending with new releases. Dashboards and story-telling.
How has it helped my organization?
It has allowed a shift from IT-centric enterprise reporting to business-centered development of ad-hoc and enterprise reporting, in partnership with IT. This brings significant extra agility to the organisation and a model of greater co-operation between business units and IT department.
What needs improvement?
As with all products there are many areas that can be improved. Tableau actively encourages suggestions from its user community, allowing for voting on what features to include it future releases. http://community.tableausoftware.com/community/idea
For how long have I used the solution?
3 years, starting with Tableau 6.0.
What was my experience with deployment of the solution?
No significant deployment issues. With a sufficiently resourced infrastructure (CPU/RAM/Storage) the product is easily deployed. Tableau helps with the necessary specifications.
What do I think about the stability of the solution?
It is a mature and very stable product.
What do I think about the scalability of the solution?
Scalability is very good, especially with release of Tableau 8 which brought 64-bit and multi-threading. Extends to hundreds of users on a single server in my organisation without any issues and has capability to include clusters of servers for larger organisations.
How are customer service and technical support?
Customer Service: Very good. Very little need to deal with them on an ongoing basis due to the robustness of the product but on the occasional time we need some help they are very responsive.Technical Support: Initially very good with strong technical support easily reached. As the Tableau user-base has grown quickly there are more formalities to reaching support now but still top-quartile. Again little need to lean on them due to the stability of the product and strong online documentation and forum support.
Which solution did I use previously and why did I switch?
Oracle Discoverer. Switched because we needed to move to a partnership model between IT and Business units. While Discoverer allowed for power users in the business to author reports its metadata layer and underlying database technology required more intensive IT support. Tableau enables the business user while giving more agility to work together to deliver ranges of enterprise solutions.
How was the initial setup?
Straightforward. Get a good server and provision it according to Tableau’s technical advice, install, and you’re away.
What about the implementation team?
Mainly in-house, some support from Tableau themselves and also a local Tableau partner. Expertise of partners not great at the time in Europe but has matured considerably over the last few years.
What was our ROI?
Commercially sensitive.
What's my experience with pricing, setup cost, and licensing?
Commercially sensitive.
Which other solutions did I evaluate?
Sas Microsoft SSRS Qliktech Oracle OBIEE Microstrategy
What other advice do I have?
Assess your own strengths and create a preferred architecture. Then see if Tableau fits some of your needs. For anything significant in scale you will need a robust underlying data architecture, it won’t do all of your ETL. While it is possible to create and deploy artifacts very quickly without formal training, it is worth sourcing some to help you leverage the best features of the product.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Consultant at a tech consulting company with 51-200 employees
Qlikview vs Tableau? I have to choose and I’m not sure
Most users love Excel, non-users hate it. When it comes to data visualization, Excel is generally dispised, except by those that have to make dozens of charts every single day. I call this the Excel Stockolm Syndrome. These are the forsaken data visualization users that keep making 3D pies when they should know better by now. Tired and overwhelmed. Not in the mood the learn yet another tool just to make those elusive “effective charts”. If you link good visualization to a tool they have no access to, you can be sure that the whole message is lost.
Becoming a Data Visualization Anarchist
I think things can be changed from the inside, improving the way people use Excel. I write for Excel users because I’m one of them. That’s not going to change soon. But I love data visualization, not the tools that make it happen. I specially like interaction, multiple charts and making them available on the web. And I need to manage more data (not big data, just more data). Some things can’t be done in Excel or require too much effort.
The Portuguese poet Fernando Pessoa has a funny short story called The Anarchist Banker. The idea is that only a banker can be a true anarchist, because only a banker can be free from “social fictions”, specially money… In data visualization, this means getting the tools out of the way, by learning them or avoiding them.
I chose the learning path and I’m learning R now. I always wanted to make those scatterplot matrices. And I want to play with the ggplot2 package. A programming language is covered but R is not going to pay the bills.
Enter Tableau and Qlikview
I will not complicate matters by discussing how I chose Tableau and Qlikview and not Spotfire, for example. I just want to choose one. Qlikview vs Tableau. Comparison articles like this and this are very helpful, but a man is a man with his circumstances. Each starting point is different from everyone else. Let me tell you what I think I know about these tools in this early stage.
Tableau
I like Tableau, I have to admit it. I like the fact that you don’t have to fight stupid defaults in design and formatting, because I share the same data visualization principles.
I like its enthusiastic and knowledgeable community. Let me give you two simple examples. I spent a lot of time making this horizon chart in Excel, and Joe Mako quickly came up with a better version in Tableau.
Then I tried to be creative with the bamboo charts and Joe Mako strikes again, with a better implementation. I’m starting to get nervous… (kidding)
I know and respect many Tableau users, not because of Tableau but because I share the same views regarding data visualization.
Apparently, maps in Tableau are good enough, so that’s a good point.
And as a blogger, I want to make my work available to the web, and Tableau Public is a nice option (my population pyramid).
The Guardian often publishes Tableau visualizations. I’d like to try that with the local newspapers here.
On the other hand, we know how stubborn some datavis experts are. Is Tableau that stubborn? Can clear vision and the right principles become a straitjacket? I really hate straitjackets (“the idea of”, never actually tried one…)
In my country, Tableau is virtually unknown and I am not sure if I want to sell shoes in Africa.
Qlikview
I know even less about Qlikview. The first chart I see in its video is the pie chart above. Not exactly a shiny example of good data visualization principles.
Apparently there is a very active Qlikview community on Linkedin but not so much on Twitter. Probably this is meaningful.
I keep reading that Qlikview is better than Tableau when it comes to making dashboards, while you should explore the data with Tableau. It’s a good point in favor of Qlikview (that’s what I need now). Extensions and the market seem to be interesting too.
Qlikview has several business partners here. Actually, I was invited to work in some Qlikview projects in 2013 (obviously I have to learn the basics until then). They can pay a lot of bills.
Its not always about features
Not everything is black and white, not everything can be decided based on feature-by-feature comparison. Not everything is heart, not everything is reason. If I choose Tableau, my data visualization skills will improve a lot. Qlikview is harder to predict. I’m sure there are many users that dislike the pie above. If not, Qlikview can be more, hummm, challenging.
What I’m going to do
I mentioned those Qlikview projects, but I’ll try to remove them from the equation, at least for now.
I have a simple dashboard in Excel and I’d like to create Tableau and Qlikview versions. That’s probably one best ways to evaluate a tool, using my own work.
So, can you help me?
I’d love to learn from you. Can you answer questions like:
- How do they compare regarding maps? Is it simple to add your own maps?
- Is it true that it’s easier to make a a centrally designed dashboard in Qlikview, while Tableau has a more exploratory nature?
- How can I share a Qlikview chart in my blog?
And please don’t tell me I have to learn both…
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Thanks Jorge!
Subject Matter Expert, IT Operations Management, CS Professor at a educational organization with 501-1,000 employees
Good data visualization features like heat maps and story boards
Pros and Cons
- "I like Tableau's heat maps and the storyboard. You can create data stories and tons of visuals with it, and it goes together really well. Tableau lets you manipulate the data in various ways."
- "The price of Tableau is too high."
What is our primary use case?
I'm a computer science professor and I teach analytics. We use Tableau to teach students how to develop visualizations of data sets.
What is most valuable?
I like Tableau's heat maps and the storyboard. You can create data stories and tons of visuals with it, and it goes together really well. Tableau lets you manipulate the data in various ways. But since we are teaching, we have to accommodate the needs of the students. Often, we have to go back to basic stuff like Excel because that is what the students will be working with at whatever jobs they get. So we try to use the type of tools that their workplace will offer. We know Excel is widely used and Tableau is not.
For how long have I used the solution?
I've been working with Tableau for about half a year or so.
What do I think about the scalability of the solution?
It's an individual solution so it works on as many desktops as you can download it to.
Which solution did I use previously and why did I switch?
We were using Azure, but we're trying to get away from that because Microsoft is very expensive. We're trying to keep our expenses down while trying to find some decent products.
How was the initial setup?
Setting up Tableau is straightforward. You just can download it and set it up on your system in five minutes.
What's my experience with pricing, setup cost, and licensing?
The price of Tableau is too high.
What other advice do I have?
I rate Tableau eight out of 10.
Which deployment model are you using for this solution?
On-premises
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Delivery Lead at UST
Mature, easy to use, and connecting to OBIEE works well
Pros and Cons
- "It's intuitive and highly mature"
- "The customization in the front end is a bit difficult."
What is our primary use case?
I am a developer and I provide solutions to end-users using Tableau.
What is most valuable?
It's intuitive and highly mature.
I use OBIEE, which is in Tableau. It is much easier than in other tools and it is easier to bring up the data insights.
What needs improvement?
The customization in the front end is a bit difficult. If they provide any utility or UI feature, where a user can do their own customization it would be great.
I would like to see an option to customize your own reports. Not being able to customize is a pain point for the developers.
For how long have I used the solution?
I have been using Tableau for six years.
How are customer service and technical support?
Technical support is good, but they could use some improvement. I would rate the technical support an eight out of ten.
There can be some delays in resolving issues because of the difference in time zones. The need to come with a way to match the time zones.
What other advice do I have?
I would recommend this solution to others but it would depend on their use cases.
I would rate Tableau a nine out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partner

Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros
sharing their opinions.
Updated: March 2025
Popular Comparisons
Microsoft Power BI
Teradata
IBM Cognos
Amazon QuickSight
SAP Analytics Cloud
Domo
SAP BusinessObjects Business Intelligence Platform
Oracle OBIEE
MicroStrategy
Oracle Analytics Cloud
Salesforce Einstein Analytics
TIBCO Spotfire
ThoughtSpot
Sisense
Board
Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- QlikView or Tableau - Which is better?
- What's your experience or opinion about Spotfire vs. Tableau vs. Qlik?
- I currently use Panorama Necto as a viewer on SQL Analysis services cube--what other solutions are out there?
- Business users moving from Tableau to MS Report builder
- Tableau vs. Business Objects - Which is a better solution for visualization and analysis?
- Tableau vs. Spotfire - What do I need to know regarding pricing and usability?
- I'm looking for real info about licensing, ease of setup and other costs involved. Can you help?
- Tableau 10: Best New/Improved Features
- A journalist is writing a story about which Data Visualization software product to choose. Can you help him?
- Tableau vs. QlikView - functionality and pricing schemes
We offered R via Tableau to our Data Scientists. They had tried it and rejected it since they couldn't use the R's built-in Plot because it is more flexible than anything you'd find in TB for layering unless you want to spend time designing an R3 visual and importing it. TB is a great tool and we do use it here.