Tableau Reviews

It has ease-of-use features that make it a good data discovery tool for use with our clients. Additionally, the ability to rapidly mine data and visualize data issues for clients is valuable.

We can use this tool with our internal data as well as on client sites to rapidly evaluate data sets and gain understanding of patterns rapidly.

The integration of multiple data sources has sometimes been difficult and the size limitations are sometimes an issue.

We have been evaluating this product for approximately six months now.

No issues encountered.

No issues encountered.

We are very early in our project but do not see any major limits yet.

Customer service has been excellent.

Technical support is very good.

No previous solution was in place.

The connections to the SQL data and flat files were straightforward.

Implementation was all done in-house.

Unknown at this time.

• Tableau
• PowerPivot/PowerBI
• Birst
• Sisense

1. Understand your business hierarchies intimately.

2. Create flattened data files for roll-ups.

3. Be prepared to clean and process data prior to use.

1. Data Blending - the ability to blend data from multiple data sources to create the report that is needed.

2. Quick and meaningful visualizations - Tableau's drag and drop features provide on the fly reports that often don't take more than a minute to create.

3. Tableau Server Subscriptions - Gives end users the ability to quickly subscribe to a dashboard.

4. Awesome support! - The Tableau help-desk and server support teams are out of this world. Have a question, shoot them an email and get a response quickly. They also have a phenomonal website (tableausoftware.com) with traning videos, a knowldge base, and plently of Tableau experts to help work through calculations and dashboard building.

We no longer need to rely on certified report creators to create reports and dashboards. Just connect to data and start building. Plently of free training availble online at tableausoftware.com for first-time users. Allows for independancy from IT.

The tool is not perfect, but with each release issues are getting resolved and performance is getting better. There is an awesome "Ideas" page on their website that allows users to submit ideas for improvement and vote on ideas that they would like to see added into any of the Tableau products. Tableau does a great job of moving these ideas from conception to reality.

3 years

No

No

No

Outstanding!

Outstanding!

Our company used Cognos Planner and a few other BI solutions before. Tableau is less expensive and easier to use. An easy choice to make the switch.

Pretty straightforward. Tableau gives great instructions. My only complaint is that they make assumptions on how your company handles security ceritifcates when using SAML. It took us some time to work though SAML configuration, but once we passed this hurdle, everything else was easy to put in place.

The intial server setup was done with an in-house team. When we expended our environment, we brought a vendor in to make sure we were implementing everything occurding to our business needs. The vendor, recommmended by Tableau, was professional and we were able to get the job done quickly.

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.

We use the solution for the dashboard and visualization. We are a consultant company with 20 employees.

The solution is deployed on-prem. I am using the latest version.

I like the visualization component. 

The development part should be better. We are putting a lot of effort in during development, so if we face any struggles, we have to find workaround solutions on the internet. It would be nice to have new workaround solutions and other options. Every customer has different expectations, so sometimes it's hard to find the right solution.

I have been using Tableau for 15 years.

It is stable.

The solution is scalable.

The setup is straightforward. It took about a week to install. For deployment and maintenance, we used two team leads.

This license is on a yearly basis.

I would rate this solution 9 out of 10.

I had a case in the dairy industry, and they had about 200 sales agents on the field. They needed some daily reports as well as some dashboards with the standard presentation of their goals and targets. So we prepared some dashboards and Kafka presentations of data collected daily and presented them to the field sales team. We drafted up some information for them about how to proceed with their daily targets. Tableau could visualize the salespeople's progress toward the targets. For example, it can use different colors to signify if the sales team is over or under its target. They can use this graphic to find what they need in their final reports. So if they are under a monthly benchmark, they can break down the graphic presentation, do final reports on a daily level, and find information on each day in the month.

Tableau's visualization features let you present information insights quickly and practically. So it's something which I prefer with Tableau. In terms of reporting, I have to point out the sheer quality and function of the Tableau server, but the first impression is that it's a great visualization tool.

If you mainly need a tool for BI reporting, it's not the best option. Tableau needs better abilities to generate simple reports, integrate, create databases, and work with data lakes. 

I can't recall ever having an issue with Tableau's stability. And also, I'm not sure how often our clients have had to update software or install patches, but I think it's pretty stable. I would consider it moderately to highly stable.

We've used local technical consultants and support in Serbia, so it was pretty good. I can't remember having any problem solving issues during the implementation. And later, during the exportation of this tool, support solved all our issues and incidents in a reasonable time.

Tableau also has a broad user community that's helpful and powerful. When you're using Tableau, you get a knowledge base with a lot of interesting and valuable information. So it's not hard to find some solution that's already prepared for simple presentations, like templates for visualizing reports in a novel way. 

I've used two editions of Tableau. The free edition was very easy to use and set up. The enterprise requires a desktop and the Tableau server, and it's not too complicated. However, it's necessary to have experience and some documentation. So setting up the enterprise version isn't easy for someone who has no experience, but it isn't too complicated overall, either. We had the support of a local company here in Serbia who rebuilt it. They are consultants who specialize in Tableau databases and everything necessary to implement this tool. So I can't remember any problems with the setup. It was relatively easy. They also had to set up the desktops, the Tableau server, and a couple of professional licenses to prepare basic reporting and visualization segments. Lastly, they just have to set up the end-user with everything they need to read the reports and see presentation and visualization.

Tableau's prices are relatively high for our market. I am from Serbia, so many companies in this market don't have the ability to pay for expensive software. My clients are quite satisfied with a lot of Tableau's qualities except for the prices.

I rate Tableau eight out of 10. I would recommend it for companies that have a specific need for a solution with strong visualization capabilities. 

We use this solution to create dashboards, analyze data and create presentation of data to have discussions with clients. We also use it to sort huge amounts of data. 

The solution is very user friendly, particularly in terms of the ease of analyzing data.

Tableau would be difficult to implement without training or the in-house technical support we have.

I've been using this solution for three years. 

The stability is very good, especially now that they've joined with Salesforce.

We have support from within the company. 

The initial setup is straightforward because the solution is already set up in the company. It was just a matter of requesting it and downloading.

We have a global package but I'm not involved in licensing and don't know the cost.

I had a look at Qlik but didn't get a chance to really evaluate the benefits from one platform to another, other than what you find on the internet. 

I rate the solution nine out of 10, there's always room for improvement. 

It was for dashboards. The key use case was for creating visibility to performance metrics for the leadership team. It was the most recent version, and it was deployed on-prem. 

The key use case that we were going after very specifically created visibility to performance metrics for the leadership team. So, it allowed us to give that common view of performance metrics and drive business conversations based on the common shared set of facts. We were able to expose data and relationships that we otherwise couldn't do in our enterprise system silos. From that perspective, we were incredibly successful in really driving performance. When you combine that with some real championing in the business and with some leadership to push it down, the fact that it was Tableau wasn't as relevant as the fact that we had the championing pushing the process and pushing it down.

The number one thing was just the ease of getting something up quickly. The other thing that was good about it was that it was fairly fast for decent-sized data sets in terms of performance and run time.

From a downside perspective, some of the more advanced modeling techniques are actually fairly difficult to do. In addition, I just fundamentally disagree with the way you have to implement them because you can get incorrect answers in some cases.

One of the key challenges is that you never know whether it is how your developers developed it or whether it was the tool. We did find that once we got into more complex models, the ability to keep objects that should tally the same way but didn't became more and more difficult. That was probably the big thing for me. I don't know enough about how the tool was developed to know whether that was because they didn't follow a recommended practice. That was probably the number one thing that I found frustrating with it.

When we started to try and get into some very granular data sets that had some complex relationships in them, the performance on it degraded pretty quickly. It did degrade to such an extent that we couldn't use it. We had to change what we were trying to do and manage its scope so that we could get what we wanted out of it or reduce the scope of what we needed out of it. It doesn't have a database behind it, per se. So, while doing some of the more complicated things that you might otherwise do on a database, we started hitting some pretty significant challenges.

I used it for about three years.

Tableau worked fairly well for straightforward data sets, but it struggled when we got into the more complicated data sets and larger data sets. 

We were able to deploy it fairly broadly without a whole bunch of work. From that perspective, it worked fine. I was deploying my stuff to about 200 users across Canada, and I don't think we saw a blip on the server when people logged in. It was fine. If we were to roll out some of the bigger applications broadly, like the ones that we were having performance challenges with, we probably would have crushed the box. We would have had to get more CPU. Most likely, it would have been a memory issue, but we never hit that inflection point.

There were about 200 users of the solution. It went all the way from the equivalent of a senior vice president and all the way down to the equivalent of a line manager. So, we had business unit leaders, vice presidents, and operational managers.

It was being used extensively for a specific use case. There were lots of other use cases that it could be used for, but there needs to be an appetite from leadership to go, drive, and commit resources to go do that.

I didn't have to deal with technical support. Mr. Google is pretty good on the topic.

We had previously used Cognos to do the exact same thing. The only reason why we replaced it was that the business decided to go towards Tableau. Otherwise, there really wasn't any real reason to replace it. It was probably a little bit easier and more interesting for people to learn and to develop applications in the program than in Cognos. The ramp-up time to get to reasonably proficient in Tableau plus the support through Mr. Google made it a lot easier for me to get resources and do development on Tableau as compared to Cognos.

The organization decided to move away from the old platform. So, basically, I was lost when they asked me to shift off so that they could shut it down. I personally prefer the previous platform. I understood it very well. I had used it for years, and it worked just fine. For the most part, the challenges that we had on the old platform were not resolved by Tableau, which just reinforced to me that it wasn't a tool problem. It was a people problem.

It was pretty straightforward. The big thing that confuses people in a project that involves Tableau is that Tableau is a very visible but small component of the overall solution. That's because 80% of the work is data. It is not Tableau. So, Tableau is actually a fairly small component over that overall solution. It took a few days to get it up and going. Almost 80% of the work is actually on the data side, which takes forever, but the actual Tableau component of it was pretty straightforward. It was not that difficult.

You can get a Tableau dashboard up on a weekend. It is not hard to get something up and running. It is pretty trivial. It isn't any more or less difficult than any other tool to get up and going. I've used a number of them, and they're all pretty easy to get up and going. Tableau was the first one out of the gate with this democratized data perspective, where they were going to do departmental BI and up to enterprise BI years ago. Now, they now charge a fairly hefty premium to leverage that product. It is not a cheap product.

In terms of maintenance, it can take as much or as little as you want because it just runs. So, technically, you don't have to have anybody to do very much. You just need a very skeleton crew to operate as is. The challenge that you run into with solutions like this is that you need to continue to refresh the information with new and different views because people want to know more, and they want to go deeper into it. It is not a function of the technology. It is a function of the use case. So, you tend to have lots of new requests for new reports and analysis, and that's where you tend to have more challenges.

We didn't get into analysis users who are able to sort of do a little bit more themselves. There were viewer licenses where you are just using preset reports, but there are obviously additional training and things like that, and you have to deal with it if you start getting into more advanced power users.

I was at another company, and we were the integrator.

It is fairly expensive. I have no idea what they paid. We were on an enterprise license, so whatever it is they licensed at the enterprise level is what we paid.

A good chunk of it has got nothing to do with the tool. It has everything to do with your leadership and your governance requiring it. We had our IT team roll up Tableau multiple times and not a single person used it because there just wasn't enough leadership support to use it. There is nothing wrong with the tool, and it worked fine for what it did, but every time I logged into it, I go, "Okay, but what did you want me to actually do with this? I see all this information. I understand it clearly. I'm not sure what I do with it though." So, without that additional guidance from leadership, rolling it out is irrelevant. You need to have that strategic leadership associated with it.

The key piece of advice would be that you got to look beyond your tool. You need to look at how you're going to get this information used in your organization. What kind of leadership support, governance support, and ongoing support are you going to have? It is all based on trusted data. The value of the tool is based on the quality of your data and the leadership's support to use it. So, if you don't have high-quality data and you don't have leadership support to use the data, you don't need any tool because nobody is going to use it.

I would rate Tableau a seven out of 10. It suits the purpose, but in and of itself, I don't think it is significantly better or worse than its key competitors.

I have found the solution easy to use and the interface is very good.

I have been using Tableau for two weeks.

The solution is stable compared to others solutions.

The setup was easy but we are having some problems with the configuration that is taking a long time. We have done some initial tests and some of the delays could be from bandwidth issues. However, the whole installation process should be simplified.

We have evaluated Domo, Microsoft BI, and Qlik, and we have found Tableau is much better.

I would recommend this solution to others.

I rate Tableau a seven out of ten.