Introduction

Motivation to try Atlas.ti 9 and write this review

As a PhD student, I did not have money to pay for expensive coding software, so I often used R for Qualitative Data Analysis (RQDA). It required a lot of research and experimentation, but I eventually was able to use it to code hundreds of open-ended survey questions that I collected for a study looking into the types of racial/linguistic ideologies encountered by multiracial/multiethnic individuals. However, as an open software, RQDA has not been updated in a long time, often froze, and was still difficult to figure out how to use due to limited documentation. The documentation that was available seemed to be catered towards experts in R programming.

As a new professor who finally has (limited) research funds, I decided to try a paid computer-assisted qualitative data analysis software (CAQDAS). However, I couldn’t find any reviews that could help me decide between popular ones such as Nvivo, Atlas.ti, and MAXQDA.

Hopefully this review can be helpful to others deciding between which CAQDS to choose.

What I was looking for in a CAQDAS

I needed a CAQDAS that could help me analyze hundreds of open-ended responses from surveys in addition to transcribed interviews. For me, the ability to quickly organize, find, and export code data in a tabular format was important.

My knowledge is limited to RQDA, Nvivo, and Atlas.ti

I only had a limited amount of time, so was only able to try out the trial version of Nvivo (for 14 days). The trial version of Atlas.ti 9 allows you only 5 days, but was able to use it for several months in exchange for writing this review. As I mentioned in the motivation section, I worked with R and RQDA for several years, so much of my review reflects my desire to have a CAQDAS that is compatible with R.

 

 

Review of Atlas.ti 9 (Desktop version for Mac)

It took me a little time to get used to Atlas.ti 9 because it wasn’t as intuitive as Nvivo. However, I got the hang of it after reading a few articles from Atlas.ti tutorials and working with it a day or two.

What I immediately noticed was how smooth/fast it was in comparison to Nvivo. With Nvivo (Mac version), the software because extremely slow after a couple days. It would take a few seconds to show codes and allow me to select them. This was frustrating since I had hundreds of segments of text to code and couldn’t make much progress after a while. I contacted the Nvivo customer service several times, but they took a week or two to get back to me and didn’t offer any solutions aside from what I had already tried based on the troubleshooting section of their website. It was unfortunate, because aside from how slow Nvivo was, it seemed to have great functions and a more user-friendly graphic-user interface.

With Atlas.ti 9 however, the software never slowed down. It was always extremely quick to show me the code list and let me search for the code I wanted to use for a given section of text.

A transcript with codes

A transcript with codes

 

Codes are shown in alphabetical order on the left side of the interface. You can also put codes into groups.

Example of Atlas.ti code list

Example of Atlas.ti code list

Unlike with RQDA, you can quickly search for the code you want to use after you select the text you want to tag. This is handy when you have a ton of codes you are working with.

Search for a code

Search for a code

 

You can double-click on a code to quickly see a list of all excerpts (called quotations) you have tagged with the code.

See all data with a given code

See all data with a given code

 

I also found it very useful to use the Query Tool and Search and Code functions to code data. This way I could easily search to see of there were other excerpts that seem to fit a code. I could search using Booleans (e.g., “contains X code”, “does not contain X document”) or regular expressions.

Documents are often data from participants such as survey responses or interviews. You can also group these (e.g. by participant or demographic group). They are also shown on the left side of the interface.

In order to work with survey data, Atlas.ti codes makes each participant (row of responses) into document “cases” and each survey question response into its own code. So if you have 50 participants and a survey of 20 questions, when you import the data (from an excel sheet for example), you will automatically have 20 codes attached to the data and 50 document cases.

To analyze data, you can create a “Code-document table” in order to select which codes and documents(participant data) you are interested in.

Code-document table

Code-document table

 

You can also use the quotation manager to find all excerpts of a given code and export it into an excel or .csv spreadsheet.

Quotation manager

Quotation manager

 

These were features of Atlas.ti I found particularly helpful for thematic analysis of the survey data I worked with.

 

Bullet-point Summary

Some parts that are significantly (and crucially) better than R for QDA:
  • ability to look up and select codes quickly during open coding/tagging process
  • ability to export Excel spreadsheets of codes/descriptions, quotations from transcripts belonging to each code, coding frequencies for each document
  • ability to work with opened-ended response survey data (although it takes some time to learn how to work with the data)
  • ability to use Search & Code with text, regular expressions, or proper nouns/names in order to quickly find/code data with certain phrases
  • ability to easily write memos/reflections throughout the coding process
Improvements over Nvivo (for me personally):
  • does not slow down over time like Nvivo, especially on a Mac–very important
  • the Support team is very quick to reply to questions –also a huge plus
Some demerits of Atlas.ti 9:
  • The code list is in alphabetical order, but I wish there was the option to organize based on categories/subcategories/codes (similar to Nvivo). It is important for me to be able to have all the codes relevant to a specific group in one, easily selectable area because I use this when selecting data to analyze or export into Excel spreadsheets. Right now all the codes in the list are ordered alphabetically, so I can work around this by renaming each code to reflect a category (e.g., AGENCY: Cultural capitalaccording to cultural norms). However, the name gets long, so it gets harder to read the entire code name on Atlas.ti’s interface when recoding/recategorizing data.
    • Note: there is an ability to make “code groups,” but this did not make it easier to find the code I was looking for when tagging data.
  • It would be nice if it had the ability to create sunburst and tree diagrams quickly (like Nvivo or R), but since I can export the data and create these diagrams with R it is not a deal-breaker for me.
  • It is quite expensive, so only individuals with access to funding or have a lot of extra cash can access this resource. As a multiracial researcher cares a lot about promoting a diversity of voices in academic research, this troubles me. Academic institutions (especially in the U.S.) are overwhelmingly White and appeal to White epistemologies (Kubota, 2020), so it worries me when poorer institutions and academics (e.g., those in third world countries, nonWestern countries) are unable to access the same academic resources and materials as White dominant institutions. To be clear, this is not just a problem for Atlas.ti–this is a problem with academia and research in general (we need more open access to journals/articles/technology). However, Atlas.ti and other industries could help solve this issue by providing case-by-case pricing based on the institution, position, access to research funds, location, etc. I reached out to Atlas.ti and they were very supportive in negotiating with me (with my limited funding options at a nonWestern institution) to find a reasonable solution. Part of it involved having me write and publish this review, which I was happy to do.

Verdict

As someone who uses R for data visualizations and statistical analyses, a crucial point for me is the ability to export data in tabular format. Since Atlas.ti has a huge number of options for exporting data as Excel files once you’ve coded your data, this is a huge selling point for me. I feel that I can still make interactive visualizations (e.g. sunburst diagrams, tree diagrams, etc.), do statistical analyses, etc. using R after doing the coding in Atlas.ti.

However, for me, the largest determiner is price. Atlas.ti is expensive, so I would use the free R for Qualitative Data Analysis over Atlas.ti if I did not have some funding to pay for it.