In public health, we often come to an analysis project with deductive themes in mind. This is natural, since our studies typically begin with specific objectives and aims which are guided by theory and prior research. Even when the theme is identified deductively though, I would argue that your code definition will usually evolve as you interact with the data, such that the definition was developed inductively. Let's go back to the story, Awkward Lunch. You've already written memos on this story and I've read it a few times. An obvious theme in this story is immigration, but there are many different ways we could define a code for immigration. One approach might be to focus on the physical act of moving from one country to another. In this set of stories, however, we're looking at stories of being in between, and I think that focusing on the physical move would not capture other aspects of the immigration experience. For the author of Awkward Lunch, immigration meant feeling isolated from his peers, needing to adjust to all kinds of new things, and relying on friends to help stabilize his daily experience. So let's try defining a code named "immigration experience". In the code system window, click on the little green label icon with the plus sign and enter "immigration experience" as the code name. Then type the definition. This code captures all references to moving from one country to another, including emotions related to feeling foreign or otherwise different, difficulties adapting to new society or culture, and connecting to new social networks. When you close that box, you'll see that the code definition appears as a memo next to the code. Like the memos we worked with earlier, if you hover your mouse over the memo, you'll get a preview of the content of the memo, most likely the entire definition, unless it's particularly long. Now, go through the story again and create segments that you think fit the code definition and apply the code by dragging and dropping it onto the segment. Remember, you can also drag and drop the segment onto the code. A coding strip will appear next to the text along with the name of the code. For practice, I'd like to ask you to apply this code to Awkward Lunch and then Desi. Keep track of your thoughts or questions about the definition and memos as you move through Desi. This is an example of when you might want to flag these memos as being different from the memos you wrote earlier. In the first paragraph of Desi, for instance, there's a reference to what seems to be her parents migration to the US, but it's indirect and doesn't really describe the experience. I'll write a memo to capture this thought and I'll click on the memo icon with a question mark on it. I can also link the memo to the code by clicking on the link code icon at the top of the memo window and selecting the code I want to link. Once you've linked the memos where you kept track of challenges you experienced while coding to the code in question, you can go back and review those memos by right-clicking on the code name and selecting linked memos. This will bring up a table with all the memos you linked to the code immigration experience, where each row represents one memo. If you click on one of the rows, you'll be able to view what you wrote in the white space above. This is a great way to keep track of your evolving thoughts on your codes and definitions. I always recommend trying to apply a code to a few documents, keeping track of questions, doubts, and challenges, and then coming back to the definition to revise. Once you've revised the definition, try the new code and definition on a few more documents and see if you encounter more questions or challenges. This is how you will work to develop inductive code definitions, even when the codes themselves were identified deductively.