The researcher's guide to life, the universe, and everything

Welcome to our group! This guide will help you understand how we think about research, how we go about doing it, and how we make each other smarter.

Research mentality

Together, our group aims to make each other the best researchers possible, and to constantly learn and adapt. Succeeding in doing research with me is a simple formula: generate many ideas, and channel excitement effectively to execute them.

Generate many ideas

If you trust Nobel Prize winners more than you trust me, try Linus Pauling: "If you want to have good ideas, you must have many ideas." Imagine your own creativity as being normally distributed. If you want to have a killer idea — two or three sigma above the mean — you need to generate enough ideas that the Law of Large Numbers kicks in.

The corollary: do not be critical of your ideas. This is incredibly hard for researchers to do. I have seen graduate students kill their own great insights one too many times. Instead, view it as part of a process. As Ira Glass put it:

"Nobody tells this to people who are beginners, I wish someone told me. All of us who do creative work, we get into it because we have good taste. But there is this gap. For the first couple years you make stuff, it's just not that good. It's trying to be good, it has potential, but it's not. But your taste, the thing that got you into the game, is still killer. And your taste is why your work disappoints you. A lot of people never get past this phase, they quit. Most people I know who do interesting, creative work went through years of this. We know our work doesn't have this special thing that we want it to have. We all go through this. And if you are just starting out or you are still in this phase, you gotta know it's normal and the most important thing you can do is do a lot of work. Put yourself on a deadline so that every week you will finish [something important]. It is only by going through a volume of work that you will close that gap, and your work will be as good as your ambitions. And I took longer to figure out how to do this than anyone I've ever met. It's gonna take awhile. It's normal to take awhile. You've just gotta fight your way through."

I will push us to iterate rapidly. Rather than scoping out a huge project and then digging at it for weeks or months, I will push us to find the core element and prototype it as rapidly as possible.

Channel energy to execute

Amorphous amounts of "hard work" are not what generate impactful results. Instead, it's about bringing energy and excitement to what you do. That means finding problems that you and I think are going to change the world. Harness that energy to drive your research. Be prepared to dig back into that original motivation if you get stuck, and use it to power through. I promise that I will not work with you on any project that I am not ready to dedicate incredible amounts of energy and excitement to, and I ask that you do the same. Be reflective: if you notice yourself slowing down, talk to me! This means that the motivation is slipping, and it usually indicates a problem with how we've oriented the research process, not a problem with you. Tell me in our next meeting, and we will step back and figure out how to change course, together.

Group culture

Our group culture is engaged and positive. Engaged means: we cross paths multiple times per week and work hard to make each other better researchers. Positive means: we frame critiques, questions and suggestions so that the recipient leaves each meeting more excited about their project than when they entered.

Be engaged, be positive. 'Nuff said.

Your time commitments

I take your time very seriously. I ask more structured time commitments of you than many faculty. However, I work hard to organize the commitments so that your time investment brings big benefits to you and to the group. If you feel that an element of the schedule is underperforming, tell me! I am always experimenting.

The weekly schedule you need to commit to:

  1. Flash meetings: Monday and Wednesday 11:30am–noon, Gates 392.
    Informal status meetings and interactive brainstorms.
  2. Project meetings with Michael in Michael's office, Gates 384. This is where we go deep on your project.
    Typical meeting schedule: one long meeting (45min) each week. If you want additional time in a given week, Michael has a 90-minute block he makes available to any project. Grab that week's 90-minute block in exchange for your 45-minute block.
  3. On-demand meetings: if you are making research progress and want to swing something by me between two weekly meetings, feel free to grab any slot on my calendar available at http://hci.st/cal!
  4. HCI lunch: Wednesday noon–1pm, Gates 104. All CS HCI researchers, not just my group. Free lunch!
  5. HCI seminar (academic year only): lunch with the speaker Fridays 11:30–12:20pm in the Gates Library, talk 12:30pm-1:30pm in Gates B01 during the academic year. Have lunch with the speaker! In addition, watch the hci-gates3 list and meet with every speaker who comes through the HCI seminar, even if it's unrelated to your research. This is how you meet the people who will later be talking about your research!

PhD students and rotation students: attend all of the above. Masters students and undergraduates: during the academic year, I understand that sometimes there are class conflicts. So, attend your project meeting, at least one flash meeting each week, and either the HCI lunch or HCI seminar lunch each week during the year. During the summer, attend all of the above.

In addition, I expect you to share your ongoing work at a flash meeting every few weeks. This is a chance for informal feedback. No slides needed!

Getting started

Everyone

If you are a visiting or rotating PhD student, masters student, or undergraduate, make sure you do all of these:

  1. Subscribe to the students-msb@lists.stanford.edu list by filling out this form. This is all of Michael's group members.
  2. Subscribe to the hci-gates3@lists.stanford.edu list by filling out this second form. This list is for all the CS+HCI researchers, not just Michael's group.
  3. Join the Stanford HCI+Graphics Slack org. Make sure you subscribe to the #students-msb, #announcements, #general, and #slack-overflow channels, as well as any channels for your project. Installing the Slack desktop client will make sure you get any notifications. We often use Slack for quick chats and questions.
  4. Subscribe to the Stanford HCI Google Calendar for all lunches, talks and other events. Use the iCal feed to do so. In Google Calendar, here are instructions for adding it; use stanfordhci@gmail.com as the email address.
  5. Request access to the Flash Meeting Agenda. Add yourself to an upcoming agenda to introduce yourself. After that, the expectation is that you'll share informal progress, ideas and frustrations every couple weeks.

PhD students

Rotation students and visiting students: there are a few other perks I'd like to get you set up with. First, the HCI Group has a Dropbox org — if you're going to be aligning with the HCI Group somewhere, ping a faculty member about joining it so you get more space. Second, we have a GitHub org. Ping a more senior PhD student in the group to get added as an admin to our GitHub org. You can use it for your research repos. Third, the faculty here are generally happy to pay for items that make your work environment better. Ergonomics (e.g., chairs, keyboard trays, keyboards) and hardware (e.g., monitors, mice) are fair game. If you need a laptop or machine to work on, also ask for that. Just prep a request list (ideally on Amazon) and let us know.

Masters and undergrads

In addition to the above, to succeed in research, you need to be able to dedicate significant time to it. (See #2: Channel energy to execute.) Each unit at Stanford is roughly three hours of work per week outside of class/meetings. Making this concrete: for my group, you need to be willing to dedicate at least four "units" of time to it in a given quarter. I am very happy to support research for credit if you'd like this reflected in your transcript!

CURIS

All I can add is: the most successful CURIS students do not view themselves as code monkeys. They actively question, contribute, and add their own ideas to the project. You are the most promising student in your cohort; that's why we chose you. Add your voice and energy to the project!

Once you're ready...