

For those of you working in teams, descriptions are particularly important to ensure that everyone has a shared understanding of the nodes. Nodes often represent abstract or complex concepts, so it’s easy to forget what you intended, and meanings can evolve over time as your analysis progresses. This can be beneficial both to the coding process, as well as your overall data analysis. Take the time to enter descriptions when you create nodes. We’re not suggesting that these are the “right” way to code (we don’t believe there is such a thing), but we’ve certainly found that we’ve saved ourselves some time, not to mention headaches, by following the suggestions below! Note that this blog post refers to 'nodes' – if you're using a recent version of NVivo, these have been renamed 'codes'.

We’ve used NVivo extensively for coding over the years and have discovered a number of tips and tricks that we’d like to share.
