Qualitative content analysis: Steps, examples, and software

What is qualitative content analysis?

Qualitative content analysis is a systematic method for organizing and interpreting textual or visual data. It helps researchers explore large volumes of language-based material—finding patterns, mapping meaning, and generating insights—without reducing everything to numbers.

Unlike purely quantitative approaches that focus on counting words or codes, qualitative content analysis emphasizes meaning and context. Researchers using qualitative research methods work with many forms of data collection such as interview transcripts, survey comments, policy documents, newspaper articles, field notes, or social media posts. They isolate relevant segments and group them into data-driven or theory-guided categories that describe a phenomenon while staying grounded in the source material.

Originally developed in mass communication research, the method now supports studies in qualitative health research, education policy, linguistic anthropology, and other fields. Its strength lies in balancing structure with flexibility by providing a repeatable workflow while allowing categories to evolve as insights deepen.

In short, qualitative content analysis helps you:

• Organize large text datasets systematically
• Stay close to participants’ language
• Combine structure with interpretive depth
• Produce transparent, defensible findings

Qualitative vs. quantitative content analysis

Content analysis sits on a continuum between qualitative and quantitative traditions. The difference lies in how researchers use and interpret the same data.

Qualitative orientation

When the goal is to explain how meanings form, researchers focus on context. Codes remain open to refinement and review, especially among researchers working on the same study. Unlike quantitative content analysis, frequencies may be noted only to highlight emphasis—not to test hypotheses. Credibility checks such as peer review, reflexive journaling, and participant feedback support trustworthiness.

Quantitative orientation

A study shifts toward quantitative analysis when codes are fixed before reviewing data and counts are converted into quantitative data types to drive conclusions. Reliability statistics such as Cohen’s Kappa may become central to rigor.

Hybrid practice

Many projects combine both approaches. Categories may stem from theory, while researchers still interpret nuance. Counts may illustrate prominence, while narrative summaries explain why patterns matter.

Your research question ultimately determines where your project falls on this spectrum.

How qualitative content analysis differs from thematic analysis and grounded theory

Although these methods all organize qualitative data, their aims differ.

• Content analysis focuses on clearly bounded meaning units and often examines frequency and distribution.
• Thematic analysis identifies broader patterns across a dataset and emphasizes narrative synthesis.
• Grounded theory aims to generate theory through constant comparison and iterative sampling.

If your goal is to systematically organize and interpret patterns within a defined dataset—while optionally incorporating counts—qualitative content analysis is often the most direct fit.

Types of qualitative content analysis

Researchers choose between conventional, directed, or summative content analysis based on how firmly theory shapes the study question. These approaches follow the same broad workflow—preparing data, coding, categorizing, and interpreting—but they differ in when categories are defined and how flexible coding remains during analysis.

Conventional (inductive qualitative content analysis)

In an inductive analysis, categories emerge directly from the data during open coding. Codes that capture similar meanings are then merged into higher order categories, which can be refined through constant comparison until no new categories emerge. This approach is ideal for exploratory or under-theorized topics.

Directed (deductive qualitative content analysis)

The coding process begins with a predefined framework derived from theory or literature. Deductive qualitative content analysis supports model testing or policy evaluation.

Summative

Researchers examine the frequency or intensity of selected terms while interpreting underlying meaning. Counts highlight emphasis, but interpretation remains central.

Across all approaches, transparency in coding rules and documentation is essential.

When to use qualitative content analysis

Qualitative content analysis is especially useful when:

• You need a systematic yet flexible method for large text datasets
• You want categories that stay close to participants’ language
• You aim to combine structured coding with interpretive insight
• You benefit from optional counts alongside qualitative interpretation
• You are working with survey comments, policy documents, media texts, or social media data

It is particularly effective in applied research contexts that require structured outputs such as category summaries or dashboards.

Step-by-step guide to qualitative content analysis

Qualitative content analysis moves through a repeatable workflow that preserves the link between raw material and final findings. The eight steps below outline a typical path from data collection to writeup.

While analysis is iterative, most projects follow this structured workflow for content analysis:

1. Prepare and familiarize with the data set
2. Define the unit of analysis
3. Develop or refine the coding frame (codebook)
4. Pilot test the coding frame
5. Code the full dataset
6. Summarize categories and identify patterns
7. Check trustworthiness and reliability
8. Report the findings transparently

Clear documentation at every stage strengthens methodological rigor and credibility.

1. Prepare and familiarize with the data

Gather all relevant sources—interview transcripts, focus group recordings, policy documents, or social media captures—in a single project space. Transcribe recordings verbatim, correct obvious errors, and anonymize identifying details to protect participants. Export the cleaned files to a text searchable format such as .docx or .txt, then read through each file at least once without coding.

Use margin notes or memos to capture first impressions, interesting turns of phrase, and possible analytic angles. Early familiarization sharpens subsequent coding by clarifying how participants express ideas, which terminology they use naturally, and where contextual cues appear.

2. Define the unit of analysis

A unit of analysis is the smallest chunk of data that will receive a code. It can range from a single word to a full paragraph, depending on the research question. For a study on stigma language, a word or phrase may suffice; for work on workplace culture, a sentence or short paragraph provides more context.

Choose the unit deliberately, state the choice in the method section, and keep it stable across the dataset so counts and comparisons remain meaningful. When multiple units are plausible, pilot each option on a small subset to see which one captures the intended concept with the least ambiguity.

3. Develop or refine the coding frame

Create a coding frame that lists category names, brief definitions, and inclusion–exclusion examples. In deductive projects, categories derive from theory or policy guidelines; in inductive projects, they grow from open coding. Either way, aim for mutual exclusivity at the lowest level so a single unit fits one category unless a justified overlap exists.

Where hierarchical relationships matter, arrange categories into parent child branches to reflect increasing specificity. A well-defined frame reduces coder drift, supports transparency, and speeds later retrieval tasks. Store the frame in software notes or a shared document that updates automatically as revisions occur.

4. Pilot test the coding frame

Apply the draft frame to 5 to 10 percent of the dataset. If working in a team, code the same files independently, then compare segment to code matches. Note disagreements, vague definitions, or missing categories. Revise wording, merge overlapping codes, or split large codes that obscure important distinctions.

Retest until coders reach an acceptable level of agreement or, in single-coder studies, until the frame feels stable. Piloting prevents large scale re-coding later and produces an audit trail that shows how analytic decisions evolved.

5. Code the full dataset

Work through each file systematically, assigning codes to every qualifying unit. Keep reflexive memos close at hand to note uncertainties, emerging ideas, or contextual factors that influence meaning. Segment boundaries should remain consistent with the chosen unit of analysis; avoid expanding or shrinking units to force a fit.

In qualitative data analysis software (QDA software), use color coding or labels to flag units needing a second look. If double coding for reliability, set checkpoints (e.g., every fifth file) to discuss discrepancies and adjust the frame as needed. Coding is complete when all data are handled and no unresolved segments remain.

6. Summarize categories and identify patterns

Export code reports or run matrix queries to view all segments linked to each category. Write concise summaries that capture the gist of each category in plain language. Note relative prevalence, typical context, and any notable exceptions. Look for cooccurrences between categories, temporal sequences, or contrasts across participant groups.

Basic counts can highlight emphasis, while qualitative comparison clarifies how meanings differ. Where visualization helps, generate bar charts or cluster maps within the software; these outputs aid interpretation without supplanting narrative insight.

7. Check trustworthiness and reliability

Establish credibility by tracing every claim back to supporting segments and memos. Invite a peer to review the coding frame and a sample of coded text, asking whether the interpretation appears reasonable. If applicable, share preliminary findings with participants for comment.

Calculate intercoder reliability statistics such as Krippendorff’s α when using a fixed frame or rely on negotiated agreement when the frame evolves inductively. Maintain an audit trail that records coding decisions, memo entries, and frame revisions so external readers can follow the analytic logic.

8. Report the findings

Describe the dataset, unit of analysis, coding frame construction, and reliability checks in the method section. Present each major category (or theme, if categories were later aggregated) with a succinct definition and one or two illustrative quotations. When counts are informative, include a simple table that lists category frequencies or crosstabulations by group.

Discuss how patterns answer the research question, relate to previous studies, or point to practical implications. Provide enough excerpted data for readers to judge the fit between evidence and interpretation, but avoid overwhelming them with lengthy blocks of text.

Qualitative content analysis examples

The following fictional cases show how researchers could apply qualitative content analysis across different data sources and analytic logics. While not drawn from actual studies, each example walks through key decisions on units of analysis, coding frames, and trustworthiness checks, illustrating how the method adapts to varying research aims.

Example 1: Inductive analysis of patient experience social posts

Research aim and dataset. A qualitative health research team wanted to understand how patients talk about outpatient chemotherapy on social media. They scraped 12,000 public social posts during a six-month window, then sampled 2,000 English language posts that mentioned infusion clinics. Each post became the unit of analysis.

Coding workflow. Analysts imported the sample into their CAQDAS project and began open coding. Short phrases such as “long wait,” “nurse support,” and “billing shock” captured post content without forcing it into a predefined structure. After two rounds, the team grouped codes into broader categories—logistics, interpersonal care, physical side effects, and financial strain—checking that posts fitted one category at the lowest level.

Trustworthiness. Two coders double coded 10 % of the sample, negotiated disagreements, and refined definitions where overlap caused confusion. Memos recorded decisions to split “side effects” into “acute” and “delayed” subcategories when new patterns emerged. A peer reviewer outside the project read random excerpts linked to each category and agreed that the labels matched the content.

Key insight. The inductive approach surfaced an unanticipated category: “crowdsourcing tips,” where patients exchanged practical advice about managing nausea and scheduling. This category pointed the clinical team toward possible patient generated resources worth formal evaluation.

Example 2: Deductive analysis of university policy documents

Research aim and dataset. An education policy study examined how U.S. universities embed equity language in academic integrity policies. Researchers collected 150 publicly available policy documents from institutional websites. The unit of analysis was a sentence, chosen for its balance between context and specificity.

Coding frame construction. Drawing on existing equity frameworks, the team built a category matrix before coding: (1) inclusive language, (2) restorative practices, (3) punitive focus, and (4) student support resources. Each category carried inclusion and exclusion rules plus example sentences.

Analysis and reporting. A cross-tab query tallied category counts by university type (public flagship, regional public, private not-for-profit). Private institutions showed higher proportions of “inclusive language” and “student support,” while punitive language dominated regional publics. The report presented these proportions in bar charts and quoted illustrative sentences to show how equity references varied by institutional mission.

Practical outcome. Findings informed a policy briefing that highlighted gap areas and suggested revision templates grounded in the higher frequency restorative statements from peer institutions.

These examples demonstrate how inductive and deductive logics guide frame development, how unit choices shape comparability, and how trustworthiness checks align with the study design rather than a one-size-fits-all protocol.

Common pitfalls—and how to avoid them

Qualitative content analysis is systematic, but still interpretive work.

Common challenges in content analysis include:

• Vague or overlapping coding definitions
• Overreliance on counts
• Ignoring context
• Inconsistent units of analysis
• Weak documentation or limited audit trails

To avoid these issues:

• Define inclusion and exclusion criteria clearly
• Pilot test your coding frame
• Maintain reflexive memos
• Keep an audit trail of decisions
• Support claims with illustrative excerpts

These safeguards ensure your findings remain credible and defensible.

Qualitative content analysis with NVivo and ATLAS.ti

Modern qualitative research often involves large, complex datasets. Dedicated research software helps unify your data and streamline workflows.

Both NVivo and ATLAS.ti support:

• Importing mixed media data
• Hierarchical code management
• Pattern and co-occurrence queries
• Reliability checks
• Exportable reports and matrices

NVivo workflow

In NVivo, researchers can:

• Import transcripts, PDFs, audio, and social media data
• Create structured codes within a project
• Use coding and matrix queries to explore patterns
• Export visualizations and summaries for reporting

With NVivo, you can keep all your qualitative and mixed methods data in one unified environment—making it easier to reveal patterns, collaborate across teams, and produce rigorous, defensible findings.

ATLAS.ti workflow

ATLAS.ti enables researchers to:

• Create quotations and assign codes directly in documents
• Organize code groups and examine co-occurrence
• Visualize relationships through network diagrams
• Calculate intercoder agreement within the platform

The right tool depends on your collaboration needs, preferred interface, and visualization requirements.

Turn data complexity into clarity

Qualitative content analysis gives you a repeatable, transparent method for transforming raw text into meaningful insight. When paired with purpose-built software, the process becomes even more efficient without sacrificing rigor.

If you’re ready to streamline your coding workflow, unify your data, and uncover deeper insights, Lumivero research software is built to support every stage of your qualitative research process.

Buy NVivo or ATLAS.ti today to start turning data complexity into clarity.