1 / 18

What’s in a Move? Normal Disruption and a Design Challenge

What’s in a Move? Normal Disruption and a Design Challenge. Reza Zadeh Carnegie Mellon University, Language Technology Institute Aruna D. Balakrishnan Carnegie Mellon University , HCII Sara Kiesler Carnegie Mellon University, HCII

maura
Download Presentation

What’s in a Move? Normal Disruption and a Design Challenge

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. What’s in a Move? Normal Disruption and a Design Challenge Reza ZadehCarnegie Mellon University, Language Technology Institute Aruna D. Balakrishnan Carnegie Mellon University, HCII Sara KieslerCarnegie Mellon University, HCII Jonathon N. Cummings Duke University, Fuqua School of Business May 13, 2011

  2. Moving can be difficult.

  3. Moving can spur innovation.

  4. Research questions 1. How likely is a project to have someone who moves? 2. Can we predict who will move? 3. Where do movers go? 4. How disruptive are moves?

  5. Who we studied • 548 projects funded by NSF • Interdisciplinary projects: computer science and other sciences • Projects started from 2000 to 2004 • Most lasted 5 years or longer • Most involved multiple PIs (mean = 4.9, range = 1 to 26) and multiple institutions (mean = 2.3, range = 1 to 13) & how Collected past and current institution information from: Interviews with 55 researchers

  6. 1. How likely is a project to have someone who moves? 33% of projects had at least one mover

  7. A project was more likely to have movers if it had: 1 32 160 more members more universities diversity of university rank

  8. A project is less likely to have movers if it has: 1 $ $ $ 2 Grants 5 more grants PIs have more high ranking universities

  9. 2. Can we predict who will move?

  10. 3. Where do movers go?

  11. 4. How disruptive are moves? surprise &disruption distance invigoration

  12. Moves were surprising& disruptive Two of the initial people left because one of them didn’t get tenured. The other one left for personal reasons. So that created some turmoil in terms of who’s going to do that part of the work. And so I as the PI got a little overwhelmed with doing the individual people’s work as opposed to coordinating it.

  13. Moves created actual & psychological distance [This] guy moved to [new university], and I really don't know if he was involved with the grant after that. Like, I did not have any interaction with him. That's why I'm blanking on his name.

  14. Moves could invigorate projects • [He] relocated… so that sort of extended what would have been a four institution project to a five institution project, and we ended up incorporating his new junior colleague.

  15. Design challenges • Nobody mentioned helpfulness of technology even when probed. • We still need better technology for collaborating over distance and mobility.

  16. Project organization strategies • One of the things that worked really well is the various PIs, co-PIs, had relatively discreet but complementary activities. So there wasn’t a lot of day-to-day interdependence between the projects, which I think works really well in this kind of research.

  17. Technology strategies • Whenever we were co-located, we always did some pair coding. But we also developed ways to do it remotely by having Skype open and then a Unix command called Screen ... when the part of the code that needed to be written was [related to my field of expertise], I would take the keyboard and type and when it was very computer science-y, [my collaborator] would take the keyboard and type. And then the person who is not typing can notice bugs and mistakes and make suggestions. And so it works. It’s a very, very efficient way of working together.

  18. Thank you! • Acknowledgements • National Science Foundation grants SBE-0830306 and OCI-0838385 • IBM Research Fellowship • Our participants for their time and thoughtful responses

More Related