Optimizing Team Performance: Collaborative Virtual Writing

Optimizing Team Performance: Collaborative Virtual Writing

Charlotte Robidoux (Hewlett-Packard Company, USA)
DOI: 10.4018/978-1-60566-994-6.ch010
OnDemand PDF Download:
$37.50

Abstract

Increasingly, collaborative writing occurs in distributed work environments. Collaboration is essential for technical writing teams that develop and share, or single source, content using content management system (CMS) technology. Technical writers must be proficient not only in developing content that can be shared but also in carrying out complex writing tasks virtually. However, research indicates that asynchronous-distributed collaborative writing can lead to productivity losses unless teams implement explicit processes for interacting and using computer-mediated communication (CMC) technology. With highly structured processes to guide their efforts, teams are more likely to see productivity gains. To achieve these gains, effective collaboration must address six key areas: (1) targets to guide team performance, (2) assessments of collaborative writing skills in virtual teams, (3) role delineation, (4) process scripts to promote efficient virtual collaborative writing, (5) a training framework, and (6) performance measurements and a recognition framework for reinforcing team accomplishments. Organizations must be willing to create a culture that supports a team environment committed to these specific areas. This chapter explores how to establish an infrastructure that promotes collaborative writing efficiency in virtual settings.
Chapter Preview
Top

Introduction

An Unplanned Collaboration

Consider a team of four writers who have worked together successfully for a few years, revising a set of documents for a well-established computer product. When the documentation is ready to be revised, each team member ensures that the book she has been assigned is updated to reflect new or changed product features. In this scenario, the writers are able to revise the documentation efficiently. Now imagine what would happen if the process for making updates changes dramatically, and only one writer fully understands the new process. Under these circumstances, the chance for success could diminish rapidly depending on the team’s ability to learn and adapt to unfamiliar tasks and to redefine their interactions with each other. That is, team members could flounder when the writers do not have an expected set of assignments and a defined approach to revising content. They could waste time trying to carry out tasks that other writers might have implemented or disrupt each other by trying to carry out the same tasks.

A scenario like this overwhelmed a team of Hewlett-Packard Company (HP) writers, who unexpectedly were forced to update individual chunks of content that would become the source material for a set of documents. Team members working in different locations were required to work collaboratively when one team member prematurely divided whole books into small, modular pieces of content that then could be reused, or single sourced, across the documentation set. While this writer thought she would improve the efficiency and quality of the content by making this change, she did not realize how difficult it would be for the team of writers to learn how to collaborate with one another under these circumstances, how to coordinate an effective flow of tasks, and how to adjust to an entirely new process. She made decisions about how the content would be updated as if she were working on her own and without understanding the consequences for the team at the point when the content would be shared. The consequence of this decision for the rest of this team was that the once-familiar experience of a single writer owning and updating a complete book would not be possible.

Although sharing reusable pieces of content had been a goal for HP writing teams, plunging a team without preparation into the process of reusing topics in different books was never the intent. In the end, the writers could not adapt quickly enough, and the only way to avoid delaying the shipment of the product was for the content management administrator to reverse the writer’s actions—to unlink the referenced topics and embed them into separate books.

This scenario revealed important information about the nature of collaboration. While teams of writers working in the book paradigm collaborate with each other, the type of collaboration employed typically is serial or parallel collaboration, not collective collaboration as described earlier in this volume. The experience also underscores the need to establish an environment that enables writers to collaborate collectively within distributed work settings. This type of environment must provide explicit, scripted processes to address the unique challenges faced by virtual collaborative writing teams.

Complete Chapter List

Search this Book:
Reset