Site Logo
Research MethodsThematic Analysis

Latent Coding: interpreting the meaning beneath the words

Evidano6 min read

Latent coding analyses what the data mean rather than what they say: the assumptions, conceptualisations, and ideologies that structure the explicit content without being stated in it. When a manager describes layoffs as “letting people go”, semantic coding records a termination account; latent coding notices the grammar of release — as if departure were the employees’ trajectory and the organisation merely unclenched. Working at this level is interpretive by definition, which raises the evidentiary stakes rather than lowering them: a latent theme is a claim about something participants did not say, and it earns its place only through patterned, demonstrable traces in what they did say.

What latent coding actually codes

Framings and metaphors: the recurring figurative structures through which a topic is thought — illness as battle, customers as traffic, time as debt.

Presuppositions: what utterances take for granted — “even the night staff were consulted” presupposes a hierarchy of consultation-worthiness nobody asserted.

Absences and euphemisms: what is systematically unsaid, renamed, or passed over, detectable only against the corpus’s pattern.

Subject positions: who speakers cast themselves and others as — expert, victim, realist — beneath the propositional content.

In Braun and Clarke’s framework this is the latent level of theme development; in content analysis, Graneheim and Lundman’s “latent content”. Both traditions insist on the same discipline: the underlying meaning must be argued from textual evidence, not intuited past it.

The sources that define the level

Braun and Clarke’s Using thematic analysis in psychology distinguishes semantic from latent themes and ties the latent level to constructionist framings — the analysis examines the ideas and assumptions that shape the semantic content.

Graneheim and Lundman’s Qualitative content analysis in nursing research frames latent content as the interpreted, underlying meaning of text, and supplies the quality vocabulary — credibility, dependability, transferability — that latent claims are judged by.

For the interpretive craft itself, the discourse-analytic tradition is the deep well: latent coding borrows its attention to what language does while remaining within a thematic architecture.

When to code latently

  • When the question concerns assumptions rather than reports: how do clinicians conceptualise “difficult” patients? what does “merit” mean inside this hiring process?
  • When the surface is known to be curated — stigmatised topics, institutional talk, anywhere impression management is structural.
  • When semantic results keep converging on something unexplained: surface themes that co-occur oddly are often one latent structure wearing several outfits.
  • Not for questions stakeholders must audit line-by-line — latent findings are arguable interpretations, and a programme board wanting verifiable barriers should get semantic analysis.
  • Not without interpretive resources. Latent coding needs a theoretical sensibility to interpret with; run bare, it produces free association.

A discipline for interpretation

State the interpretive lens

Latent analysis always interprets from somewhere — a theory of stigma, a concept of institutional talk, a feminist reading. Name it. The lens is what makes the interpretation examinable rather than oracular.

Code traces, not conclusions

First-pass latent codes should name observable textual features — “release metaphors”, “agentless constructions for errors”, “consultation presupposes rank” — kept close enough to the text that another analyst can find the instances.

Require pattern before theme

A latent theme needs recurrence across data items and speakers, with the trace codes as its evidence base. One arresting metaphor is a quotation; a structure of meaning appears as distribution.

Hunt the counter-evidence deliberately

Search for data that resist the reading — participants who name the assumption, passages where the framing breaks. What survives the hunt is stronger; what does not, was projection.

Write claims with their warrant attached

Every latent theme in the report carries its trace evidence and its lens: “read through X, these patterns indicate Y”. The reader should be able to disagree at a specific step, which is what separates interpretation from assertion.

Worked example: “resilience” in a public-sector staff survey

An organisation asked why burnout persisted despite a celebrated wellbeing programme. Semantic analysis of 300 staff comments had already listed workload, staffing, and “resilience training fatigue”; the latent pass asked what conceptions of responsibility structured the talk.

Trace coding found three recurrent patterns: workload appeared overwhelmingly in agentless grammar (“the demands have grown” — no one demanding); wellbeing appeared as personal inventory (“my resilience”, “top up my reserves”), a possession employees carry rather than a condition work produces; and management appeared as weather — anticipated, endured, never addressed as decision-makers (“when the restructures blow through”). Counter-evidence was hunted and found bounded: union representatives’ comments broke all three patterns, naming actors and decisions — the exception that displayed the rule’s reach.

The latent theme — responsibility privatised: the corpus conceptualises wellbeing as an individual asset depleted by an agentless environment — was reported with its lens (a governmentality reading), its trace distributions, and the union counter-case. The practical upshot differed sharply from the semantic report’s: not more resilience sessions, but the finding that the programme’s own language taught staff to blame their reserves. The organisation rewrote its wellbeing communications; that is what latent analysis is for.

Common mistakes

  • Interpretation without traces. Themes announced from analytic authority, with quotes as decoration rather than evidence — the failure that discredits the level.
  • Semantic themes with latent titles. Renaming “staff report high workload” as “discourses of overwork” changes the register, not the analysis.
  • One lens applied as truth. Reporting the reading as what the data “really mean”, rather than as an interpretation from a named position.
  • Ignoring reflexivity. The analyst’s own categories are part of the instrument at this level; a latent analysis with no reflexive account is missing a methods component.
  • Depth as a status move. Choosing latent because it sounds more sophisticated, on a question the surface would have answered — the commonest and least admitted error.

Limitations

Latent findings are constitutively contestable: different lenses yield different readings of the same corpus, and the method’s integrity lies in making the contest possible, not in winning it by fiat.

Reliability tools lose purchase — inter-coder agreement on interpretations of the unsaid is neither achievable nor, in the reflexive traditions, sought. Quality shifts to credibility: trace evidence, counter-evidence handling, and the coherence of the interpretive chain.

And the level tempts overreach into minds and motives. Latent coding licenses claims about meaning structures in the data; it does not license psychoanalysis of participants, and write-ups that slide from “the talk assumes” to “they secretly believe” have left the method.

Where software helps

The trace layer is where tooling contributes: finding every agentless construction around “workload”, every possessive framing of wellbeing, across 300 comments is retrieval-and-coding work, and Evidano handles it with each coded trace linked to its passage — so the distribution a latent theme rests on is demonstrable, and the counter-evidence hunt is a search rather than a hope. Semantic first passes to organise the corpus come cheap the same way.

The interpretation is not delegable, and this is a design fact rather than a disclaimer: a model can surface candidate patterns in the said; deciding what unsaid structure they evidence — through which lens, against which counter-readings — is the analyst’s argument to make and defend.

Topics

  • latent coding
  • latent content
  • latent vs manifest content
  • interpretive coding
  • underlying meaning
  • thematic analysis
  • implicit assumptions

Other methods in thematic analysis

Written guides are linked directly; the rest have a reference entry in the methodology directory.

Published research using these methods

Studies and evaluations where this family of method was applied with Evidano — the work, not the claim.

Keep reading

Browse all articles