Month: November 2016

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.

No Slacking November


img_5183November is here, and that means two things: it’s almost the holidays(!!!!) and it’s almost time for everything that I have been working on (or not) throughout this semester to be due. Though I am delighted by the prospect of having a month off from school, I know that getting to that point will be no walk in the park.

Throughout this month, I will continue to work on my grad school applications, as well as writing the beginning sections of my final thesis paper. Though both of these tasks are not only very important, but also very time consuming, I must admit that I have fallen prey to the temptation of procrastination. However, now that I only have a month to finish everything, it’s go time. I have always told myself that I work well under pressure, and this month will be the ultimate test of that. Though, as usual, I am worried, I am confident that I will get everything done with the help of my advisor, family, and friends.

Luckily, the beginning of November brought me more than just a reality check. I just recently received data back from the soft launch of my study, and everything seems to be going well! Though the soft launch data only contained data from 12 participants, it provided a final opportunity for edits. In our piloting phase, we were focused on making changes to the study based on flaws in the design, questions, etc. However, this data allows us to make changes based on actual participant responses. I will be presenting my study to the entire Relationships Lab this Friday, and, after getting some final feedback from my colleagues, I should be ready to fully launch the study! Thankfully, data analysis isn’t in my plan until next semester. So, once the study is fully launched, I can keep focus on my current tasks, and just wait until the data is sent back to me.