Libby Hemphill research and posts on social media, collaboration, and related technologies

13Oct/090

Twitter network for danah boyd JSB Symposium talk

Today's John Seely Brown Symposium had an active Twitter hashtag of #danahjsb. I imported the hashtag network* into NodeXL and had it draw up a graph for me (click the image for a giant BMP version):

#danahjsb network

#danahjsb network

Image size depends on the user's number of followers. Edge color depends on the kind of edge - yellow indicates a following relationship, blue a reply/mention relationship. Compare our graph to Marc Smith's graph of the #win09 hashtag users:

#win09 network

#win09 network

You'll notice a couple of things. First, Marc is better with NodeXL than I am, and his graph is just easier to read. Then, dig a little deeper and notice that the network of users who used the #danahjsb hashtag is more densely connected. The #win09 network is brokered by the guy in the middle, and the #danahjsb network has no obvious brokers. More to come on my thoughts about the symposium talk and panel, stay tuned.

* only users whose tweets are public are included in these network diagrams

More Info:

What the hashtag?! - view the tweets

Coming Soon - watch the symposium talk and panel

16Sep/090

Building Bridges: A Study of Coordination in Projects

On August 13, I successfully defended my dissertation. Today, I submitted my final, approved version to University of Michigan's institutional repository. That version won't be available until after I receive my degree in December, but you're welcome to read a nearly identical version of my complete dissertation.

Dissertation Abstract
In our efforts to understand how collaborative work can be accomplished, we often turn to discussions of “coordination” for help. However, the concept of coordination is inadequate for explaining the many interdependent processes at work within successful collaborations. In this dissertation, I examined a collaborative construction project – the Woods Avenue Bridge (WAB) Project – with many coordination demands. I used data from this project to develop the concept of adaptive capacity – the set of capabilities a team develops that enable them to adjust to internal and external stresses.

Through analyzing meeting minutes, interview transcripts, and documents the project team developed, I was able to identify behaviors and approaches the team took that may have enabled them to better respond to changes in their environment. I use a specific example of a time when the team successfully redesigned the structure they were building in the field to illustrate the kind of coordination work adaptive capacity enables.

From data about the WAB Project, I identified components of adaptive capacity including perspective taking, multimembership, affect, and social capital. Understanding these components and the adaptive capacity they can develop helps us understand what about a team enables them to accomplish coordination work. Without adaptive capacity, we lack an integrated explanation of the ways in which different components interact and how those components address coordination.

This dissertation contributes to our understanding of how collaborative teams accomplish coordination by refining the concept of adaptive capacity and integrating earlier literatures on coordination, collaboration, and adaptation. The concept of adaptive capacity helps us understand the resources collaborative teams develop that make it possible for them to find flexible and creative solutions to their coordination problems.

1Sep/090

Current Research: Joining Virtual Organizations

People keep asking me what I'm working on now that I've defended my dissertation and moved to Arizona State. The answer is, "research!" More specifically, I'm working on a research project to understand and improve the experience of joining a virtual organization. My colleagues, Erik Johnston and Stephanie Teasley, and I are studying post doctoral researchers who joined (or are joining) virtual science research organizations. I've made a diagram of our research process to make this more clear (click the image for a larger version):
Joining Virtual Organizations Research Project Process

The red parts represent the inductive, qualitative portion of our study. I am primarily responsible for those stages of the project. I am currently collecting data, and that's why that piece looks different. Erik is primarily responsible for the deductive portions, those in blue. This diagram was inspired by process diagrams of grounded theory and deduction from

Gasson, S. (2003) Rigor in Grounded Theory Research: An Interpretive Perspective on Generating Theory from Qualitative Research. In Whitman, M.E. and Woszczynski, A.B., eds. The handbook of information systems research. Hershey, PA: Idea Group.

Gill, J. and Johnson, P. (1997) Research Methods for Managers, 2nd Ed., London: Paul Chapman Publishing.

31Aug/090

Libby the Visiting Scholar

I have joined the faculty of the School of Public Affairs at Arizona State University for the academic calendar year. My office door and email signature now say, "Visiting Scholar." I'm visiting ASU to work with Dr. Erik Johnston on a grant we received from the National Science Foundation last year: Joining Virtual Organizations. I'm conducting interviews and observations with post doctoral researchers and their colleagues in 8 distributed science research projects. Stay tuned for preliminary findings about what post docs experience when joining distributed teams and how distributed teams integrate new members.

Filed under: Academia, Research No Comments
21Aug/090

danah boyd and Panel at JSB Symposium

Each year the School of Information hosts a John Seeley Brown Symposium on Technology and Society, and danah boyd is this year's keynote speaker. John Seeley Brown, Ed Vielmetti, Cliff Lampe, and I will be on a panel following her talk: "Youth-Generated Culture: Growing Up in an Era of Social Media"

JSB Symposium info
Tuesday, October 13
2pm
Blau Auditorium at the Ross School of Business, Tappan and Monroe Streets

30May/094

How To: Styles, Templates, and Quick Styles in Word 2007

I'm using Word 2007 and RefWorks, including the Write-N-Cite III Word plug in. I don't want any crap from you LaTeX users. Yes, I know how to use LaTeX. No, I didn't pick it for my dissertation. Moving on.

Rackham, the graduate school at the University of Michigan, has arcane and ugly formatting requirements that my dissertation must meet in order for me to receive my degree. They will not let me graduate if my margins or headers are wrong. That's pretty compelling incentive to get my formatting right. Using the excellent "Using Word 2007 for Your Dissertation" guide provided by the University Library's Knowledge Navigation Center as a starting point, I set off to make sure Word would format my dissertation correctly.

The keys to making your formatting life easy with Word are styles and templates. You can learn more about both at Microsoft's site. I'm a faithful style user, and I assume you can easily become one if you aren't already. All text in my documents is associated with some style - e.g., Normal, Heading 1, Long Quote. You need not worry about the specifics of a style while you write - just make sure all your text is associated with a style. Word does much of that automatically. Once you're done writing and ready to format, you should first open a new blank document and create a template.

Creating a Template

The real purpose of your template is to store the formatting rules you assign to all your different styles. Your template need not have any content, but I find it helpful to write a little something so I can at least see my style changes in action. To create a template, you need to edit the styles so they match your formatting rules and then save the document as a template (*.dotx) instead of a regular document.

Attaching Templates to Files

Once you have defined all your styles and formatting rules in a template, you need to attach the template to your Word document. In Word 2007,

  1. Go to the Office button
  2. Choose "Word Options" from the bottom
  3. Choose "Add Ins" from the side menu
  4. Choose "Templates" from the Manage drop down at the bottom
  5. Click "Go..."
  6. Click "Attach" and navigate to the template file you just created and saved
  7. Make sure "Automatically update document styles" is selected
  8. Click "Ok"

You should see your document change to reflect the formatting rules in your template.

Using Quick Styles

One of my favorite features of Word 2007 is the Quick Styles feature. Quick Styles let you save template rules so they are accessible from the "Change Styles" menu on the Home ribbon. To get your formatting rules into a Quick Style, essentially saving you the hassle of attaching a template:

  1. Open your template file
  2. Click "Change styles" on the Home ribbon
  3. Choose "Style set" and then "Save as Quick Style Set..."
  4. Give your set a name you'll remember and click "Save"

Now, you can apply your template's rules in any document right from the Quick Style menu by click "Change Styles", then "Style Set," and choosing the name you gave your set.

Notes

I wrote this post in part to remind myself of the steps involved. Styles and templates can make working in Word incredibly easy, but you absolutely must always use styles to format your text. If you make changes by hand (e.g., clicking Ctrl+B to make something bold), you'll screw the whole process up. Only when used together (and exclusively) will styles and templates make your writing life easier.

Office 2008 for Mac can do the styles and templates stuff but does not have a useful Quick Styles feature. To attach a template to a document in Office 2008 for Mac:

  1. Open the "Tools" menu
  2. Choose "Templates and Add Ins..."
  3. Click "Attach" and navigate to the template document you created
  4. Make sure "Automatically update document styles" is selected
  5. Click "Ok"

If you're using RefWorks, you should use either Word 2007 or Word 2008 but not both. RefWorks gets confused when you try to add or edit citations with both programs. I do most of my writing in Word 2007 on a virtual machine running Windows 7. I occasionally make edits using Word 2008 natively on my Mac, but I do not make changes to citations in both programs.

Filed under: Technology, Writing 4 Comments
5Apr/090

Why else might RWW be right about Skype?

Bernard Lund wrote a column (article?) for ReadWriteWeb recently that listed 10 reasons Skype is the biggest Web 2.0 winner. "Web 2.0" doesn't even make sense anymore, but let's set that aside. Lund's article is interesting even without the "Web 2.0" buzzword. For instance, he points out that Skype is profitable. Profitable is surely something winners are, right? What he leaves out, though, is even more interesting.

Skype's core business is about connecting people. Unlike Facebook and Twitter, where connections have become almost a side effect of advertising and broadcasting our every thought, when we use Skype, we do so to make a real, timely, engaged connection with another person (or group). Maybe the lesson Skype has to teach us is not that telecom companies are bad but that Web 2.0 companies who don't help us connect to each other, not just us to advertisers, aren't where the money is. At least, I can hope that's part of the lesson.

30Mar/093

Academic writers cannot get writer’s block

At least, that's what Paul J. Silvia, author of How to Write a Lot: A Practical Guide to Productive Academic Writing claims. I'm inclined to believe him. Writer's block seems bogus for us.

I've been reading books on writing while taking breaks from my ever-growing dissertation. Today I read a little of the Howard Becker Gem Writing for Social Scientists: How to Start and Finish Your Thesis, Book, or Article and most of Silvia's book. Here are a couple gems from Silvia's book:

Academic writers cannot get writer’s block. Don’t confuse yourself with your friends teaching creative writing in the fine arts department. You’re not crafting a deep narrative or composing metaphors that expose mysteries of the human heart. The subtlety of your analysis of variance will not move readers to tears, although the tediousness of it might…Novelists and poets are the landscape artists and portrait painters; academic writers are the people with big paint sprayers who repaint your basement. (p. 45)

and

Like their dislike of jocks and the yearbook club, many writers’ distrust of semicolons is a prejudice from high school. … While you’re rebuilding your relationship with the semicolon, reach out and make a new friend – the dash. Good writers are addicted to dashes. (p. 67-68)

I'm proud to say that I a) do not have writer's block and b) use both semicolons and dashes often and appropriately. I have trouble sticking to a writing schedule as Silvia (and many, many other writing guide authors) recommend, but at least I've mastered the dash.

Filed under: Academia, Writing 3 Comments
27Mar/090

The Wrongheadedness of Best Practice Thinking

I’ve come across a gem of a book introduction, and I’m writing to recommend that you read it. Yes, all of you. The introduction is from the book Strategic Procurement in Construction by Andrew Cox and Mike Townsend, published in 1998. The shelves of bookstores are crowded with advice for practitioners and business owners about the latest “best practices” for their business or for business in general. I have contributed to the best practice literature myself, trying to make my onboarding research findings accessible and interesting. I’ve been troubled by the literature before; something about the idea of a “best practice” made me wary, much like a “Truth” did when I spent more time with philosophy. I noticed this frustration most acutely when teaching master’s students in a professional degree program. So many students demanded that I teach them best practices, that I tell them what to do in their next job. I tried to explain to students that I was helping them acquire new tools for meeting the challenges information professionals face, not giving them step-by-step instructions for how to do their eventual jobs.

Cox and Townsend argue in their introduction, and throughout the book, that best practice thinking is wrong-headed and leaves us playing catch up. One of my favorite bits of the introduction reads:

They will be searching for the ‘Holy Grail’ of best practice. By this one means practitioners are looking for the answer that provides the solution to all of the problems which they face managerially. Unfortunately, this desire to discover the single solution (best practice), that will allow the practitioner to avoid the need for thought and risk taking, is an illusion.

They go on to discuss concepts such as appropriateness and leverage and recognize that many practitioners would call their discussions “common sense.” Their response?

Some of the practitioners who read these pages may accept what has been said, and argue that this is just common sense (which it is), and that they already know this. If that is the case then this book may have little to teach them, however, because experience leads the authors to conclude that such a form of sense (in a business context) does not appear to be all that common.

I wish I’d written something like that in the paper Andy and I submitted recently that was rejected for having results that were not surprising enough. The results we found in our onboarding study were surprising because we found them and not necessarily in their content. For instance, it’s surprising that teams still behave as though new employees will be immediately productive even though the sense that onboarding takes time is apparently common. Much like Cox and Townsend find that strategic procurement is not all that common, neither are teams who smoothly onboard their new members.

My questions as I continue to read Cox and Townsend’s book are really about how one encourages strategic, reflective thinking over best practice thinking and how one should present research results that show just how uncommon common sense can be. See, one can learn things by studying construction projects. This message brought to you by my dissertation, a work in progress.