Tableau Reviews

The data blending capabilities is a huge factor for our team. The ease of blending data from multiple sources has allowed us to generate new insight and bring a different level of questions to the meeting table. The type of dashboards we have been able to create have made it easier for individuals who are not use to looking at data to navigate and drill into their own material to find answers or ask questions they never thought to ask in the first place.

We’ve been able to replace several manual spreadsheet reports that took hours for individuals to complete. With Tableau Server and some automation processes put in place, those reports are now automatically delivered to the end users, saving time and money. We can also develop reports much faster than in the past plus provide an interface to a database which in the past might not of been used as much due to the lack of technical skills to write the queries.

Formatting controls could use some improvement. We’ve found that to be the most confusing part of developing reports, at least until you get use to where all the controls are at and how to use them. Ideally, making a user-friendly interface for formatting the worksheets and dashboards would be a big improvement and time saver. Recent version upgrades have added some new features such as being able to change the format for your entire workbook all at once. Still a work in progress though.

I have used it for eight years and sever administrator for 2 years.

Deployment and stability have been flawless so far. We’ve not encountered a data set that has slowed the software down and we use records with millions of rows. There is no clear-cut line of determining when best to consider switching over to an enterprise-wide model vs. per license, so there could be a better way of informing their customers on when to flip that switch.

We have never experienced an issue with the server software or any technical problems with the desktop or interactor licenses.

Once others in the company start seeing what it can do they immediately ask what needs to happen so they can get a license. We started down the path of looking at core enterprise licensing but were told the company is moving away from that model and sticking with a per user/license structure. Depending on how many in the company want to start using the software plus needing the additional interactor license to access the server the purchases can add up quickly.

Very little need to contact their customer service but when I did they were professional and quick to respond.

Both customer service and technical support have been excellent. Sales reps have been very nice to work with and you don’t end up with that used car salesmen feel. In fact, we typically meet with our reps about 3-4 times a year and have been extremely supportive.

No - most of our reporting was done between MS Excel and MS Access.

Setup was extremely easy. Essentially a plug-and-play right out of the box.

We implemented it in-house. Implementation was easy in comparison to other systems we’ve worked on in the past. QA testing was seamless and found no integration issues.

We’ve found quite a bit of savings using Tableau, based on the time it takes to develop ad-hoc reports, changes in process due to new insights and report automation.

Best advice on pricing is to anticipate the desire for more licenses once the results of this product are acknowledged in other parts of your company. Note that for others to interface with a published report on your server, they need what’s called an interactor license. We acquired several guest interactor licenses in order to lend out to departments so they can see the benefit of accessing their reports on the server vs. static reports. This encourages them to purchase their own interactor licenses or at least plan to purchase when preparing their budgets for the following year.

We evaluated several potential software systems such as Visier, Lumira, and Qlik, but found Tableau the easiest to use for individuals who did not need to have a programming background. Plus, the freedom to develop from a blank canvas with data that could be from any corner of the company appealed more to our team than working with a set of canned metrics to one specific department.

The annual Tableau customer conference is a huge learning opportunity for new and seasoned users alike. The week-long conference provides a large number of workshops to help increase your skills and many of these sessions are hands-on training. Also a great way to network with other users and see how they are using Tableau.

I have been using Tableau since 2006; 3.5 years as an employee of Tableau Software and 7 years as a trainer/consultant. The more robust features include improved geo-encoding. Shape content is a big winner, as is cluster analysis. Cross-DB joins are helpful, as well. A huge improvement is the ability to render DV to any device from phone to PC.

As a training organization, the subject of improving organization functions is somewhat opaque. The overall view is that we see software as a service as the big win for any client. Note well: To truly realize organizational change, top management must embrace the use of Tableau.

• 100% in the cloud.
• Reduce the price once in the cloud.
• Go back to emphasizing simplicity.

I have used it for 10 years.

We have not encountered any deployment issues; still fast and easy overall.

We have not encountered any stability issues. The QC process seems to improve with each major release.

We have not encountered any scalability issues.

On a scale of 1 to 10, customer service is an 8. It is helpful to hear a tel call from support but not without advance notice. Also, some of the new support folks are not up to speed with more challenging subjects.

There are no 10s in real life; technical support is 8.5.

Initial setup was not complex at all.

Generally, assessing ROI is a very open-ended question. Real ROI if that significant will never be revealed. Day-to-day savings are in time savings, which are viable, to say the least.

We do studies for firms as part of our services. QLTek is still viable but more and more we are hearing about Power BI. Carolina Health Systems just adopted Power BI to replace Tableau due to server costs.

We find that there is a new type of Tableau user emerging. These new users do not abide by the tenets of data visualization by thought leaders like Stephen Few. Hence, we created a blog for an open discussion comparing the work of the artist Jackson Pollock with this new generation. That blog is accessible below.

http://www.viainsights.com/Blo...

Note well: VIA Insights has no formal relationship with Tableau; we are completely independent.

The ease and speed of creating visualizations and interfaces with any database are this product’s most valuable features.

It is able to provide answers within hours instead of days. Typically, we would have to create a SSIS package to connect to that database, then create a SSRS report and meet with the users a few times before coming up with the final visualization product. With Tableau, we can create all of these in one session.

It would be great if the licensing cost per user was cheaper.

I have been using it for one year.

We currently cannot use version 9 because we have to wait for our Tableau Server to be upgraded to version 9 first.

Technical support is good.

We were previously using SSR for reports and SSIS for retrieving the data.

Installing Tableau Desktop was easy.

We worked with the Tableau team.

I would recommend lowering the licensing cost per user.

I would recommend that everyone use this product.

The ability to create visualizations of data is the product’s most valuable feature to me because it provides a meaningful view of the data and the metrics used by our clients.

The ease with which users can visualize and share data has improved how we look at our metrics.

It’s a very basic thing, but being able to copy and paste data elements from the screen would be nice.

I have used it for nine months.

I have not really encountered any deployment, stability or scalability issues. Our issues are not related to the function of the tool, but more to do with attitudes concerning looking at data and metrics.

It is well received when people see what it can do in transforming their data and metrics into meaningful displays that allow for greater insights.

• Very easy and fast to build dashboards, compared to many other BI tools
• Has connectivity options to various data sources
• Good community support and very useful free training videos

Clients are pleased with the beautiful and interactive dashboards. They are also happy with the noticeable shortening in time to production.

If it had a semantic layer, it would be great. I know Tableau is not meant for data modeling but the data warehouse is not always perfect. Without a semantic layer, we need to reach out to the ETL team for even small data model changes.

Also, a semantic layer would have allowed for building 'subject areas' by grouping tables and defining joins. This would then allow users with appropriate permissions to build ad-hoc reports without having to worry about table joins.

I have used it for 1.5 years.

We did not have any issues with deployment, stability and scalability. We deployed Tableau Server in the AWS cloud.

We have contacted customer support few times and the support team always came back with solutions / work-arounds promptly. So, customer service and technical support is good.

We evaluated a few other solutions, but we chose Tableau because of the speed with which we can build reports, the simple deployment (cloud), easy scalability and the cost factor.

Initial setup was straightforward and in fact very simple.

An in-house team implemented it, but we went for AWS cloud-based deployment, which was not complex.

Try the trial versions and explore all of the features before going in; it is very useful. Also, the training videos on their website are good.

Data Visualization & Analytics: In my last project, we used ESRI maps super-imposed with brand sales and sales history. By adding more dimensions to the data, we were able to drill from sales territories to analyze product sales at individual retail outlets. The next phase will be to add age-group demographics to the analytics.

That also describes our Agile approach. Incrementally add dimensions to the underlying data, and add richness to the analytics capability, and it’s a business-driven approach.

The client is in transition from traditional BI reports to real-time, mobile sales reporting, with a goal of eventually providing predictive analytics. The transition included a move away from IBM Cognos to Tableau, and using IBM Watson for predictive analytics. In this case, Tableau was able to do all the predictive analytics with less development effort and more visual results than Watson Analytics.

The trend I see from clients is towards more mobile solutions, more real-time analytics, and the integration of analytics and order entry. E.g. A sales consultant can seamlessly transition from sales analysis to entering an order while on-site. This implies a BPM integration with SAP, Oracle eBusiness Suite, SFDC and others.

The architecture this client was prototyping was an SFDC application with imbedded analytics provided by Tableau delivered to a tablet device. There are several ways to go about this, but the architecture was selected because SFDC was the system of record for all customer information.

I have used this solution on and off for about three years, more as Solutions Architect and Project Manager than a full-time developer.

I did not encounter any deployment issues, but a production deployment was outside of the scope of my role.

I know the client ran into several ODBC issues with the interface to Denodo, a data virtualization environment, but I can’t comment because Tableau support was outside of the scope of my role.

The client has a large Cognos footprint and they were looking to Tableau as a more agile reporting & analytics tool. For this project, we used Cognos 11 and were experimenting with IBM Watson Analytics. We were able to perform all the analytics they were doing in Watson Analytics, using Tableau.

In prior projects, I have experience with SAP BusinessObjects, SAS and QlikView.

Tableau was installed and configured by an in-house team and it was complete before I arrived on-site.

In my experience most (all) enterprise-scale clients have multiple, entrenched BI reporting tools that Tableau will have a tough time to displace. Tableau is most successful when it is introduced at a departmental or subsidiary level in an organization. That’s the starting point, and grow the ‘footprint’ from there. With that background in mind, make the initial pricing & licensing simple for a department to budget for & approve.

IMO, I don’t think any client can isolate an analytics tool and derive an ROI that stands up to scrutiny. I usually start by looking at a company’s annual report and I look for the transformational initiatives. E.g. They want more mobile capabilities, more real-time decision making, etc. I use that as the entry-point for discussion around capabilities, not a discussion of technical features and I look for real-world use cases to develop a solution architecture.

My advice to clients is always: Start with a clear goal in mind, generate some quick wins, and grow the environment from there. The enterprise-scale initiatives are big on vision, but I’ve seen more failures than successes.

The product is definitely a leader in the analytics-lite & data visualization space. Unless a client has a well-defined use case for one of the statistical or predictive analysis tools, Tableau can meet the needs. If the use case for Tableau becomes too complex, then clients can use the ‘R’ extension. I don’t have hands-on experience with that feature.

Without a doubt the best aspect of Tableau is the data flexibility. I work with Tableau within the confines of a healthcare organization- which is constantly expanding the metrics, datasets and sources we have to draw from in order to meet the needs of the US government, our physicians and most importantly our patients. With Tableau we have the ability to create a dashboard that displays all of the aforementioned data sources in a way that appears uniform.

Before we built a data platform using Tableau we were unable to align our employees around their data. We had a few dozen data sources representing important areas of focus for our operations teams. It was unreasonable to expect our operational leaders to consistently monitor the results of these different reports. Our hope was to build a platform everyone could access, that would be a one stop shop for reliable answers to important business questions; Tableau gave us that ability and made it affordable.

While Tableau is flexible it doesn't deal well with data that comes in a predetermined organization- i.e. data cubes. Our team has repeatedly had trouble trying to import raw data if it had any predetermined structure.

Two years.

No, it was pretty seamless.

The issues we have encountered have been largely due to our own server structure, not Tableau itself.

On the contrary, Tableau gave us the ability to manage larger volumes of data.

7/10.

7/10.

No, not for this purpose.

Very straightforward- we were live with access in a few days, though it took a few months to build our more polished dashboards.

Our decision support team handed deployment, in house.

You will need a team comprised of programmers, developers, user experience specialists and customer service representatives.

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.