Tableau Reviews

We use Tableau for data analysis. We integrate 15 sources of data and then that data is brought into AWS. From the AWS, the data is uploaded onto a dedicated Tableau server where we have all our dashboards running. We then run code on the data to return results, such as the regression and causation.

The solution has great features which nobody can beat, you can do a lot of customizations, such as use different dimensions and colorize them. Additionally, you can use the numeric values for the customization, which is an exceptional feature.

There is a lack of visualization in Tableau which could be improved. For example, if you want to do a Sankey in Tableau, you have to do a lot of work to do it. Sankeys are available, they are for sale for a minimum of $400, which is out of the question. Whereas if I wanted to do a Sankey, it is simple for me to use a free visualization and put in the data, and from what I already have, receive a fancy Sankey.

Whenever it comes to specialized visualization, Tableau is an absolute failure.

The integration between Tableau and our statistics software or other software, such as Python is very loose and undefined. If they improve that it would be a benefit.

I have been using Tableau for approximately two years.

The solution is stable.

If I have web analytic data on session IDs, Tableau or Power BI both fail miserably in scalability because you are not able to go on a session-level and have 18 million rows fire up visually.

We have approximately 100 users using the solution.

The initial setup is simple.

We had a local team of two technicians that do the implementation and maintenance of the solution.

We are on an annual license which costs us $1,400 which is very expensive. Microsft BI is less expensive.

I have evaluated Microsoft BI.

The reason why we are not getting rid of Tableau is because of legacy reasons. Legacy, meaning it is being carried over and our organization does not have time and energy to transfer everything to Microsoft BI.

I will not give any credit to Tableau or Power BI for the very simple reason that everything is in the hands of the developer of how you visualize the data. There is not any magic in what Tableau is doing, the magic is from the developers who are creating the visualization. Any visualization tool which gives that capability sets you apart.

I would not use Tableau if I am working out of a financial organization because it is lacking fancy visualization. However, if I was a bank or a government organization where I am only looking at trend charts and bar charts I think Tableau comes out ahead of other solutions, such as Microsoft BI.

I rate Tableau a five out of ten.

Private Cloud

We use the most recent version. 

We use the solution to engage the field teams and we integrate that with the data warehouse data and build the dashboards for them.

It is helpful that the solution provides access to one's own data. It allows a person to get insights out of the data provided by his tool, based upon the KPIs that the person wishes to look at. It all depends upon different use cases. We have dashboards for marketing people, field teams and executives. It all depends upon which insights a person wants, in which case he can prep the data accordingly. This is good. 

The most valuable features are the visualizations, the way they show the combination charts. This allows a person to jointly put in different measures in different axes and greatly facilitates the user in understanding the data better.

There should be a focus on memory data, which is the concept of Tableau. This is where they squeeze the data into their memory. Because of that, we see performance issues on the dashboards. The architecture should be improved in such a way that the data can be better handled, like we see in the market tools, such as Domo, in which everything is cloud-based. We did a POC in which we compared Tableau with Domo and performance-wise the latter is much better.  

As such, the architecture should be improved to better handle the data.

We are seeing a shift from Tableau to Power BI, towards which most users are gravitating. This owes itself to the ease of use and their mindset of making use of Excel. Power BI offers greater ease of use. 

For the most part, when comparing all the BI tools, one sees that they work in the same format. But, if a single one must be chosen, one sees that his data can be integrated at a better place. Take real time data, for example. I know that they have the live connection, but, still, they can improve that data modeling space better.

We have been working with Tableau for almost seven years.

The solution has pretty good stability. It's a robust tool, even though it has a steep learning curve. But, still, I feel that from the stability perspective, it's a leading BI tool in the market. It's pretty stable.

I personally don't like any BI tool to have that scalability. What we usually do is integrate scalability into our warehouse layer. We know how to scale up and down and we handle it there. We don't rely much on the BI tools to do that.

I am talking about the scalability of a program in general, be it in its relation with users or as it concerns dashboards. 

We recently started working with Tableau online and that particular solution is scalable. It ingests the hardware, the server capacity by itself. So, if users go from, let's say... 100 to 500, we don't see a dip in performance. It still behaves the same. Because of this new integration technology with the cloud, they are scalable in that regard.

We are in contact with technical support. One service we have is Tableau online. If we see a dip in performance, we raise a ticket to the Tableau support team, work with them and make certain they address our issues. I would rate my experience with them as three out of five. 

We used Tableau from the get go. 

While I was not directly involved in the setup, I know that it's not that easy. There is a need for a proper administrator who has experience in that field.

We used an integrator from Tableau when implementing.

Our experience was good and we were assisted with our implementation requirements. They were able to make notes to match our use case and answer all of our questions, including those concerning the number of users we have and how to set up the server.

I'm not part of the administrative group which handles the setup. I am mostly a consumer and responsible for building the desktop. I use the desktop version to build the dashboards and am not responsible for the server health check or maintenance. As such, I am not in a position to provide information about the staff required for maintenance, updates and checkups. There are a couple of people who are responsible for this, one from the customer side and another from our team. Both parties are in sync when undertaking these activities. 

I have no knowledge concerning the licensing costs of Tableau. 

The solution is mostly deployed on-premises, although we have also done cloud-based deployment. 

We have around 500-plus users making use of the solution and mostly 90 percent are viewers. We have very few creators or explorers. Creators comprise seven percent and explorers three percent. 

My advice to others would vary depending on their use cases, what they're looking for and the level of competency they have within their organization to use it. Tableau has a steep learning curve. So, it depends upon one's use case, the reason the person is going with that specific BI tool. The procurement department would need to evaluate the use cases very carefully, because there are so many BI tools available in the market. One's focus should be more on a centralized tool when bringing a new one to his organization. It should address all the answers to one's users, like what they're looking for. Definitely Tableau is good in the data discovery part and it can handle large data sets. So, all of these things should matter when one is trying to evaluate a tool.

I rate Tableau as a seven out of ten. This is because we are using it and it has a steep learning curve. It's not user-friendly. One must build a competency in creating the visualization and then support it. All of these things matter when one is evaluating a tool. That's why a shift is going towards Power BI.

We use the product to build diverse dashboards for a revenue authority. It helps us analyze taxpayer behavior to understand payment patterns and identify areas for improvement in compliance.

The platform's most important feature is predictive analysis. We can map taxpayers' locations with data and connectivity to databases and sources. We can forecast future trends using the visualization feature. These are a few features that make it unique.

The product's features for cloud integration need improvement. They should revise licensing and pricing models to cater to smaller enterprises. Users must be able to customize and write their code similarly to one of its competitors. Many companies have in-house data science models for Twitter or Facebook based on predictive analysis. There is a possibility of integrating these models seamlessly into Tableau.

We have been using Tableau for a year and a half.

It is a very stable tool. I rate the stability a ten out of ten.

We have 10 Tableau users in our organization. We plan to increase software usage.

The technical support team is very supportive.

We also work with Power BI and an open-source solution. In comparison, Tableau has a sharp learning curve. It is intuitive and easy to use. It has less deployment time and impressive visualization features. We can connect different data sources, including SQL, Oracle, etc.

The initial setup process is easy. It takes less than an hour to complete. I rate the process a nine out of ten.

The product's price is relatively inexpensive and manageable for enterprise-level companies. However, they could reduce the cost or offer discounts for smaller companies.

I rate Tableau a nine out of ten. It is a stable and powerful tool compared to Microsoft BI.

I have used Tableau in the past with other clients for enterprise-level data visualization for financial and manufacturing industries. I have also used it for documents dashboard and different kinds of KPI visualizations. I'm currently using it for academic purposes. In my current organization, we are not using Tableau. We are using Power BI.

Tableau is very flexible and easy to learn. It has drag-and-drop function analytics, and its design is very good. It is a very good tool, and it basically brings life into data with good design. We have been creating a lot of interactive visualizations and dashboards.

It has a public version. There are public communities from where you can get a lot of examples for practice.

Its price should be improved. Its price is much higher than Power BI and QlikView.

Programming is not easy on Tableau. For programming, you have to have a separate model. They should include programming directly on the web portion of the Tableau desktop so that people can write Python or JavaScript code for customizations instead of using a different model. Currently, Tableau Data Prep is a separate application that you have to purchase. It would be helpful if they can include Tableau Data Prep and programming languages such as R, Python in the next version.

Tableau Public, which is a community version, doesn't allow you to save your work on your desktop. They should allow it. Currently, you can only upload it in the community.

I've been using Tableau for almost eight or nine years.

It is very stable. 

It is scalable. They have a cloud version, and you can implement it on the cloud.

Their technical support is good. Our own IT can also manage it, and I can also get support from Tableau.

We also use Dimension, Power BI, and QlikView. Domo is also there, but Domo is a little bit more expensive. Microstrategy is also a little bit more expensive, and it has different media storage.

Its installation is straightforward. It is a one-click installation. 

I installed it myself on my laptop.

Its price is higher than Power BI and QlikView. Tableau costs around $70 per user per month, whereas Power BI is around $8 to $9. QlikView is around $30. 

Tableau has various prices for various models such as Creator, Designer. 

I would recommend this solution if you do not have budget constraints. It is a very good solution with excellent visualizations. I plan to keep using it for academic purposes.

I would rate Tableau a nine out of ten.

On-premises

The primary use case is for household survey and population, and housing census analysis. I have also been using it for monitoring and evaluation of projects.

I provided Data Visualization skills to selected staff of The Gambia Bureau of Statistics (GBoS) in 2018 using Tableau. Previously, SPSS was used to analyze the data but after I introduced them to Tableau, the team was so happy that together we decided to look at the Census 2013 dataset and analyze it using Tableau.

I have also used it to develop a key indicator list based on the Living Standards Measurement Survey.

GBoS, with the help of the European Union, bought Tableau and have since been using it to analyze household surveys instead of SPSS or Stata, as they were doing before.

Another project that I am about to complete using Tableau is the Data Lifecycle Assessment of the Planting for Food and Jobs project in Ghana. I am working on this project with the Ministry of Monitoring and Evaluation and it is being sponsored by the Alliance for Green Revolution in Africa.

Already, the staff is so much in love with Tableau that they want me to provide Advanced Training for them so that they can adopt it as their Data Visualization Tool.

The most valuable features are the ability to classify variables into Dimensions and Measures, Ask Data, and Show Me.

The Dimensions and Measures feature solves one of the basic problems most would-be data analysts have, which is to determine which variables to analyze or focus on. Tableau makes this easy by splitting them into Dimensions and Measures and then use Dimensions to dissect or dice and slice the Measures.  

Ask Data enables non-technical personnel to quickly derive insights from data just by knowing which variables are available.

Show Me is a feature to help with knowing which chart is an appropriate one for the selected variables, and it makes helps in creating appropriate visuals.

I cannot end without mentioning the overall seamless flow of how to derive insights from data using Worksheets, Dashboards, and Stories.

I think predictive analytics is the main driver of business decisions and hence Tableau should strengthen the ability to make predictions.

The forecasting feature in Tableau in my view is too limited because it must have dates but I should be able to predict the outcome of an event without having a date as part of the input.

In situations where you are analyzing or using just one measure such as Sales, Tableau does not create the header for you. Furthermore, it is not straightforward as to how to create it.

I would like to have the ability to perform multiple pivots and creating different variables. For example, if I have the regional population for six regions and branch offices, together with the number of clients per branch, all as a record or observation, then I should be able to pivot them separately resulting in the Region, Population, Branch, and Clients.

I have been using Tableau for three years.

The scalability is simply awesome.

The technical support is awesome.

I have worked with Excel, SPSS, and Power BI.

Tableau is easy to use and the support from the community is awesome. Also, I see Tableau as a product for the future due to the commitment from the development team.

The Tableau Development Team listen to suggestions from the users and follow discussions on the community forum and factor that into product upgrades. 

End users want things to be done quickly and intuitively and the only way that any product will survive is by listening to end users 

The deployment was straightforward. I would say that it was a nice and easy, no-brainer setup.

The implementation was done in-house but there was an occasion that I had issues. I contacts support and it was super.

The ability to make insightful decisions quickly is a big benefit to all and therefore reduces cost in terms of manhours spent in cleaning and creating visuals.

It is a bit difficult for some people when they hear $70.00 per month, as some solutions are available for less than $10.00 or for free. What I always tell my trainees is that it is not so much about the cost, but rather, how you can quickly get the insights you have derived into the minds of your audience or stakeholders.

It is important to consider the ease of use. If a product is free but usability is a problem then it is not actually free because it cannot be even used.  

I had already used other tools and also wrote my own program in VBA to analyze data.

Customers need more insights and hence, they should look into Natural Language Processing (NLP). The ability to analyze text data or focus group discussions or radio phone-in programs would be helpful. 

When there is a major upgrade and you install it, it wipes off all of the recently used files and newbies get frustrated. If something can be done about it then that will be very helpful

On-premises

We use Tableau and Tableau Server for data visualization. We have a Global Tableau Server used by five thousand users on a monthly basis, with fifty thousand email notifications and more than five hundred workbooks for sales, marketing, revenue management, and operations analytics.

The solution has improved the organization by allowing quick access to data visualization and data exploration. Also, it helped to have a global server used as a repository to see all of the reports in the same place.

The features that stand out in this solution are:

• Scheduled extract and the multiple connectors are fantastic.
• Tableau Prep is fantastic.
• Tableau mobile on the tablet is also great for operations and the field users.
• "Ask Data" is good.

The performance could be better. At times, it can take up to one minute or more to open a workbook, which is very frustrating for the users.

Three to five years.

Stability is okay, although performance is slow on our side.

Our solution handles five thousand users per month.

Premium customer service and technical support are fantastic. Best in class!

We previously used Cognos and Power BI. We switched because with Tableau, you do not need IT support. Users can create their dashboard really quickly.

The initial setup was a bit complex, more so than expected. I would use a fully managed solution if I had the choice again.

Our in-house IT department implemented this solution.

The initial cost that is set according to CPU cores is expensive. You need to go with at least thirty-two CPU cores for five thousand or more users.

Before choosing this solution we evaluated Qlik, Domo, and Power BI.

The solution is very good. Loved it and the employees also love how quickly they can create a workbook and share it. Overall, a great solution and a great team.

We use it for different groups within the bank. They produce the visualizations they need based on their requirements. It's just rolling out. It's mostly for reports or visualizations - different financial applications. There are also HR applications as well.

For the groups that are advanced, they are pretty happy with the results, and the ones that are just starting the process, the journey, our group is ready to help. There are a lot of learning materials out there to get them trained and try different things out.

In the long run, things should be faster to deployment, to production, than they used to be before.

It's the speed of getting results, based on what the user actually requires. Before it was a very strict, follow the FDLC process. There was a lot of documenting and control that you had to follow before it went to production. We have decreased those a little bit so that they can move to production a lot more quickly than they used to. So time to market, or time to production is a lot faster than it used to be, because of self-service.

It's the ease of use, the quick deployment from developing it and then moving it on to our servers. It's much faster than our Cognos deployment.

It is also a self-service tool so it decreases the burden on having centralized IT-type teams or developers. It has now gone out to the different groups within the bank, and we just have to make sure that they follow certain governance rules so that they don't create crazy queries. It's easier for them. Hopefully, in the long run, they will get their visualization much more quickly. They are closer to the team members that are giving the requirements so they get feedback right away.

I think they have just come out with a tool called Prep, which we just heard about today. It was something that was missing, a little data preparation type of tool. I believe it is an ETL tool but it's not, as far as I know, a robust type tool.

The other thing is a data modeling tool, a little bit more advanced modeling. I would like to see functionality like Cognos has in the Framework Manager.

Less than one year.

We are somewhat new at it, so as more and more people onboard to the server, we'll see how that is being managed. Of course, if the performance is slow, we have to find out the reasons, the causes. If it has to do with how they are building certain things, we have to send that information back to them and then they have to correct their models.

We are in the early stages right now. I wouldn't consider ourselves in the middle or advanced stage yet. We're onboarding a number of customers now to our servers.

This is one of the things that we're going to have to address as people start onboarding. It's going to be the challenge, where we have to choose which BI tool to use. Thre is scalability in term of the number of users and in terms of the volume of data. We don't know the volumes of data that we're dealing with. If they're extracting data and putting it onto our server, that all will take up space. Those are things that we're going to discover over time.

Tableau is also improving its product. We're not using the latest version which has some performance improvements. That's because we don't have the hardware to support it. That is something that Tableau will, I'm sure, improve over time as well and catch up with some of the bigger players.

I haven't personally used support but when there is an issue, an internal ticket gets placed and if we can't resolve it ourselves, then we have a platform team. There is a member there who will submit it to Tableau. There have been a few of those.

The switch was driven by the end-user level. We discovered that people were actually getting the self-service tool without us really being aware of it. Once we found out that they were using it, we did some research and looked at the market, saw how popular this tool is and how easy it is to use compared to our existing tool. We said, "Okay, let's not fight the end-users. Let's help the end-users, let's adopt it and help them grow." 

That is how we've moved to this level where we've actually built out of a center practice. We're now a group, not so much of developers, but of people that will help the individual businesses build their own projects.

The most important criteria when selecting a vendor are support, for sure, and their ability to advance in the technology. We have found with Tableau that there is such a community out there. They have a lot of information that is freely available. Those are the main things, support and that they advance their products, that they don't get stale.

I wasn't the one that did the server setup. Definitely, on the desktop, it's very easy to use. And I suspect that the server is also fairly easy. It's pretty straightforward in terms of deploying projects onto the server and promoting it on to production. I haven't heard of any real hiccups yet.

In our case, people were already using Tableau. There are other groups within our company that are using other types of tools like MicroStrategy, and we already had BusinessObjects and Cognos here. But because of the ease of use and the self-service nature of the product we decided, for products in that category, that Tableau was the best.

My advice would be that you should consider Tableau. Certainly, for visualization-type projects, it would definitely be one of the products to look at, and I would recommend it at this time.

Because we are just starting the process, I would definitely give it an eight out of 10. We are getting a lot of good support from the groups using it, but that can only get better as we get more and more groups adopting it, and they are happy. It's really going to be a matter of how happy our users are in building their projects. As that grows, and if their feedback is good, then that will only increase the product's rating.

Tablo has a good community base and we're trying to recreate that community within the bank as well so that different groups of individuals can help each other. That's what we're promoting, and it's working. We have our own intranet site that people can go onto and ask questions and get answers. We also have training and all sorts of different information that's Tableau related.

We use it for internal monitoring purposes.

I like Tableau a lot as its visualizations are great; there's no doubt about it. It's easy to use. 

The look and feel and features are very good. Dashboarding is very good.

The product has been stable. 

While my experience has been mostly positive, there are certain limitations, as every tool has.

If I have to develop any, for example, pie charts, I can develop them just fine. However, if I have to develop a donut chart, that I cannot do it in a simple way. There are tricks that I need to use if I have to design a donut chart. It should be more flexible and provide more visualization options.

It does not provide detailed reporting like other reporting tools such as Microstrategy or Cognos, or other enterprise reporting solutions.

If they could provide better reporting as well as visualization, it would be a perfect product.

Pricing is a major thing. If someone has to use it within an organization, it is not that cost-effective, especially when a competitor like Power BI or some other reporting tool comes almost free along with their cloud solution. If someone is opting for any cloud solution, any cloud platform, especially if I talk about Microsoft, they will give you Power BI almost free of cost, or at a minimal cost. In such scenarios, people would prefer using Power BI or a similar kind of tool rather than using Tableau. That is a major concern which Tableau should look into.

I haven't been using it continuously, however, I started using Tableau around six years back. Since then, there have been two projects in which I worked on Tableau. I did work with it in 2021.

The stability has been good. there are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

I'm not managing any scaling aspects. I'm basically from the development team. Every company has its own scaling goals. In my company, I don't really follow that aspect.

I can't say how widely used it is in my organization. When we deploy a tool, there are different teams. There are different stakeholders who are actually using it. I manage my team. I know about only my team, not other teams.

I'm not part of that team that manages the setup. I cannot comment on that.

As far as ROI goes, I'm not directly aware of it, however, likely you can Google statistics. 

The pricing can't compete with Microsoft, for example, which basically gives their BI product away for free to those that purchase cloud products.

I'm also aware of solutions such as Microsoft BI, which is bundled into Microsoft Cloud products. It makes it less expensive for users if they are already heavily using Microsoft.

I'm a customer and an end-user.

I'd rate the solution at an eight out of ten. 

On-premises