NVivo does not analyze anything. You do, and it keeps the receipts
The most common disappointment with NVivo is discovering it will not find your themes. What it is genuinely good at is holding a large amount of material, letting you interrogate it quickly, and producing an audit trail that a committee will accept. Those are worth having, and they are learnable in a few sessions.
Get your free quote
We reply within 1 business hour, no delays.
No card details required · 100% confidential · On time, or it's free
Most NVivo pain is created in the first hour of the project
Projects that become unusable usually went wrong at setup. Files imported without a naming convention, no case classifications, demographic information sitting in a separate spreadsheet, and codes created ad hoc as the researcher went along. None of that is fatal on its own. Together they produce a project where you cannot run the query you want six months later.
The setup that avoids it takes about an hour. Cases for your participants, classifications carrying their attributes, a folder structure that matches how you will actually want to slice the data, and a coding structure with some hierarchy rather than two hundred flat nodes.
Get that right and the software starts paying you back. Matrix coding queries comparing themes across participant groups, in seconds, is genuinely difficult to do by hand and is exactly the kind of evidence that strengthens a findings chapter.
- Cases and classifications set up so attributes are queryable later
- A hierarchical coding structure rather than a flat pile of nodes
- Memos and annotations used as the audit trail they are meant to be
- Queries that answer the question you actually have
What we cover
Driven by your project rather than a generic curriculum
- Project setup, import and file naming that survives the whole study
- Coding in the software, and when to code on paper first
- Case classifications and attributes for comparison across groups
- Matrix coding, crosstab and coding comparison queries
- Getting output into your thesis without reformatting it twice
Where NVivo earns its license fee
Large or messy datasets
Forty interviews, mixed media, documents and field notes together. Beyond a certain volume, managing this by hand stops being feasible and this is where the software clearly wins.
Comparison across groups
How did this theme differ between early-career and senior participants? A matrix coding query answers it immediately, and answering it by hand is slow enough that most people simply do not.
The audit trail
Memos, dated coding, and a record of how the frame changed. Committees increasingly ask for this, and NVivo produces it as a side effect of working in it properly.
Not for finding themes
Auto-coding and word frequency are not analysis, and a findings chapter built on them reads exactly as it was made. The interpretation is yours and the software cannot do it.
Working on your project, not a training dataset
You send the project file or a description of it
If the project exists, we look at what is there. If it does not, better still, because setting it up right at the start saves the most time.
Set up or repair the structure
Cases, classifications, folders and a coding hierarchy. If the project is already underway, this may mean reorganizing rather than starting over, which is usually possible.
Code together on a subset
Shared screen, your data, your decisions. The point is that you learn the workflow on the material you actually have, so it transfers the moment the session ends.
Learn the queries that matter to you
There are many and most people need three or four. We work out which ones answer your research questions and you practice those rather than touring the menus.
Get output into the thesis
Exports, tables and figures that go into your document without a day of reformatting, and that are labeled the way a committee expects.
We teach the software and work alongside you
- We do not code your project for you.
- We do not run your analysis and hand back results.
- We do not write your methodology or findings chapters.
- We do not supply someone else's project file for you to adapt.
- We teach the tool on your data, and review what you produce with it.
NVivo is licensed software from Lumivero and you need your own license. Many universities provide one, and it is worth asking before buying. Read the full policy.
Frequently Asked Questions
Usually not. Good qualitative work is done in spreadsheets, in Word and on paper every day, and using software does not make an analysis rigorous. It helps most with large datasets, comparison across participant groups, team coding and audit trails. If none of those describe your project, the learning time may be better spent elsewhere.
Enough to work in it, a few hours. Enough to use queries well on your own project, a few sessions spread over the analysis. The thing that takes longest is not the software, it is deciding what you want to ask of your data.
It has auto-coding and word frequency tools, and neither produces themes in any meaningful sense. They can be useful for orientation on a large dataset. A findings chapter built on them is transparent to an examiner and is one of the fastest ways to lose credibility in a viva.
Almost always, and this is a common starting point. Nodes can be merged and reorganized, cases and classifications can be added retrospectively, and files can be renamed. It is tedious rather than impossible, and it is far better than carrying on and finding you cannot run the query you need.
There is a Mac version, and it has historically lagged the Windows version on some features. If a specific query type matters to your design, check it is available on your platform before you commit, because discovering the gap during analysis is expensive.
For a first project, often yes. Coding a couple of transcripts by hand forces you to think about meaning rather than about where the button is. Then bring the frame into the software once you know what it is.
The method work is identical across all of them and transfers directly. Tell us which you are using and we will tell you honestly how much software-specific help we can give on that one before you book anything.
Send the project file, or tell us what you are about to start
We will tell you what needs setting up, what needs repairing, and which handful of features will actually matter for your research questions.
Get NVivo Help