NVivo is qualitative data analysis software used to organize, code, and interrogate unstructured material such as interview transcripts, focus group recordings, open-ended survey responses, documents, and field notes. It does not analyze your data for you. It is a workbench that holds your material in one project, lets you attach codes to passages, and then retrieves and compares everything you coded a given way, so you can build and defend an interpretation across a large body of text.
Understanding what NVivo does and does not do prevents the most common disappointment. The software speeds up the mechanics of qualitative analysis, storing data, applying codes, running queries, and keeping an audit trail. The analytic thinking, deciding what a passage means and how codes build into themes, remains yours. A tool cannot rescue an unclear research question or a vague coding framework.
What NVivo actually does
At its core, NVivo lets you create a codebook of categories, called nodes, and tag any segment of text, audio, or image to one or more of them. Once material is coded, you can code and retrieve, pulling together every passage assigned to a node to examine the evidence for a pattern in one place. You can run queries that cross-reference codes with attributes, for example comparing how a theme appears across different participant groups, and you can visualize relationships among codes.
This is the practical advantage over manual coding with highlighters and spreadsheets. With a few hundred pages of transcripts, retrieving every mention of a concept by hand is slow and error-prone. NVivo makes retrieval instant and keeps a record of every coding decision, which supports the audit trail that gives qualitative findings their credibility.
NVivo and Atlas.ti
NVivo's closest competitor is Atlas.ti, and both are mature, capable tools that support the same fundamental workflow of coding, retrieval, and querying. Differences lie in interface, visualization style, and pricing rather than in what analysis is possible. The choice between them rarely changes your findings; it changes how comfortable the daily work feels. What matters far more than the software is the quality of your coding framework and the rigor of your method, whether that is thematic analysis, content analysis, or grounded theory.