What is our primary use case?
I work in the hospitality industry and I use Tableau Online and Tableau Bridge with our food ordering company. In our specific uses, I have found that Tableau is very good for extracting data, rather than for working live on the data.
Although the process of transferring data to Tableau isn't the best, once the data is already on Tableau, it works completely fine. I will typically make use of layer aggregation and other operations such as slicing and analyzing it by getting right inside the data in various ways.
How has it helped my organization?
Due to the demands of our industry, we always have things that we would like to see more in-depth over different dimensions, such as restaurants, branches, cities, and so on. With Tableau's help, our company can aggregate all the raw data and then analyze by rows, to see, for instance, which restaurant is doing the best by comparing them with one another. It also enables us to easily split areas into zones and use the data to test for not only which restaurants are doing the best, but also where (i.e. in which cities and branches).
What is most valuable?
Although Tableau isn't the best for us when it comes to processing and working on live data, it is very good at extracting data for analysis. Once you have extracted the data, the aggregate layers you can create, along with slicing and other operations, are very handy. It allows us to really get inside the data, and it is, in my opinion, better than any other tool I have used with the same pricing model.
Of the best analysis features, multi-aggregation layers come out on top for me, because they let you extract raw details while making multiple aggregations on different time levels and different dimensions, and you still manage to get your work done quickly without having to load a lot of data grouped over different dimensions.
Tableau Bridge is also a very good tool, however I can tell that it does need a few fixes and some maintenance. That said, it's still good for its first few years since release.
What needs improvement?
Most of the problems in Tableau Online that I have noticed have to do with performance or weird, inexplicable bugs that I can't pin down. For example, you might try unloading some data, and you'll be waiting for a long time without anything happening.
These bugs always seem to happen when we perform big upgrades or do maintenance work, and we have had to send a lot of tickets for unexplained issues during these times. It doesn't seem to be a problem only for us, but also for customers all over the world, such as in Ireland, Western Europe, Eastern Europe, and the US, too.
As for future features, I would like to see major upgrades in Bridge and the Flow Tool, allowing us to do more data engineering work. I think it would give Tableau a big edge in the market to look into how to incorporate more data engineering tools into their product.
Besides that, I would also like the charts to be more realistic and easier on the eyes.
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.
For how long have I used the solution?
I have been using Tableau Online for three years now.
What do I think about the stability of the solution?
The stability is okay. It's not 24/7, but you can say it's stable enough. In the start, it's more stable, especially compared to our OBIEE problems, which have taken two or three days to solve in the past.
What do I think about the scalability of the solution?
It's easy to contact Tableau and ask to increase users or resources. They'll do it in the blink of an eye.
At present, we have 20 users, 12 of which are shift users. The majority of our users in total are board members or high-level managers.
How are customer service and support?
I wouldn't give their support more than a seven out of ten rating.
Which solution did I use previously and why did I switch?
I have previously used Power BI, Qlik Sense, and Qlikview. I switched because Tableau was better in working with different sources compared to Power BI which was the only one that was truly on par. Qlik Sense and QlikView were easy to use but didn't have most of the features that Tableau and Power BI offered. Then there's OBIEE which I have used for the past two years, but it is quite difficult for non-technical users.
I also didn't like that Power BI is typically coupled with Microsoft Azure, whereas Tableau works well with AWS and Google which are a lot easier.
How was the initial setup?
The setup is straightforward. I mean, there's not much setup at all. It's easy for any mid-level user to do it. For example, I just used the documentation they provided and did everything myself. The documentation was sufficient
and the implementation strategy doesn't take more than 20 days.
What about the implementation team?
I implemented Tableau by myself using the documentation they have made available. And for maintenance on one single node, you might need only two to three people involved.
What's my experience with pricing, setup cost, and licensing?
For data extraction and analysis, Tableau is better than any other tool I have used with the same pricing model.
What other advice do I have?
My ultimate advice is that you should know what the tool is capable of first and what your needs are. I think it's better to use the Server edition, and not Cloud, because there are a lot of problems in the Cloud version that don't seem to be present in the Server version. As for myself, I will likely switch to Tableau Server next year after doing a bit more research on how to do the changeover.
I would rate Tableau an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: I am a real user, and this review is based on my own experience and opinions.
It is decent. Comparatively other BI Tools. May be it is Quick Build & Maps leading to Topper in BI Space.