SPSS Statistics is a software package used for statistical analysis. It is now officially named "IBM SPSS Statistics". Companion products in the same family are used for survey authoring and deployment (IBM SPSS Data Collection), data mining (IBM SPSS Modeler), text analytics, and collaboration and deployment (batch and automated scoring services).
$99
per month per user
Tableau Desktop
Score 8.3 out of 10
N/A
Tableau Desktop is a data visualization product from Tableau. It connects to a variety of data sources for combining disparate data sources without coding. It provides tools for discovering patterns and insights, data calculations, forecasts, and statistical summaries and visual storytelling.
If I didn't want to code, IBM SPSS would be after JMP and Tableau, and before SAS and R. The user interface is very clunky compared to the analytics software I stated. You could definitely learn to do basic analysis faster in SAS than SPSS. I selected SPSS to test the …
I also use or have used Tableau, Excel, and R (wasn’t able to list R above). Tableau is better for visualizations, Excel works for generalized/more basic statistical analysis but lacks more complex features, and R has been difficult for me to master and lacks the UI and ease of …
Compared to Stata, python and MPlus, SPSS is more user friendly especially for beginners. It displays data and output in easily readable formats and makes statistics fun and easy. However, Stata, python and MPlus are more ideal for complex statistical methods like structural …
Two alternatives I considered before choosing SPSS are the programming languages R and Julia Statistics. Both are freely available, open-source packages for sophisticated statistical analysis and visualization. In my case, I preferred SPSS to these somewhat newer options due …
Select IBM SPSS because it is a program that is easier to use than RStudio [which] requires the application of much more work hours to master and make the most of each of the tools it offers.
I use Stata for tasks that SPSS cannot support, but ultimately SPSS has a short learning curve, strong statistical processing, and a mature tool set. SAS is also mature, but more programming based. JMP tries to 2nd guess what I need. NOTE: R (open source) is a great option …
I have used SAS, R, Systat, Stata, Excel, Access and I continually find myself using SPSS to do the same set of tasks I would be using the previously named software to do. It's an all encompassing software that is very easy to use but can become as powerful an analytical tool …
Graphics within SPSS provide you with a general framework for understanding your data, so that you will be better able to interpret the complex inferential procedures that follow.
I described earlier that the only scenarios where I use SPSS are those where we have legacy projects that were developed in the late 90s or early 2000s using SPSS, and for some reason, the project (data set, scope, etc.) hasn't changed in 24+ years. This counts for 1-2 out of around 80 projects that I run. Whenever possible, I actively have my team move away from SPSS, even when that process is painful.
The best scenario is definitely to collect data from several sources and create dedicated dashboards for specific recipients. However, I miss the possibility of explaining these reports in more detail. Sometimes, we order a report, and after half a year, we don't remember the meaning of some data (I know it's our fault as an organization, but the tool could force better practices).
SPSS has been around for quite a while and has amassed a large suite of functionality. One of its longest-running features is the ability to automate SPSS via scripting, AKA "syntax." There is a very large community of practice on the internet who can help newbies to quickly scale up their automation abilities with SPSS. And SPSS allows users to save syntax scripting directly from GUI wizards and configuration windows, which can be a real life-saver if one is not an experienced coder.
Many statistics package users are doing scientific research with an eye to publish reproducible results. SPSS allows you to save datasets and syntax scripting in a common format, facilitating attempts by peer reviewers and other researchers to quickly and easily attempt to reproduce your results. It's very portable!
SPSS has both legacy and modern visualization suites baked into the base software, giving users an easily mountable learning curve when it comes to outputting charts and graphs. It's very easy to start with a canned look and feel of an exported chart, and then you can tweak a saved copy to change just about everything, from colors, legends, and axis scaling, to orientation, labels, and grid lines. And when you've got a chart or graph set up the way you like, you can export it as an image file, or create a template syntax to apply to new visualizations going forward.
SPSS makes it easy for even beginner-level users to create statistical coding fields to support multidimensional analysis, ensuring that you never need to destructively modify your dataset.
In closing, SPSS's long and successful tenure ensures that just about any question a new user may have about it can be answered with a modicum of Google-fu. There are even several fully-fledged tutorial websites out there for newbie perusal.
An excellent tool for data visualization, it presents information in an appealing visual format—an exceptional platform for storing and analyzing data in any size organization.
Through interactive parameters, it enables real-time interaction with the user and is easy to learn and get support from the community.
collaboration - SPSS lacks collaboration features which makes it near impossible to collaborate with my team on analysis. We have to send files back and forth, which is tedious.
integration - I wish SPSS had integration capabilities with some of the other tools that I use (e.g., Airtable, Figma, etc.)
user interface - this could definitely be modernized. In my experience, the UI is clunky and feels dated, which can negatively impact my experience using the tool.
Both money and time are essential for success in terms of return on investment for any kind of research based project work. Using a Likert-scale questionnaire is very easy for data entry and analysis using IBM SPSS. With the help of IBM SPSS, I found very fast and reliable data entry and data analysis for my research. Output from SPSS is very easy to interpret for data analysis and findings
Our use of Tableau Desktop is still fairly low, and will continue over time. The only real concern is around cost of the licenses, and I have mentioned this to Tableau and fully expect the development of more sensible models for our industry. This will remove any impediment to expansion of our use.
Probably because I have been using it for so long that I have used all of the modules, or at least almost all of the modules, and the way SPSS works is second nature to me, like fish to swimming.
Tableau Desktop has proven to be a lifesaver in many situations. Once we've completed the initial setup, it's simple to use. It has all of the features we need to quickly and efficiently synthesize our data. Tableau Desktop has advanced capabilities to improve our company's data structure and enable self-service for our employees.
When used as a stand-alone tool, Tableau Desktop has unlimited uptime, which is always nice. When used in conjunction with Tableau Server, this tool has as much uptime as your server admins are willing to give it. All in all, I've never had an issue with Tableau's availability.
Tableau Desktop's performance is solid. You can really dig into a large dataset in the form of a spreadsheet, and it exhibits similarly good performance when accessing a moderately sized Oracle database. I noticed that with Tableau Desktop 9.3, the performance using a spreadsheet started to slow around 75K rows by about 60 columns. This was easily remedied by creating an extract and pushing it to Tableau Server, where performance went to lightning fast
I have not contacted IBM SPSS for support myself. However, our IT staff has for trying to get SPSS Text Analytics Module to work. The issue was never resolved, but I'm not sure if it was on the IT's end or on SPSS's end
Tableau support has been extremely responsive and willing to help with all of our requests. They have assisted with creating advanced analysis and many different types of custom icons, data formatting, formulas, and actions embedded into graphs. Tableau offers a weekly presentation of features and assists with internal company projects.
It is admittedly hard to train a group of people with disparate levels of ability coming in, but the software is so easy to use that this is not a huge problem; anyone who can follow simple instructions can catch up pretty quickly.
I think the training was good overall, but it was maybe stating the obvious things that a tech savvy young engineer would be able to pick up themselves too. However, the example work books were good and Tableau web community has helped me with many problems
Have a plan for managing the yearly upgrade cycle. Most users work in the desktop version, so there needs to be a mechanism for either pushing out new versions of the software or a key manager to deal with updated licensing keys. If you have a lot of users this needs to be planned for in advance.
Again, training is the key and the company provides a lot of example videos that will help users discover use cases that will greatly assist their creation of original visualizations. As with any new software tool, productivity will decline for a period. In the case of Tableau, the decline period is short and the later gains are well worth it.
I have used R when I didn't have access to SPSS. It takes me longer because I'm terrible at syntax but it is powerful and it can be enjoyable to only have to wrestle with syntax and not a difficult UI.
I have used Power BI as well, the pricing is better, and also training costs or certifications are not that high. Since there is python integration in Power BI where I can use data cleaning and visualizing libraries and also some machine learning models. I can import my python scripts and create a visualization on processed data.
Tableau Desktop's scaleability is really limited to the scale of your back-end data systems. If you want to pull down an extract and work quickly in-memory, in my application it scaled to a few tens of millions of rows using the in-memory engine. But it's really only limited by your back-end data store if you have or are willing to invest in an optimized SQL store or purpose-built query engine like Veritca or Netezza or something similar.
I found SPSS easier to use than SAS as it's more intuitive to me.
The learning curve to use SPSS is less compared to SAS.
I used SAS, to a much lesser extent than SPSS. However, it seems that SAS may be more suitable for users who understand programming. With SPSS, users can perform many statistical tests without the need to know programming.
Tableau was acquired years ago, and has provided good value with the content created.
Ongoing maintenance costs for the platform, both to maintain desktop and server licensing has made the continuing value questionable when compared to other offerings in the marketplace.
Users have largely been satisfied with the content, but not with the overall performance. This is due to a combination of factors including the performance of the Tableau engines as well as development deficiencies.