There were a lot of sticky notes involved in figuring out my next research agenda. Luckily, I got great help at DSST!
Recently, I had an amazing opportunity to attend the DSST (Digital Societies and Social Technologies) Summer Institute in College Park, MD. DSST brings together junior (e.g., postdoc, pre-tenure faculty) and established researchers from fields like Computer Science, HCI, Social Informatics, Information Science, Sociology, Anthropology, STS, and more. While there, I participated in workshops, got more familiar with methods used in other fields, and got a lot of great tips on articulating my research agenda (this is frequently a struggle for me because I have such broad research interests).
In small groups, we mapped out the research space of DSST, focusing on how we fit into the picture of a research area that encompasses so many different communities and venues. Interdisciplinarity is not for the weak!
There is so much I could write about this event, but there is one particular issue that resonated in multiple presentations, workshops, and offline discussions — the issue of vocabulary. It seems to me, that the biggest problems in interdisciplinary work arise not when we don’t know the words the other person is using but when we use the same words in different way. Here are a few examples:
- Problem: In Computer Science, this term often means “research challenge,” as in “I’m working on the problem of how to connect parents and children who live apart.” However, in some Social Science domains the word “problem” may be reserved for situations that are broken or non-normative. In other words, “connecting parents and children” is not a problem to solve — I might be supporting families in facing the challenge of separation, but I’m not fixing something that is broken. In some ways, using the word “problem” takes agency away from the people we am trying to support, instead positioning the designer as “the fixer.” Usually, this is not what people who build systems actually mean. This is a loaded term and might be better avoided or replaced with “challenge.”
- Theory: In Computer Science, this term often refers to the study of abstract constructs like Algorithms and Data Structures and frequently developed through mathematical proofs. In the Social Sciences, there are many types of theories serving different functions (my favorite reading on this is Halverston’s “What Does CSCW Need to DO with Theories?”). Theories are frequently heuristics used to understand and discuss empirical data and may or may not need to have strong predictive power. My personal observation is that theorists of both sorts have keen minds and a love for an elegant explanation and can become great friends once the vocabulary issues can be resolved.
- System: In Computer Science, “system” usually refers to a set of software and hardware that performs a specific function. At DSST, it was more frequently expanded and used to refer not just to the software and hardware but also to the people, practices, and ecosystems around the use of that particular tool.
- Ethnography: I’ve heard builders use this terms to refer to any sort of formative work that involves observing and talking to users. Not surprisingly, people who are trained as ethnographers might see this as an over-simplification. It’s hard to put the same label on a single week of observation versus two years of being embedded in a particular setting. Perhaps, rather than using the loaded term, it might make more sense to refer to specific methods used such as “two weeks of participatory observation” and “contextualized interviews.”
- Social Computing: This is a slippery terms, because we are all still trying to figure out what it means. This area is at the intersection of social science and computational systems, but what is included or excluded? As I spoke to people at the workshop, many equated Social Computing with either large-scale social network analysis (e.g., “we looked at 3 mill Tweets”) or Crowdsourcing (e.g., “we leveraged the crowd to do citizen science”). I was happy to provide a third possibility that I believe should be included in the definition: mediated communication for supporting one-to-one and small-group relationships. I hope that we continue to include things like videochat, ShareTable, haptic connectedness devices, small online support groups, etc. in our definitions and investigations of Social Computing.
In industry, most of our work happens in interdisciplinary groups. This kind of reflection has helped me understand why at times I have had trouble explaining my work or outlook to somebody from a different background, like formal methods or software engineering. DSST reminded me the importance of establishing a common ground and a common vocabulary in any work that brings together diverse disciplines.
At CHI 2013, I attended and helped organize a workshop on Designing for Diverse Families. I’ve been meaning to blog about it for the past two months and recently reconnecting with one of the other organizers has given me the push that I needed. I want to tell you about one discussion that we are hoping to turn into an actual project. I also want to invite both workshop participants and readers who find this to be a compelling idea to potentially join in on this project.
The goal of the workshop was to better understand our own assumptions about what constitutes a “family,” understand the gaps in our own work, and see how we can be more inclusive as a community. The variety of projects presented really highlighted how different families can be in terms of structure, practices, values, and culture. While this diversity can make it very difficult to design for families, it is also an incredible resource. At a time when many parents experience a great deal of anxiety about “parenting right” and face conflicting seemingly authoritative sources on doing it this way or that way, it can be valuable to show that there are many ways to be a parent. Things that are assumed to be true in one culture, can be unheard of in another, but nonetheless children grow up and succeed. My favorite idea that came out this workshop is that getting a perspective from a different culture on specific parenting questions can be of benefit to many families. Basically, we want a parent to be able to ask “how do other families do this?” when faced with everyday worries such as when to introduce particular foods, how to sleep train a child, how to deal with an unruly teenager, etc. Presenting these answers in the context of their originating geography can help bring home the idea that there is no single right way of dealing with most of these questions, but rather many approaches that can be successful.
So, a few of us would actually like to make this happen! Here’s the basic sketch of a plan:
- We populate the initial list of questions and answers using Yahoo answers
- We continue getting answers to common questions by selectively using Mechanical Turk, tracking the geographic locations of the Turkers
- We allow users to ask questions of the community and see a selection of answers from different parts of the world displayed on a map
- Users are encouraged to give their own answer to another question when they see answers to their own
Obviously, it’s fairly rough at this stage, which is why I’m reaching out to y’all. So for the parents out there, would this be useful for you? For the builders out there, would you be interested in getting involved in making this happen? For the researchers out there, would you be interested in getting on board or just giving advice? If you are interested in being a co-investigator, please fill out this survey to let us know what you’d like to do and we can start getting a plan together!
One of my favorite conferences, Interaction Design and Children (IDC) is going to be in NYC this year! Full papers are called for on January 22nd and I hope to see a lot of great stuff this year (definitely excited about the paper I will be submitting ). In the meantime, I wanted to reflect on some of my favorite IDC papers of all time. These are the ones that have directly influenced my own work and I wanted to share them with others who are interested in family communication technologies.
The first paper is about Mediated Intimacy in Families and it is a qualitative investigation of how parents and children build closeness. Dalsgaard et al. emphasize the importance of emotional and physical expressiveness in all relationships. But they also found differences: parents and children build closeness through play together and care provided by the parent for the child, rather than through reciprocal exchanges and setting of public and private boundaries (as in strong-tie relationship). These insights led quite directly to the work that I’ve done with the ShareTable, where my goal was supporting the kinds of care and play activities that might be done remotely.
Freed et al. used a doll house to investigate how children think about remote communication. This image is from their paper and belongs to the authors.
The second paper is about children connecting with peers through tangible characters in doll houses. Freed et al. built a pair of doll houses where toys could call each other, mail letters, and videochat with each other. This is a cool idea and an interesting way of investigating how children think about remote communication. The dollhouse approach turned out to be quite compelling to the kids, with most of them engaging in some level of shared play and finding the experience engaging. I had already been engaging with the idea of communicating through play, but seeing this work eventually inspired me to think about physical arrangements for videochat that could support narrative and pretend play.
Raffle et al. investigated asynchronous messaging with toddlers. This image is from their paper and belongs to the authors.
The last paper is about asynchronous messaging with preschoolers. If you had asked me before this paper was published whether I thought that asynchronous communication with toddlers would work, I would probably have been very dubious. It’s just not that easy to communicate remotely and it seems much easier to connect with a person than with a message! I have to say that this paper has changed my mind. It presents three prototypes for asynchronous contact that thoughtfully explore what it may look like to engage toddlers with remote relatives asynchronously. This hasn’t led me to do a new paper or a new project (yet), but it reminded me not to underestimate the power of creative ideas and the ability of children to adapt to new ways of connecting.
If you like these papers, you might thing about checking out IDC in NYC this year. I’ll definitely be there, so let me know if you want to meet up.