Tableau Enterprise Reviews

In my consulting firm, I use Tableau for data visualization and data analysis. Alongside Tableau, I also use Python and, on occasion, SPSS.

The EU had recommended Tableau for use in some of the statistics offices in Africa, including government institutes in Ghana, and just last week I was using it to do a program for the Ministry of Monitoring and Evaluation. There, I used Tableau to convey selling points to buy Tableau, which is one example of the consulting work I do for clients. 

I also train others in visual analysis with the use of Tableau. This September, I trained 265 medical statisticians. Last week, I trained 13 staff from the Ministry of Monitoring and Evaluation. And soon, I'll be training another group of 20 people on Tableau.

Tableau is a good product for people like me who provide data analysis training because it makes my job far easier. It's a good product and very easy to use, making the introduction of key technologies extremely simple.

For instance, when you get data, and go in to analyze it, people ask, "This is numeric?" People start thinking about, "How do I get all these tools?" Tableau takes the data and automatically breaks it down into two dimensions and measures. That makes it easy for me when I'm doing training.

So what I would say to trainees is, "Don't worry about all these data types, when you are designing your questionnaire, because in Tableau it breaks them into two. And the measures are the ones that you are going to actually work on. You normally break them down by the dimensions." And that makes it simple for people to understand. Otherwise people don't know where to start when it comes to data analytics.

Tableau makes life very easy for not only myself but also for others, because you can quickly get into data analytics and visualization with it.

Tableau is easy to use. That's the first and most important thing. I not only provide consulting but I also train people to use it, so with its ease-of-use it's not as difficult for me to train executives and management staff, because they don't have the IT background, unlike when I'm using Python. They don't know anything about programming, so Python is more difficult.

Tableau is also, right from the outset, a self-service product. It's easy for anyone to understand and use. Some of the organizations that I introduce to Tableau are using the full-blown version, i.e. the commercial version, and they can very quickly start analyzing data with the use of the Ask Data feature, where you can simply drag and drop while querying for data with natural language processing. You type in English and it will pick the data and analyze it for you.

Those features are built into Tableau which makes getting started with data analysis very easy. And it's also got some pretty good built-in visualization tools. I would say Tableau is one of the best when it comes to self-service functionality.

I attended a Tableau conference recently, and a quick improvement came to mind. When I am training people how to use it, I've come across situations where I've found it difficult to explain relationships. For example, when you want to blend data or when you want to show relationships, like when linking multiple tables; well, if you're an IT guy, that's easy. But if you are not an IT guy, you don't know anything about entity relationships, and it becomes a bit difficult for others to follow along.

It takes me a long time to get people to understand, even up to the point where I feel that this is the lowest level that I can go in terms of explaining it. I realized that many people don't really have any experience or knowledge about relationships between objects, and it makes it hard for me to get my teaching across. 

So I was suspecting, and I think I made this recommendation, that Tableau could find an easier way to introduce relationships. For now, if you want to build relationships in Tableau, or even in Excel, you have things like Access modules and Sheets. But how do I know that I need to use one object with another for the relationship. And if you then put in a table, what do you do after that? You have to double click, but people don't know that you have to double click.

I was hoping that there's a way that they can make that process a bit easier, though I don't know how they will do it. Perhaps when you load Tableau and connect to a data source, there would be a prompt that asks you if you want to link two tables together. So if you want to link two tables together, maybe you do A, B, C, D.

That might help with the self-service idea. If you're talking about self-service, then it should be easy for people who do not have the time, or who do not have that IT background, to pick the data and use it correctly.

In addition, and more generally, what I would like to see more support for is predictive analytics. When you're doing descriptive analysis, Tableau is excellent, and it's easy to do. But when you are trying to predict something, like in Tableau's forecasting feature, it seems to require date fields, or it won't work.

But I can forecast something without relying on date fields; maybe I want to predict that a branch has to close if it doesn't want to make something soon. I don't need dates to do that. For this reason, I'm using Alteryx for predictive modeling instead of Tableau.

Overall, the only major frustration that I have had so far is with Tableau Public. I first used Tableau Public when I was building capacity, and when there was a later release to download and you wanted to upgrade, all your work would have to be manually re-entered. I don't know how they can solve that. I was expecting that they might make a release on this upgrade, and then I can hit upgrade and it will install over what ever I have already.

Otherwise, for now I think they are doing well and I know they're still adding a lot of features. But it does sometimes make our work difficult, for those of us who are building capacity, and who are regularly changing people around. It means you have to keep learning all the time.

Another small detail for improvement is that when you draw bar charts, the default color could be something more neutral like gray. Instead, the default is blue, and I don't exactly get why this is the case.

I've been using Tableau for the past three years now.

I contacted support when I had a problem with data entry in 2018 or 2019. I spoke to a man based in Ireland and he was super.

I had originally put the problem I had on the Tableau community support forum, but I didn't get the right answer. I've forgotten the exact problem but it involved connecting to a data set from an Excel file. Instead of the data field displaying the data for you, what I got instead was an error or no response.

It kept happening like that so I sent a message to support, who gave me some steps to follow. I followed them but it still did not work. However, I realized that any time I do it and it shows up and I click data,  it then suddenly goes off. I'm still wondering why that happened. I think it depends on the size of the file or some other reason. I have not tried it again because I'm a bit busy now but it's something that I want to go back to because support didn't give me a satisfactory answer.

They told me, "Do this." I said, "I tried it. It did not work." They asked me again to do something and I tried it, and it still did not work. But then I tried on my own, and this time when the problem came up I clicked the data interface twice to reload it. On the second time I clicked, it worked, but I don't think that is the right way to handle it. 

I used Power BI before discovering Tableau in 2016/2017.

At first I did not like Tableau, because Tableau initially put me off considering that I have a problem with how Françafrique countries, like in West Africa, are controlled by France to not buy anything from Anglophone countries. I've worked in 15 African countries. And for instance, in Ghana, we are bordered by Françafrique countries but they haven't bought things from here because France tells them, "Don't buy." Which to me is wrong. Why should you sit in Paris and dictate to Africans?

I also decided that, "Okay. I'm not going to go into any French country and work." So, for my consultancy, apart from mainly Côte d'Ivoire, I also said, "Look. It is the attitude towards Anglophone and West African countries, I'm not going to help anybody." Because my contract with the World Bank was to build capacity. So I decided I'm not going to go there.

So, when I saw Tableau first, the word itself made me think that this might be the same kind of product, and I would not even look at it, because I was against it.

I kept on using my Power BI until a colleague, another consultant who we met from South
Africa, said to me while I was demonstrating Power BI, "I think you can use Tableau." I said, "What is Tableau? I don't want it." He said, "Oh I don't know much about Tableau, but somebody told me it's easier to use than Power BI." He said, "Why don't you look at that?"

We were working on the same project and I told him, "No, I'm not interested, I will not
look at it. It's a strange product, I don't want to look at a different product." And the guy insisted, "Oh please, you must take a look at it." Because we were looking at the project like we're a team, I said, "Okay, I'll look at it."

So that evening I downloaded it and I realized that all the things that I'm doing in Power
BI, that requires some level of IT background, well, I don't need that in Tableau. So then I decided, okay, let me really look at it. Who is behind Tableau? I asked where is the name Tableau from? Where did you get that name from? Okay.

So that was the time I changed my mind towards Tableau, and to be honest with you I've not regretted anything for doing it. I'm quite happy about it.

Setup is not that difficult for me. However, I remember in Gambia, there was some initial difficulty when I was teaching how to set up the organigram for the National Social Staff System.

In the National Social Staff System, you have about 11 ministries involved and the coordinator, and it's the coordinating agencies in Bureau of Statistics. So I needed to set up the system so that all the other ministries can enter their data. And when you enter the data, the other ministry, let's say, Ministry A can also enter data. And Ministry B cannot see what Ministry A is doing.

Now, when I was doing it, it was not difficult at all, but because I had to handle other systems and leave, I tried to explain it to them but they found it a bit hard to grasp.

So where you have multiple alliances and you set them up like organizations, it can get a bit complex. Because there's differences within the same organization under different departments. It's not a big problem when you buy Tableau for one single organization, but when you set things up for multiple organizations like the National Social Staff System, it can get problematic.

The national system is made up of different entities: Ministry of Health, Ministry of Agriculture, Ministry of Finance, etc. They are different ministries and they don't necessarily need access to all of each other's data. But if you buy Tableau for each of them then that is fine but if it comes to a situation where they all come under one number and you're setting up, you don't want one ministry to see what the other is entering.

So there was definitely a bit of a problem there. But I can't blame Tableau because no matter what it is, sometimes you need a certain level of IT skills to get certain things done. 

At $70 per month, I think the price is a bit scary. I have a small consulting firm in Ghana, working in about 15 different African countries, and when it comes to our part of the world, $70 a month is a lot of money for software.

In fact, where Tableau was approved for use in Gambia, I had the EU pay for three years. But I know it's expiring soon, and I don't think they will have the money to renew. I don't know how they're going to do it. When you come to Africa, especially when you're on the net, we don't use it so much, so I don't know if there is something that they can do about pricing for people in the African continent.

Yet recently, I trained 265 medical statisticians on how to visualize their data, using Tableau Public. They were so happy. And they thought, "Oh, this is very easy for us to do." But when they asked me about the price and I told them, they said, "$70? But we can't pay."

So that for me is a problem here. And, mostly, it's a problem for everybody. There are some companies that can easily afford it, but the majority of companies cannot.

I have occasionally used IBM SPSS for similar work that I perform in Tableau, but I only use it when the client absolutely requires it.

I wouldn't tell people to go with Tableau just because it's the tool that I use. I would instead emphasize its remarkable ease-of-use and the way Tableau really listens to their users and comes up with frequent upgrades. 

I would rate Tableau a nine out of ten. 

There are many and various use cases. Some use it internally for inter-department analytics, sales analytics, campaign management, and sentiment analysis.

The most valuable feature is the richness of its visualization and from a self-service standpoint, the ease of use.

The interface is fine. The functionality in the UI front is good as well.

It integrates easily.

From a UI visualization standpoint, I think it's pretty robust.

The data processing in Tableau is pathetic compared to Qlik.

In Qlik, I can replace my ELD layer for an application. This can't be done in Tableau.

The initial processing of data in Tableau takes a lot of effort.

If there could be a feature that a particular visual can be exported or just the data behind the particular visual can be exported in one single click, just one button on a visual and it exports the relevant data out to Excel or a CSV output, that would be good.

I have been using Tableau since 2014, maybe even before that.

It's pretty stable.

It's decently scalable. I have been able to scale it pretty easily.

Technical support is good. On a scale of five, I would say four.

The initial setup is neither straightforward nor complex.

Pricing is not bad. It's competitive.

I'm a BI Architect.

My recommendation for this solution would depend on the use cases.

I would rate Tableau and eight out of ten.

We have been using Tableau for all sorts of analytical tasks. When I was having an ERP SAP practice, we used SAP analytical tools and IBM Cognos plus Tableau for dynamic display session purposes. Tableau ended up being the best solution. That is why we moved over to Tableau. We predominantly implement and use Tableau. 

It's a pure data platform. Everyone relies on Tableau. Our departmental meetings and reports for monthly meetings and reviews happen live on Tableau. We can prepare all of our KPIs on it. In fact, all of our KPIs can be placed onto one single screen and divided into nine tiles that can be further divided.

We can easily review and define all of our KPIs. The data is perfectly validated. It allows us to run corporate and board presentations purely on Tableau's visualization center.

It's an extremely good product with respect to performance and analytics. 

All the transactions that are happening are happening in SAP and some of the solutions are in Oracle as well. The combination, the data extraction which is filtered into authenticated, validated financial data, sales data, material data, etc, into Tableau platform is very useful for us.   

The solution makes for very productive and really informative decision making. It can lead the whole business and build a strategy across whole working departments.

The licensing costs of Tableau are on the higher side and probably if you wanted more adaptability in usage across business divisions you need to have more reasonable pricing of licenses of Tableau. Tableau is a standalone product. That is a disadvantage.

Due to the fact that it is a standalone product, it has to extract the data from other ERP systems or other bespoke systems and other data systems, etc. If you have big data systems and you have got other informed decision-making tools and the data is being extracted into Tableau it is dependent on many other platforms.

In contrast, if you use SAP vertical data systems and you have SAP's Data Hub, etc., then everything is vertically integrated. The whole data pipeline is vertically integrated and there is a visualization screen right there as well. Therefore, you don't normally have to go for a separate integration process altogether or need a data extraction solution.

In the end, Tableau has got two or three disadvantages in the sense that it is not a seamlessly integrated platform, end-to-end platform. It's purely a standalone reporting tool. On top of that, the licensing cost is extremely on the higher side. Thirdly, IT divisions probably are a little bit hesitant to use Tableau due to the fact that separate training is required, and separate skill sets are needed to develop everything. 

The cost of owning the solutions from Tableau is much higher compared to any other analytical solutions.

We've used Tableau for the past two and a half years or so.

Technical support is okay. It depends on the countries. I was in Australia for some time and there the support is much better than in India. This is probably due to the fact that a number of users are struggling with it and you get delayed support here. It's better to use Tableau proactively and develop a center of excellence in our organization. That is what I did and it helped us out a lot. I don't have any complaints about technical support per se.

Tableau is undisputedly the number one analytical product in the world. I have given a long presentation to management and the CEO about what differentiates Tableau over other products such as Cognos and Hyperion, SAP, etc. Lumira also is a strong contender, however, Tableau is way ahead because of the dynamic reporting that is possible and the whole virtualization that is very easy to produce, or reproduce. The business users themselves enjoy working on Tableau much better than other solutions like SAP, Cognos, Hyperion, etc.

The pricing of the solution is a bit high.

We're only customers. We don't have a business relationship with the company.

We have not moved to the cloud so far with this product. Only SAP Ariba is on the cloud. The rest of our solutions, all analytical solutions, are on-premise solutions only.

Businesses should know what exactly they can do with Tableau. It's not just a visualization center or dashboard. You can contact a lot of assets that are in use - such as institutional analytics, predictive analytics, and prescriptive analytics. It can integrate with any artificial intelligence learning solutions and analytic solutions. That is where big data analytics play an important role. Modern business is more focused on all sorts of big database analytical solutions, especially for retail and other larger CRM business.

A company needs to decide answers to questions such as "how do you extract data?" or "Which department wants what data?". They would definitely need to have an initial, extremely focused approach of implementing it, with the full participation of the business teams. That is how a successful Tableau implementation needs to happen. However, it doesn't end there. You also need to educate business users or corporates on the solution as well.

Tableau is an extremely good product. I'd advise other users to use all aspects of and take advantage of its capabilities. Tableau has many licensing products available and a whole analytical model should be under one platform rather than going for bits and pieces from Oracle, IBM, SAP, Microsoft, etc.  Tableau is undisputedly the leader of the whole analytical solution and it should remain so only because it should have a larger use phase.

The training of Tableau is good, however, users should be aware that the consultants' availability across various countries is limited. I'm from Bangalore and if I need a Tableau consultant it's very difficult to locate one. You can, however, often find freelancing consultants. They can also get the job done.

Overall, I'd rate the solution seven out of ten.

There are so many solutions on the market. Primavera solution is a project management software. There is no product that can beat Primavera in the project management functions so you have many such project management products, SAP Project Manager, Product and Portfolio management is there, Microsoft Project is there. There are other Oracle project management solutions out there and then Primavera is there. 

When Oracle purchased this solution, the popularity of Primavera died out. I've personally stopped recommending that particular product. There are others that cost less, so why use that one?

Tableau should learn from Primavera, and ensure it builds its user base and market its abilities so that corporates understand the depth and breadth of its usage. Many only use 10-20% of its capabilities. It's the duty of Tableau to ensure potential use cases are advertised and more information is disseminated to corporates to help them understand how it can benefit them and why that should adopt it.

We primarily use the solution for HR and energy dashboards. We have made and a few other dashboards for opportunities and accounts. 

Tableau has really good and interactive visualization and interactivity. 

The action feature which Tableau has is very useful for us. If we click on one visualization, it will pass the value to another visualization. That interactivity within different visualizations is the most valuable feature of Tableau.

Tableau would be really good if we could have predefined templates. I was doing a POC another newer tool, Einstein Analytics. They have predefined templates already set up. These predefined templates do the heavy lifting for the initial dashboards. We don't have to build them from scratch. Our dashboards look really good and 20 to 30% of the look and feel of the dashboard completes with the predefined templates. If Tableau works on the predefined templates, that would be so helpful to a lot of companies. It would save time for the developers.

The pricing is a bit higher than the competition. They'll need to lower it to stay competitive.

They need to move more into machine learning AI. Right now, in a POC that I'm doing with Einstein Analytics, they are more into machine learning and AI. Tableau is lagging as of now. If they want to have a long run in the market, they need to integrate machine learning and AI. It has to be very robust.

I've been using the solution for two years now.

I can say that this solution is quite scalable. I'd rate it eight out of ten. It integrates with many solutions. I haven't used our code in everything, however, I have used it for our HR integration and I find the code is quite scalable. 

In the last project I managed, there were 110 regular users of the solution with about 20 suer-users that were able to edit reports and dashboards and tasks of that nature.

I'd give technical support a nine out of ten. There were time zone differences. However, I got a timely reply and call from them, so it was very good. The support is very good. It's both responsive and helpful. I'm quite satisfied with them.

I've used BusinessObjects and MicroStrategy as well. I used to use Power BI for a few months.

The main competitor to this product is Power BI, which I also use. This license is a bit costly compared to Power BI. Not more, but a bit costly from what I've seen.

There's not much of a difference between Power BI and Tableau. They have the same kind of interface and the features. The main difference between the BusinessObjects and the others is that its an enterprise tool. The licensing cost of the BusinessObjects is very, very expensive. The visualizations and objects etc., all have separate licensing for dashboarding. On top of that, the chart's not that interactive. If you click on one chart, it will automatically change the data of the several other charts related to that. That is not very interactive compared to Tableau or Power BI.

The initial setup was not exactly straightforward. It was complex, or, to be fair, had a medium amount of complexity to it. The use cases were complex also and few of them had medium complexity to begin with.

Deployment was basically in the development environment and then we deployed it in the UAT for the users. They had a look at our reports in UAT first and then we deployed it into production. I was also working as a Tableau administrator also and then I learned Tableau administration in order to handle that aspect. I handled Tableau administration with the user and deployed the reports, etc.

The company has different verticals basically. I worked on HR and energy verticals. They also had finance and accounts. I have to maintain that administration part for all of them; not just my dashboards. From a deployment perspective, it was tough for me to maintain all the users and all the rules for the accounts department and for finance, and to be in the group for them, and to assign permissions for them. I did have issues in the servers in terms of gateways. I resolved them myself in the end with the help of Tableau support. 

I handled the implementation myself. I didn't need the assistance of a reseller or consultant.

The company chose to purchase a creator license for me, which was $70. With that license, you can also be an administrator. We also have 20-25 extra licenses and they cost around $20-$35 each. Those are for normal users who will be viewing the dashboards. Those are monthly charges.

There aren't any other costs over and above that.

Apart from that we had database licensing. So because we used Snowflake as a cloud database.

Our company has a partnership with Tableau.

I've used both on-premises and cloud, depending on the requirements.

This particular solution is quite an easy to use product. It's very robust. Even a layman who has previously was not worked with any other BI tools would love to work on this. They will find many things easier to implement. There are a few other tools that are in the market. However, from an implementation point of view, it's very robust. 

I'd rate the solution nine out of ten overall.

We use Tableau for BI reporting.

The most valuable feature is the interface, which is user-friendly and intuitive. Even for somebody new, who has no idea of how a BI tool is supposed to function from a technical standpoint, it is very intuitive. You simply import the data and then use the drag-and-drop capabilities.

Data cleansing and data transformation functionality need to be improved. Tableau is not a full-stack BI tool, like Sisense. Including this type of functionality would add flavor to the tool.

The main point is that Tableau requires the data to be in a certain format for the end-user, in order for them to create charts. If it's not in a certain format, or in a certain structure, then the user will have to manipulate it.

The charts in Tableau are quite limited.

I have been using Tableau for a few years.

Tableau caters to a lot of databases and flat files, which means that you can connect to multiple data sources. In this regard, I would say that it is quite scalable.

We have between 40 and 50 users in the company.

We are quite satisfied with community support. It is always there if you need any help and I am pretty happy with it.

I have worked with other BI tools including Spotfire and Power BI. There are not as visually appealing as Tableau and I would stay that purely from the UI perspective, Tableau definitely has the upper hand.

Conversely, Power BI has some capabilities that are missing in Tableau. Examples of this are charts and graphs. If you want to create something that's customizable, it's a very difficult and tedious task in Tableau. This is unlike Power BI or Sisense. 

The initial setup is very easy. Once you download it, it is a typical setup with a series of screens where you just press the Next button. Anybody can install it in a few minutes.

I am currently researching Sisense to get an idea of what the pros and cons of the different BI tools are. Sisense is a more complete tool that includes data cleaning, data transformation, and ETL capabilities right in the tool.

Tableau, on the other hand, is used for visualizations, dashboards, and storytelling. Their data has been cleaned or preprocessed in an SQL database beforehand.

Tableau is a product that I recommend.

I would rate this solution an eight out of ten.

The product’s performance is better than other tools. The working speed is good. Creating visualization on Tableau is somewhat easier than other tools.

The product has some limitations. Creating empty extracts is not easy. We faced some issues in the initial phase. Creating extracts side by side with multiple lines is not possible in Tableau. This feature is available in Power BI.

If we want to make any changes to the server, we must have the Administrator role. The product should also allow users with Explorer roles to make these changes.

I have been using the solution for the past three and a half years.

The tool is stable.

The tool is scalable. Around 50 people are using the product in our organization. Everyone knows about the product. We have around seven administrators. The number of administrators varies based on the project and tasks.

The technical support is good. I raise a ticket in Tableau Community if I get stuck at any point. I can get the solution easily from the community.

Positive

I am also using QuickSight. When we create multiple visualizations and multiple sections using Tableau’s dashboard, the way of executing the visualization is quicker in Tableau compared to other tools. We can pull millions of data and create millions of tables. Apart from the performance issue, compared to other tools, the product provides the best and most advanced features.

The initial setup is easy. The time taken for deployment depends upon the data, the visualization, the types of reports, and the number of cards.

We are also learning to use other tools. It is beneficial to learn Tableau. It will help us in the future. Overall, I rate the solution a ten out of ten.

I use Tableau in a jewelry company to analyze sales and service inventory.

I can't comment on the valuable features of Tableau. I am familiar with some of the other tools, but I can't point out one specific big feature of Tableau.

A specific thing in Tableau is that I have looked at how to add pictures to the reports. I don't have the ability in Tableau to create a tooltip and see the picture of a piece of jewelry or watch that is a best seller.

I have been using Tableau for over five years. I don't remember the version of the solution I am using, but I feel it is the upgraded version. Maybe the server is not the latest one, which might be behind by a year. I am a customer of the solution.

Tableau does break down a little bit. The server version of Tableau doesn't allow you to see what is going on, making it a part of Tableau that is not great. Tableau's server version doesn't provide the ability to extract the information to see why the reports or dashboard didn't run properly. When you refresh in Tableau, you can't see what it's doing, and nothing happens since it doesn't show you what's going on, and then Tableau gets fixed all of a sudden.

One of my biggest problems is getting all the users to use Tableau, but that's not a specific problem of the tool alone since it is one of the most common problems among BI tools.

I only have ten Tableau licenses that are used in my company.

I have only sought some local support within Israel for Tableau. The only way to solve the problems in Tableau is through checking on forums.

Tableau is deployed on-premises.

Tableau's initial setup was straightforward. When you need to make complicated dashboards, that can be very difficult in Tableau, but the initial setup was very quick. Connecting the data sources was very easy in Tableau.

The pricing for Tableau is the same as the other products in the market. I haven't checked Tableau's price recently, but I don't think it is a factor when choosing the tool.

Before choosing Tableau, I had checked QlikView, which is now Qlik Sense, and I preferred the way Tableau works over Qlik Sense. Tableau made me feel independent and not dependent on programmers, making it more user-friendly.

I would look at Microsoft Power BI. I am unsure if I would push Tableau since it is not a widely used tool. I don't know if others in the field of jewelry use Tableau.

Overall, I rate the solution between a seven and eight out of ten.