Build Themes From Codes

At the end of the last chapter you had something new: a codebook, with a few labels that turned up in more than one account. That is real progress, but a list of codes is not yet meaning. Knowing thatpermission to be a beginnershows up three times tells you an idea recurs; it does not yet tell you what your set of accounts is saying. This chapter is where scattered codes become patterns you can stand behind. It introduces the move at the center of the whole method: building a theme.

What Is the Difference Between a Code and a Theme?

Look back at the coding you did in the last chapter. Three different people, writing about three different hobbies, all landed under the codenot for an audience: the painter who makes work no one will see, the baker who doesn’t care what the family thinks, the writer whose pages no one will read. Separately, each is one person’s remark. Together, they start to say something: that these people value their hobby because no one is watching. Noticing that larger point is the step from coding to theming.

Here is the distinction, held side by side. A code is a short label you attach to a piece of text, close to the ground. A theme is a meaningful pattern you build by grouping several codes, and it says something about the question you are asking. A code points at a line; a theme points at a finding. The named method for building themes this way, from codes up, is called thematic analysis, and it is the beginner-friendly backbone of interpreting a set of accounts.

The word that does the real work in that definition is meaningful. A theme is a pattern of meaning relative to your question, not simply the topic that comes up most often. This is the single most common place beginners slip.

There is a second guard that goes with the first. A theme must be anchored: attached to specific quoted excerpts from more than one account. A pattern you assert but cannot point to is just a hunch, and a pattern that lives in only one account is that one person’s experience, not a theme across your set.

A code names what an idea is in a reusable label. A theme says what a group of those ideas reveals about your question.not for an audienceis a code: it can sit next to any line about hidden work. “The freedom of these hobbies comes from having no audience” is a theme: it interprets what several of those coded lines, taken together, add up to. One labels; the other concludes.

Build a Theme from Your Codes

Theming is a deliberate pass over your codebook, not a flash of insight. Here is the procedure, and you already have everything you need for it: your codebook and the excerpts each code came from.

1. Lay out your codebook. List your codes with the quoted excerpts each one is attached to, so you can see the evidence, not just the labels.

2. Group the codes that point the same way. Look for two or three codes that, taken together, say something about your question.not for an audience,fear of being judged, andprivacy gives freedomclearly lean toward the same idea.

3. Name the pattern as a finding. Write a short phrase that states what the group reveals about your question, not the topic it sits on. Aim for a sentence you could defend, like “the value comes from the absence of an audience.”

4. Anchor the theme in excerpts from more than one account. Attach the specific quoted lines that show it, drawn from at least two different people. If you can only anchor it in one account, it is not yet a theme.

5. Check it against your question. Ask whether the theme actually answers something you set out to understand. If it just restates the topic, push further until it says something.

The discipline lives in steps 3 and 4. Naming the pattern as meaning keeps you from labeling the obvious topic; anchoring across more than one account keeps you honest about whether the pattern is really there.

See a Theme Take Shape

Let’s build one theme, end to end, from the codebook you built in the last chapter. The question that set was gathering meaning on was: what does taking up a creative hobby as an adult give you? Here are some of the codes, with the excerpts they came from.

Step 1 and 2: lay out and group. Reading down the codes, three of them lean the same way:not for an audience,fear of being judged, andprivacy gives freedomall circle the idea of working with no one watching. They come from three different accounts, about three different hobbies. That is a group worth naming.

Step 3: name the pattern as a finding. The lazy label would be “creativity,” or “hobbies,” the topic every account shares. Push past it to what the group actually reveals: for these people, the freedom to make something comes from the absence of an audience. That is a finding. You could state it, and someone could disagree with it, which is exactly what a topic label can never do.

Step 4: anchor it. The theme now travels with its evidence: the painter who can only paint because no one will see (“that’s the only reason I can make them”), the writer who would “start performing” if anyone might read. Two accounts, quoted, pointing the same way. A reader can check the theme against the words.

Step 5: check it against the question. Does “the freedom comes from having no audience” answer what taking up a hobby gives an adult? Yes: it names one specific thing these hobbies give, a private space with no judgment in it. The theme earns its place.

Notice what you did not do. You did not call “creativity” a theme, and you did not build the theme on a single account. You grouped codes, named the meaning, and anchored it across more than one voice. That is thematic analysis at beginner depth, and it is the same move you will make on your own set.

Your Turn!

Now you build a theme yourself, from codes that are already attached for you.

Your scenario. You are still working on the study about what taking up a creative hobby as an adult gives you, and you have coded three more accounts. Below is that slice of your codebook, with the excerpt each code came from. Your job is not to re-code it, but to build one theme from it.

Your codebook slice:

Your task. Build one theme from these codes:

• group the codes that point the same way, and set aside the ones that belong to a different pattern.

• name the theme as a finding about the question, not as the topic everyone shares.

• anchor it in quoted excerpts from more than one account.

Your deliverable. A short theme entry: the theme name, the codes you grouped under it, and the anchoring excerpts (from at least two accounts). One or two sentences saying what the theme reveals.

Let’s Recap!

• A code labels a piece of text; a theme is a meaningful pattern you build by grouping several codes.

• A theme states a finding about your question, not just the topic that everyone in the set happens to share.

• Thematic analysis is the named method for building themes from codes, from the ground up.

• Every theme must be anchored in quoted excerpts from more than one account, or it is a hunch, not a finding.

• Building a theme means grouping codes, naming the pattern as meaning, and pointing to the words that show it.

You can now turn a codebook into themes that say something real about your accounts. But the accounts in a set do not always agree, and in the next chapter you will learn to treat that disagreement not as a mess to tidy away, but as some of the most revealing material you have.

Model Solution

Here is one strong theme built from the codebook slice. Your wording will differ; what matters is that you grouped the right codes, named a finding rather than the topic, and anchored it across more than one account.

Theme:Strangers make room for you before you have earned it.

Codes grouped under it:being expected,welcomed by a stranger,folded into the group.

Anchoring excerpts (three accounts):

• running club: “someone saved me a spot at the start line, like I was expected.”

• life drawing: “A woman my age waved me over the first night, and we’ve sat together every week since.”

• choir: “By December they’d folded me into the group like I’d always been part of it.”

What it reveals: across three different activities, what these adults got was not mainly the skill or the exercise; it was being taken in by people who had no reason to, a sense of belonging offered before they had done anything to deserve it.

What you set aside, and why. The codespermission to be a beginner,unplugged, andfeeling lighterare real, but they point to other patterns (being allowed to be bad at something, escaping the everyday, feeling better), not to being welcomed by strangers. Leaving them out is part of the skill: a theme is a group that coheres, not a bucket for every code in the account.

If you named a finding rather than “creative hobbies” or “community,” grouped the three welcome-related codes, and anchored the theme in at least two accounts, you have the core skill of this chapter: building a theme that says something, and can prove it.