Part 8: Coding Between the Lines

For the most part, my research has reached a pleasant stasis since my last blog post. A team of experimenters and I have been running sessions every week and slowly but surely collecting data.

That being said, I’m still working on new things. I am now working on a new part of data collection/analysis: coding response data. (I know this is CMU, but no, not programming coding.) A section in my study is where participants write about whether they made a sacrifice for their partner and what their motives were for their actions. My focus is on whether they had intrinsic motivation, but I am also assessing other types of motives to see how they all relate with each other and fit with the literature’s findings. Now we have to take the participants’ responses and code them for what kinds of motivations appear so we can see what kinds of motivation touch promotes.

Unfortunately, no one has released a standardized coding scheme for motivation for writing responses. Researchers have come up with definitions and methods to categorize behaviors as certain types of motives, but no one has implemented a way for how these motivations would manifest in writing. Thus I have to work from scratch. I started with the basic definition of each motivation and then thought about how these would play out in responses. For example, intrinsic motivation is about doing an activity because you truly want to do that activity, such as doing something out of enjoyment or interest. A phrase such as “I wanted to help my partner” would be coded high on intrinsic motivation because phrases like “I want” indicate that the participant truly wanted to make a sacrifice.


Fun fact: 90% of my life is just editing

Of course, there’s always the danger of reading too much into what a participant wrote or making too many leaps of inference. That’s why it’s important for coders to give higher ratings for statements that are explicit and clear and to not overthink ambiguous statements. For now, I am working with my advisor to work out the kinks of how to code these responses and how to make it easy and clear for new coders to learn. We should be able to have a workable coding scheme come January.