Try our new research platform with insights from 80,000+ expert users
reviewer1311126 - PeerSpot reviewer
Managing Partner at a tech services company with 51-200 employees
Real User
Top 5Leaderboard
Tableau is not just a dashboarding solution, it is also a visual analytics solution
Pros and Cons
  • "One of the most valuable features of Tableau is that it's a visual analytics solution, not just a dashboarding solution. Compared to Power BI, which is a dashboarding solution, there are no limitations with Tableau. For example, when you add a chart or a map to Power BI, it has a 3,000-point limitation. When you try to track your whole vehicle on the map, you only see the first 3,000 rows on the map, and Power BI doesn't tell you which part of the data is shown on the map. But Tableau doesn't have any limitations, which means that you can see five million data points on a map. It starts the project by creating the visuals that directly converts to SQLs. In that way, all the components have no limitations. When we compared Tableau to Power BI, we also found Tableau to be more fancy. Fancy means you can create more visual graphics and more visual dashboards. With Power BI, this isn't so—it's just some tables and some simple charts together. Tableau is more for business users who want to analyze data. Tableau can directly connect the analytics systems, like R or Titan, and get the results in screen, so it's a good solution for analytics scientists. It has some predefined capabilities to understand the data."
  • "Tableau's automatic insight could be improved. It has some predefined capabilities to understand the data, but I think they need more. Customers need more insight automatically from data—they don't want to discover them, they want to get the forecast automatically. The data preparation should also be improved because it's not easy. Tableau tries to focus on the business side, but the backend side has not improved much. They also have an ETS solution, but it's limited."

What is our primary use case?

Tableau is primarily used for analyzing data. It is not just a dashboarding solution, it is also a visual analytics solution, which means that end users can make their own analyses on that product. They can find lots of findings. The product has lots of capabilities that allow the user to focus on data. 

What is most valuable?

One of the most valuable features of Tableau is that it's a visual analytics solution, not just a dashboarding solution. Compared to Power BI, which is a dashboarding solution, there are no limitations with Tableau. For example, when you add a chart or a map to Power BI, it has a 3,000-point limitation. When you try to track your whole vehicle on the map, you only see the first 3,000 rows on the map, and Power BI doesn't tell you which part of the data is shown on the map. But Tableau doesn't have any limitations, which means that you can see five million data points on a map. It starts the project by creating the visuals that directly converts to SQLs. In that way, all the components have no limitations. 

When we compared Tableau to Power BI, we also found Tableau to be more fancy. Fancy means you can create more visual graphics and more visual dashboards. With Power BI, this isn't so—it's just some tables and some simple charts together. 

Tableau is more for business users who want to analyze data. Tableau can directly connect the analytics systems, like R or python, and get the results in screen, so it's a good solution for analytics scientists. It has some predefined capabilities to understand the data. 

What needs improvement?

Tableau's automatic insight could be improved. It has some predefined capabilities to understand the data, but I think they need more. Customers need more insight automatically from data—they don't want to discover them, they want to get the forecast automatically. 

The data preparation should also be improved because it's not easy. 

Tableau tries to focus on the business side, but the backend side has not improved much. They also have an ETS solution, but it's limited. 

For how long have I used the solution?

I have been working with Tableau for four years. 

Buyer's Guide
Tableau
January 2025
Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.

What do I think about the stability of the solution?

Tableau is stable, but the analytic tools don't distribute. You should subscribe in analytic prospectus. In that way, Power BI or Calique or Tableau uses subscription instead of publication, so if the user should ask something or should want to avail of something, they focus on a report and click on subscribe. In that way, they get the data, so the business case is changing a little. Old products, like Oracle BI or SAP BusinessObjects, have more publication features that these kinds of products don't have. I think Tableau's publication feature needs to be improved. 

What do I think about the scalability of the solution?

Tableau is scalable. 

Which other solutions did I evaluate?

We also evaluated Power BI. We chose Tableau because it is a visual analytics solution, not just a dashboarding solution, so there are no limitations with Tableau. The second reason was because Tableau is more fancy—you can create more visual graphics and visual dashboards. However, Power BI has the advantage on the backend side. It has a huge cloud environment, but Tableau doesn't. 

What other advice do I have?

I rate Tableau an eight out of ten. 

Tableau has a good site named publictableau.com. There are lots of examples and millions of Tableau dashboards already published there. You can download the dashboard and see what's behind it, to analyze it. It's a good chance to create different kinds of dashboards. 

To those considering using Tableau, I would also advise that they understand the infrastructure of Tableau. Tableau uses lots of big data technology inside their product: Elasticsearch, Red Cache, Amazon Apache, etc. I think there are more than 50 different big data technologies inside them. If they know their infrastructure, they should understand the big data technologies also. 

Disclosure: My company has a business relationship with this vendor other than being a customer: Partner
PeerSpot user
Presidente at EDR
Real User
The interface is good, it is user-friendly, and it integrates well.
Pros and Cons
  • "It is very easy to implement and to use."
  • "A strict security measure is needed. I believe it is weak in terms of security."

What is our primary use case?

We are not resellers, we are developing in Tableau, and we are implementers.

What is most valuable?

It is very simple to use for the end-user. It is user-friendly.

It integrates well.

The interface is good.

It is very easy to implement and to use.

What needs improvement?

A strict security measure is needed. I believe it is weak in terms of security.

For how long have I used the solution?

We have been using Tableau for three years.

What do I think about the stability of the solution?

Tableau is a stable solution.

What do I think about the scalability of the solution?

The scalability is great.

We have ten users in our organization.

Which solution did I use previously and why did I switch?

We are also experienced in using Oracle OBIEE. We have the same application ruling in both technologies.

How was the initial setup?

We have no issues with the configuration.

We need two people to deploy and maintain the system.

What's my experience with pricing, setup cost, and licensing?

The price could be improved.

Licensing fees are paid on a yearly basis. 

The licensing is by addition, we currently have an administrator and the viewer.

What other advice do I have?

Yes, I would recommend this solution to others who are considering using it.

I would rate Tableau, a nine 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.
PeerSpot user
Buyer's Guide
Tableau
January 2025
Learn what your peers think about Tableau. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
reviewer1595463 - PeerSpot reviewer
Project Manager at a local government with 51-200 employees
Real User
Easy to use, stable, and offers competitive pricing
Pros and Cons
  • "The stability seems to be very reliable."
  • "There should be more widgets that would help less trained individuals create charts with less difficulty."

What is our primary use case?

I'm not using it on a daily basis. I've gone through the training and I've got my associate certification.

What is most valuable?

The solution is very easy to use and simple to understand. They make it very easy to navigate around it and to learn the product. 

The solution is very easy to set up.

The pricing is good.

The stability seems to be very reliable. 

What needs improvement?

Personally, I have not extensively used it, and therefore it's hard to think of areas that might need improvement as I haven't fully experienced every aspect of the product. 

I'd like to see more advanced forms of charting, if possible. 

There should be more widgets that would help less trained individuals create charts with less difficulty.

Tableau probably does not have advanced big data analysis features. It's not in the same category. It doesn't have those features to the same degree as R. You do this recreational; kind of modeling and analytics. It does have some predictive items, however, it's very simple. You can't customize much.

What do I think about the stability of the solution?

The solution seems to be very stable. I wouldn't say that we have used it in a big data kind of way. We don't have big data; we're not really able to test Tableau to the limits.

What do I think about the scalability of the solution?

Most of the companies that we work with that use it are medium-sized enterprises and is typically public companies or government organizations. 

How are customer service and technical support?

I can't really evaluate support services from Tableau. Our client agencies use them directly, and therefore they are the ones dealing with support. I don't have much experience on the support side.

Which solution did I use previously and why did I switch?

Some of our clients also work with Microsoft BI. I'd personally worked with Talend, SAP HANA, and Power BI. I personally prefer Tableau due to its ease of use. With SAP HANA, I don't really have easy access to it. However, with Talend, if I wanted to, I could easily go to its website and download a copy of it.

How was the initial setup?

The initial setup of the product is not difficult. It's very easy and quite straightforward. A company shouldn't have any troubles handling an implementation. 

What's my experience with pricing, setup cost, and licensing?

It's my understanding that the pricing of this solution is quite reasonable and very competitive. That said, I haven't really done an in-depth comparison against competitors.

What other advice do I have?

We are consultants and not exactly customers of the product itself. We run projects. We give policy guidance.

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

If a company is looking for a way to create charts quickly, and communicate with charts, Tableau is definitely an easy place to start. Of course, users will need some training to understand how to create certain visualizations in Tableau. Other than that, Tableau is quite easy to set up. It's easy to connect to your data sources. Once you have connected to the data sources, you easily create the charts. There's a lot of options, a lot of charts that you can create. However, for the more advanced features, you definitely need some experience. 

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user639489 - PeerSpot reviewer
Enterprise Risk Manager at a transportation company with 1,001-5,000 employees
Vendor
Presents analysis results in a visual manner, though improvement needed in filters when applied on large data sets

What is most valuable?

The most attractive feature for our users is the ease of visualizing data in a meaningful manner. The ease of experimenting with different visualizations is also very useful.

The ability to load and work with large volumes of data without requiring very high level of system resources is also valuable for us.

How has it helped my organization?

Key users of Tableau are from the Internal Audit team. Introduction of the tool has allowed the team to move away from data sampling to working with the entire data population in most cases. More importantly, the ability to present the analysis results in a visual manner to stakeholders, which has enhanced the ease of communicating the impact of the audit findings.

What needs improvement?

Improvement is required in the way filters operate when applied on large data sets. Having the ability to select and deselect filters without having to retrace the original path would make it easier to demonstrate the results.

For how long have I used the solution?

More than two years.

What do I think about the stability of the solution?

The maximum volume of data we have connected is approximately six million records each having about 130 data fields. We did not encounter stability issues when connecting to a pre-downloaded copy of the data. However, on trying to access the live data (a flat file system), the operation was very slow.

What do I think about the scalability of the solution?

No.

How are customer service and technical support?

With reference to the issue stated above, we noted that Tableau did not attempt to provide any resolution for the issue. We felt that they just left it with the local vendor to sort out the issue (which was never resolved).

Which solution did I use previously and why did I switch?

We have used (and continue to use) ACL for data analytics. However for simple analytics, and in particular, data visualization, we prefer to use Tableau. We have also seen that users are able to understand Tableau faster than ACL.

How was the initial setup?

The initial setup was for the desktop version of the tool connecting to Excel files and stand-alone databases at the back end. We did not have any issues with this.

However, on attempting to move to the server version, we faced issues with data connectivity for our core ERP which were not resolved. Attempting to connect to the Oracle HRMS module went without a hitch, and within a few seconds, we were able to perform live data analysis without any degradation in performance. Connecting to our core ERP (Kerridge Autoline, now known as CDK Autoline) failed due to ODBC driver version issues (we presume).

What's my experience with pricing, setup cost, and licensing?

The Desktop and Professional version pricing is straightforward. Cannot comment on the Server licensing aspect.

Which other solutions did I evaluate?

Qlik Sense and ACL.

What other advice do I have?

Thoroughly test your data connectivity requirements to make sure everything works well.

From an end user perspective, it is a very easy tool to use.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user6972 - PeerSpot reviewer
BI Expert at a non-tech company with 51-200 employees
Vendor
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.
PeerSpot user
it_user150534 - PeerSpot reviewer
it_user150534Analytics Manager at Quorum Review IRB
Vendor

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).

See all 3 comments
it_user6972 - PeerSpot reviewer
BI Expert at a non-tech company with 51-200 employees
Vendor
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.
PeerSpot user
it_user3678 - PeerSpot reviewer
it_user3678BI Consultant, Author, Trainer on Tableau Software, Speaker with 51-200 employees
Vendor

Nice write up, Kelly. LOVE seeing the passion for Tableau!

it_user1245 - PeerSpot reviewer
Project Manager at a computer software company with 51-200 employees
Vendor
Tableau is excellent for visualizing pre-built data or data that are already organized

Valuable Features:

• Graphical representation – great for showing trends over time or comparisons • Data source integration – can integrate with almost every type of databases/data sources like text files (csv, txt), SQL, SSAS, Oracle, etc • Flexible – very simple for a user to create reports with parameters and filters • Drill down – this functionality is built in so it is very simple to export into Excel and link from report to report, dashboard to dashboard. • Links - Using the URL you can link to any webpage or any report accessible via URL

Room for Improvement:

• Unlike Tableau, QlikView is a powerful, agile platform. • Lack of shortcuts – no controls such as dials or gauges which are generally find with dashboard • Poor Performance in hierarchical data– this is an usability problems when filtering as it doesn’t recognise the hierarchy. You can’t clear all filters enabling the user to start again when using complex filters • Unable to link parameters

Other Advice:

• Graphical representation of data - refers to the aggregation of data in a relevant and easy to read • Customizable Maps: Table 7 allows correlation with geographical indicators displayed by different colors. Each geographical area will receive a predefined color. For example, if economic growth in Spain it will receive colors depending on the level of growth • Related Charts: It is possible that in one chart to be visible all the variations. • In addition to the possibilities of visual correlation with indicators of geographical areas, the new version of BI offers a number of other new features: • multiple maps • Multiple names points / geographical areas (depending on language, types of abbreviations) • ability to add new points according to geographical longitude and latitude points • Automatic identification and centering it on the map for viewing relevance.
Disclosure: I am a real user, and this review is based on my own experience and opinions.
PeerSpot user
it_user4401 - PeerSpot reviewer
it_user4401Developer at a transportation company with 1,001-5,000 employees
Vendor

From my point of view, Tableau has three advantages: First is that the user can create visuals quickly and then switch between types easily in order to find the model that best represents the message. Second is that the user's interface is well organized and he can customize the view with a few clicks. And third is that defaults are based on best practices and the initial result contains nice color combinations and layout.

See all 2 comments
reviewer1774416 - PeerSpot reviewer
Data Analyst at a tech services company with 11-50 employees
Real User
A flexible product that makes it easy to do a lot of things and comes with great support
Pros and Cons
  • "It is so easy to do a lot of things. There is a lot of flexibility and creativity in this product. In other products, you don't have this flexibility."
  • "I would like Tableau Prep to be integrated with Tableau Desktop. I would also like more customizations for tables."

What is our primary use case?

We are a consultant, and it is our main product for consultancy.

It is deployed on the cloud as well as on-premises.

What is most valuable?

It is so easy to do a lot of things. There is a lot of flexibility and creativity in this product. In other products, you don't have this flexibility.

What needs improvement?

I would like Tableau Prep to be integrated with Tableau Desktop. I would also like more customizations for tables.

Its setup should be simple. It is complex to deploy if you work in a test environment.

For how long have I used the solution?

I have been using this solution for four years.

What do I think about the stability of the solution?

It is stable.

What do I think about the scalability of the solution?

It is easy to scale. It is suitable for small, medium, and large enterprise

How are customer service and support?

Their technical support is great.

How was the initial setup?

It is complex. If you work in a test environment, it is complex to deploy. It should be more simple. You need someone who can help you with deployment.

What's my experience with pricing, setup cost, and licensing?

It is reasonable based on what it offers.

What other advice do I have?

I would advise following Tableau Blueprint in your deployment. There are guidelines that will help you.

I would rate it a nine out of 10.

Disclosure: My company has a business relationship with this vendor other than being a customer: partner
PeerSpot user
Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros sharing their opinions.
Updated: January 2025
Buyer's Guide
Download our free Tableau Report and get advice and tips from experienced pros sharing their opinions.