Tableau Desktop - The product is easy to use, and does not require IT skills. I can create dashboards and connect to databases very easy and quickly.
Director of Analytics at a tech services company with 51-200 employees
Easy to use and does not require IT skills.
What is most valuable?
How has it helped my organization?
We experienced an 80% reduction in the amount of time it takes to prepare reports and dashboards using Tableau. Before that, we had to use Excel spreadsheets and that consumed a lot of time to prepare data monthly. In addition, there was a problem related to the amount of lines in Excel that are not enough for our database.
What needs improvement?
I’d like to see a better ETL preparation engine.
For how long have I used the solution?
I have been using Tableau Desktop and Tableau Server for four years.
Buyer's Guide
Tableau
October 2024
Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,406 professionals have used our research since 2012.
What was my experience with deployment of the solution?
The product is very stable and ease to deploy. We can deploy an enterprise solution in two days.
How are customer service and support?
Technical support is very helpful and provide quick answers. In addition, their technical support is in many languages, which is very helpful when you face some issues.
Which solution did I use previously and why did I switch?
I previously used QlikView and MicroStrategy, and they are not as friendly as Tableau for the end user. If you do not have IT skills, you probably will be stuck with a basic level of visualization.
How was the initial setup?
For simple and more complex setups, it is easy to set up the product without too many issues.
What about the implementation team?
If you want to start with Tableau Desktop, you can choose an in-house implementation, but if you are going to set up an enterprise solution, my advice is to use a vendor team to support your implementation. It will be faster.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing model is very simple. There is one price for Tableau Desktop and two types of enterprise prices. You always know which price you are going to pay.
What other advice do I have?
If you have a lot of databases to bring together, you might experience some ETL issues. But in the next release, version 10, the product will have a cross-join database, and that will help a lot to bring in many datasources.
Disclosure: My company has a business relationship with this vendor other than being a customer: Partners
Senior Engineer Business Intelligence with 10,001+ employees
We already had an ETL solution in place, so Tableau complemented it well for our use cases.
What is most valuable?
There are many features which I can speak about, but its overall ease with which you can analyze your data within a couple of clicks is an outstanding feature. Also, the stunning visualization with lots of statistical options, makes it a valuable product.
How has it helped my organization?
When we started with Tableau, it was basically used for converting existing Excel reports. But later on, after exploring the features and with latest releases, it had a greater impact on the way we interact with the data. We were able to connect the data from different source of data together. We were able to relate the defects, quality and cost aspects of the products of our company from different regions in a much more efficient way. The visualizations gave a better picture of the current state of affairs and we got an idea of what needs to be improved in the line of business. Now, Tableau has become an integral part of our organization for any analytical solution.
What needs improvement?
Tableau comes out with one major release every year and minor releases frequently, which is very good. Also, most of the changes are done based on the ideas posted on the community, which means it listens to the user base to come up with the changes, which is phenomenal.
As far as the changes I would like to see, they could improve performance with respect to big data connections and cube data sources. Many users in my organization feel that Tableau is great with RDBMS, but with Hadoop or cube data sources, the performance is not so great.
For how long have I used the solution?
I have been using Tableau for nearly four years for the majority of my reporting and analytical solutions.
What was my experience with deployment of the solution?
We did not face any issues with deployment, stability or scalability. The deployment was simple and we have not faced any issues until now.
How is customer service and technical support?
I would rate customer service and technical support as 9/10, excellent. The turnaround time for any issue is very good.
How was the initial setup?
The initial setup was straightforward. The only thing you have to check is for hardware compatibility. The rest is very simple, with just a click of a button.
What about the implementation team?
As implementation is simple, we preferred an in-house team. But you will get assistance from a vendor team if required.
What was our ROI?
ROI depends on how effectively you utilize the tool and explore the data.
What's my experience with pricing, setup cost, and licensing?
Pricing of the tool would be expensive for any small organization. I would suggest sitting with the vendor's relationship manager to discuss your strategy and the pricing model you’re looking for.
Which other solutions did I evaluate?
We explored other tools such as QlikView and Pentaho, but Tableau stood out in terms of its ease of use, great visualizations and simplicity. We already had an ETL solution in place, so Tableau complemented it well for our use cases.
What other advice do I have?
Tableau is more than a reporting tool; it has the analytical capabilities which need to be explored efficiently to get the best out of the tool. If you just want to replicate an Excel report, it would not help much in terms of ROI.
Tableau is a very good analytical reporting solution. It is improving its features with every release.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Tableau
October 2024
Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: October 2024.
816,406 professionals have used our research since 2012.
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?
The drag-and-drop interface and its flexibility are the product's most valuable features.
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.
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 technical 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.
Director at a tech services company
It has extended the native capabilities of various type of data sources (database, big data).
What is most valuable?
Self-service: Its ease of use means Tableau can be operated by business users. It is aligned with the mission “Help people see and understand the data”.
How has it helped my organization?
Tableau has extended the native capabilities of various type of data sources (database, big data). There are also significant features at the map and features level of detailed expressions.
What needs improvement?
With the Device Manager in Tableau 10, you can design, customize, and publish a single dashboard with optimized views for tablets and phones.
Other features include clustering segmentation data and a custom territories map.
For how long have I used the solution?
I have been using it since 2012 (four years).
What was my experience with deployment of the solution?
We encountered issues with Tableau 8. However, since Tableau 9, there has been significant improvement.
How are customer service and technical support?
I rate technical support 8/10.
Which solution did I use previously and why did I switch?
We evaluated others, but Tableau is the business intelligence platform which allows everyone to use the product in a way that supports how they work with data.
How was the initial setup?
Tableau is easy to be deployed from the beginning, from the desktop up to Tableau Server, which you can implement at the organization level.
We have implemented Tableau in organizations of up to thousands of users.
What about the implementation team?
We are a Tableau partner. We provide system integration services to our clients. We begin implementation by focusing on a specific subject area where it is the most important and it will have a significant impact for executive management.
What's my experience with pricing, setup cost, and licensing?
Research the variety of licensing schemes and choose the best one for your organization.
What other advice do I have?
Try it first by downloading the trial license. You will love it and experience how easy it is to use the product.
Disclosure: My company has a business relationship with this vendor other than being a customer: My company is a Tableau partner.
Business Intelligence Director at a tech services company with 51-200 employees
We evaluated other solutions, and selected Tableau mainly because of the licensing costs.
What is most valuable?
Self-service.
How has it helped my organization?
Talking about self-service, now we can provide information enterprise-wide. Before Tableau, about 15% of the organization had access to information; now with Tableau, about 80% of the organization have access to our data warehouse, and other information sources such as Excel and SQL Server databases.
What needs improvement?
Well at this point, we are in the process of implementing the in-memory feature for our costing process. We need to have online costing information. We think if we have more parameters or tools to customize this feature, we can improve the performance in the processes that generate and load the information.
For how long have I used the solution?
I have used it for two years.
What do I think about the stability of the solution?
We can tell you that Tableau 8 had issues mainly with SQL Server databases, but with Tableau 9 and above, the issues with SQL Server have been solved and now we have a very stable solution.
How are customer service and technical support?
Our local vendor support (in México) was so bad!!! However, we have encountered in the online support a very good source of information that helps to solve our issues. In fact, we have submitted a lot of cases to the Tableau support team, with very fast responses.
Which solution did I use previously and why did I switch?
We evaluated other solutions, and selected Tableau mainly because of the licensing costs.
How was the initial setup?
The initial setup was pretty straightforward; we only had one issue with the Active Directory configuration.
What about the implementation team?
Our in-house training program consisted of two teams for one week: one team for Tableau administration, and one team for Tableau super users.
I think that it is good advice to consider a well-organised implementation program.
What was our ROI?
I don’t have authorization to provide numbers for our organization, but I can say that Tableau is a product with great price performance.
What other advice do I have?
Tableau is a user-friendly product, but I think that is very important to consider a well-organised training program based on the user roles (administrators, super users, information consumers, etc.).
Disclosure: I am a real user, and this review is based on my own experience and opinions.
BI Expert at a non-tech company with 51-200 employees
Top 3 Tableau Fears
Yup. It exists. And it comes in many forms. I've done a lot of Tableau presentations to managers and analysts over the past couple of years and the same concerns keep cropping up.
- The Elusive Single Version of the Truth - (the Sasquatch of data fear)
This one is usually expressed by upper management frustrated with being confused about the numbers they are being presented with and having to ask for all the details about the data in order to trust that taking action on those numbers will be worthwhile and/or safe.
Those of us in the analysts army know that this is a red herring and has absolutely nothing to do with Tableau or any other tool. There is no single version of the truth. There are 'truths within context'. A problem exists when that context isn't transparent. For example, different departments will create different versions of the same named measure with inclusions/exclusions that are pertinent to their work. So the results may be valid in one circumstance, but not when considered for another.
What is needed is proper data governance, open communication and collaboration/sharing of information. More importantly, it is the analysts duty to note definitions and sources within the reports. Remember, that report will go out into the world (or rest of the organization) without you there to explain it.
- The Dreaded Spreadmart Invasion -
This fear is often expressed by those in BI departments as it was once believed that BI departments could help us get control over the Excel invasion. Spreadmarts have existed since humans started putting numbers down on paper. It's why we invented filing cabinets. Once we all got our hands on Excel, our filing and co-ordination system became inadequate. Most organizations have a filing problem, not a reporting problem and it certainly wouldn't make sense to stop access to the analysis tool to gain control. That would be like a library ignoring the dewy decimal system and not allowing people to borrow books because it was too difficult to keep track of them.
Managing the implementation of Tableau within the organization provides the opportunity to address this problem: set up proper Projects and Groups, build and co-ordinate access to data sources, assign senior analysts to review and vet workbooks before publishing, and most importantly SHARE best practices and learnings.
- SS Data Security -
This fear is completely legitimate and ridiculous at the same time. There are already people with access to data who have no business having access to data. Try and weed them out. I have worked in places where the server (SQL) was inaccessible for days because a 'senior' analyst has left a badly built query running and forgotten about it. Seriously. My point here is that if you are concerned that certain people shouldn't have access to data connections with Tableau because they might pull all the data and freeze everything, well, they would be doing that same thing with any tool tool you gave them. They can even do it with Excel.
One of the great things about Tableau is that you can share the data if you choose. You can set up a data connection, put limits on the amount of data it pulls, do the analysis, prepare the dashboard and send the workbook to someone without having to publish it. If they have Tableau, then they can open it up and use the data to conduct more analysis. If they have rights to the connected data, then they can refresh it. You've limited the amount of data that can be pulled (e.g. rolling 12 months), so they can't crash the system. If you have Server, there's even more options.
All three of these issues can be addressed through COLLABORATION. Instead of creating rules, create conversations.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
BI Expert at a non-tech company with 51-200 employees
Why I Love Tableau
I love Tableau because they took the time to design a solution that allows me, a plain old analyst, to produce reports that help management make sound decisions on business practices. Now let me define 'plain old analyst':
- Masters in Demography.
- Advanced statistical research
- Published in peer-reviewed journals
- Courses in SPSS (grad school), Excel, Access, VBA, SQL, and SSAS (in that order).
I am not a DBA or a Business Systems Analyst. I do not work in IT. And I'm not that old.
Disclaimer: This is not intended as a braggy or defensive rant; rather I hope that by understanding who the average Tableau analyst user is, you will understand our passion for this product.
I'm an analyst because I love using data to help Directors and Managers figure out solutions to their problems. As well as building standard department/program monitoring reports, I get requests for issues that crop up as often as humans interact. Human behaviour causes outcomes, intended and unintended. Here's some examples:
- "What is the accuracy of our Cardiac Wait-list Registry in this province? People could die if our data isn't perfect."
- "How close are we to the eradication of Measles with our Immunization campaigns?"
- "What is happening with babies born with Crystal Meth addiction? Are they all coming into government care?"
- "Why are Caesarean Deliveries on the rise? What is the resourcing cost?"
- "Do we need to hire more staff or should we shift services? What's up with overtime?"
- [ENTER YOUR RECENT FIRE HERE]
Tableau saves me so much time in the creation and management of regular reports, that I can deal with these urgent ad-hoc requests in record time. Or spend more time on those requests that we knew were important but were just to complex to do in Excel without a lot of time, VBA and effort. I'm not knocking Excel; she has been a valued friend over the years, but she's a bit of a mother-in-law (she's difficult, but you still love her).
Tableau was designed with my work in mind. It doesn't limit me. It exceeds my imagination. It makes me a kick-ass user. It makes me a better analyst. So much so, that I can't STFU about it.
Tableau users are often seen as fanatics - some are concerned that perhaps we've drunk too much of the Kool-Aid. Ted Cuzzillo of datadoodle has a fantastic post on his perspective of the Analyst Users (mostly Kool-Aid drunkards) and the BI Industry Analysts who attended the 2011 Tableau Conference in Las Vegas last fall. I tend to think of Ted's BI Industry Analysts as the folks on the left side of Stephen Few's BI Wall and plain old analysts like myself on the right.
Over the years, my experience with the Tech-centric folks has been varied. Usually, I'm met with general disregard or arrogance. There is an assumption by some of these folks that us plain old analysts just make pivot tables or the occasional pretty chart. They don't consider that we may be data savy (data quality, governance, security, process) or understand that we are actual business process and analysis experts.
I work hard at trying to form good relationships with these guys, which usually begins with me having to prove my mettle or give them something they need. I try to find my "guy". He's usually the guy on the left.
He's the friendly one, the most knowledgeable one with respect to the data I need, and the one who isn't threatened by other people's expertise because he's confident in his own.
Both sides of that wall have an important role and if we work together we can learn from each other and make great things happen. I've developed some great personal friendships with people on that side of the wall... it can happen.
At the conference, I didn't meet any of the "BI experts" that Ted describes, but I did meet many other analysts and without fail, they were all nuts about Tableau and the work they were now able to do. People passionately told me about their reports, new tricks they'd learned, and the cool dashboards they'd discovered through Tableau Public bloggers.
And then there was Christian Chabot's (Tableau's CEO) opening address. Imagine a Lynyrd Skynyrd concert, the crowd is shouting "Free Bird" and the original band members are all still alive. A little over the top? Ok, maybe. But we are passionate users. Because finally, after years of wrangling and blending data in Access (or SQL if we're lucky) and spending weeks building interactive dashboards with Excel and VBA - we finally have a tool built for us.
In a post at Information Management Ted paints a not too pretty future for the tech side of BI with the adoption of new user friendly technologies, wherein senior management may not foresee the potential dangers of "receding IT". He is optimistic though; while the pendulum may swing too far in the opposite direction, a rational readjustment will likely emerge.
Hopefully it's a future where the data is well managed and prepared, and Analysts on both sides of the BI wall work together building reports and sharing knowledge. It might be a little stormy at first, but it could be the perfect storm.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Nice write up, Kelly. LOVE seeing the passion for Tableau!
BI Expert with 51-200 employees
BIME vs. Tableau Comparison
1.1 General
This document compares two BI tool players in the Big Data arena – Tableau (http://www.tableausoftware.com/) and BIME (http://www.bimeanalytics.com/).
1.2 Comparison: BIME vs. Tableau
Parameter |
BIME |
Tableau |
Details |
Visualization |
8 |
9 |
Many types of graphs and visualization objects |
Ad-Hoc |
9 |
9 |
In both tools, a Semantic Layer pane allows for quick data exploration and manipulation |
Canned Reports |
8 |
8 |
Both tools support the ability to crete and consume pre-built reports with minimal time and effort |
Dashboarding |
9 |
9 |
Both tools have powerful built-incapabilities for authoring, publishing and administering dashboards on the web server |
Analytics |
8 |
8 |
calculation engine using a large function library |
License costs |
3 |
6 |
BM – Monthly subscription model
|
Cloud offering |
9 |
6 |
BM – SaaS-based solution by nature TL – 1. "Tableau Public": TL server hosted in Tableau; 2. Customer server in EC2 instead of on-premise |
Ease-of-use / intuitiveness |
8 |
9 |
Intuitive visual analysis, drag & drop, no SQL needed |
Ease-of-implementation & maintenance |
9 |
9 |
Very quick setup, semi-automatic semantic layer creation: data-types recognition, dimensions and measures definition, no code, no SQL required |
SDK/API |
6 |
7 |
TL – JavaScript API for web apps authoring BM – new API to allow 3 rd party integration and OEM |
Israel-based support & PS |
3 |
9 |
BM – Limited IL presence |
Financial stability, market presence and track-record |
5 |
8 |
BM – 15 employees, 1 st release 2 years ago, Angel-funded; Large installed-base |
1.1 Summary
Significant strengths of Tableau:
- Financial stability, market presence and track-record (both WW and in IL)
- Tableau's license costs are not cheap, but seem cheaper than BIME's in the long-term
- Israel presence – support and professional services
Significant strengths of BIME:
- Cloud offering – BIME is a SaaS product, thus cloud-enabled top to bottom.
- While Tableau does have some capabilities in this domain, it's not a true cloud solution.
Significant strengths of both:
Visualization, user capabilities (Ad-Hoc, Analytics, etc.) and Ease-of-implementation.
Significant weaknesses of both:
API capabilities are quite limited and immature.
Note:
- It seems like an issue both vendors are aware of and are working on in their roadmaps.
- It is not the most important feature, unless you plan an embedded/OEM solution.
Performance –
Both tools have a native connector to almost every Big Data platform available on the market. While this does not ensure good performance, it does improve the chances of getting better performance than other tools, which do not have such a connector.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Thanks, Ariel. If Visualman refers to visualization and visual analytics - I would agree with such a statement
Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2024
Popular Comparisons
Microsoft Power BI
Amazon QuickSight
Teradata
IBM Cognos
SAP Analytics Cloud
SAP BusinessObjects Business Intelligence Platform
Oracle OBIEE
Domo
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
I echo Kelly's comments as I have heard similar fears in the institutional research profession when discussing the democratization of data. I think Tableau Software triggers these issues deeply - visualization that taps innate human perceptiveness is powerful and promotes clear understanding of organizational performance and accountability (or lack thereof).