It’s the Communication, Stupid: Lessons in Communication-Driven Product Development  

Changes in software design and development are creating new opportunities for technical communicators at DDS. Writers have become an integral part of product teams, evaluated on their ability to help get products out the door. In some cases writers’ deliverables have themselves become full software development projects. As technical writers take on new roles they’re getting increased visibility, more interesting and varied work and a chance to move up ladders outside of the traditional technical writing group.

Dykstra, Peter. STC Proceedings (2000). Articles>Communication>Collaboration

An Iterative Approach to Better Working Relationships

Discover creative solutions to inter-personal problems in the workplace using an iterative approach: observation of moment-to-moment interactions to assess the effectiveness of our responses. We will present six options for resolving conflicts, clarifying when and how to use each through case studies, work in small groups, and simulations.

Ziff, Joel D. Usability Professionals Association (2004). Presentations>Collaboration

Journal of Computer Mediated Communication

A journal which publishes research into CMC.

JCMC. Journals>Human Computer Interaction>Communication>Collaboration

Just a Cog in the Machine? Implications for Technical Communicators

This article explores the implications of choosing to work as a cog in the field of technical communication. The author includes perspectives from cog-colleagues and manager/cogs, and touches on concepts of ownership, recognition, and egoless communication. She recommends exercises in discipline-specific poetry and editing in a workshop setting as practical ways to work toward detachment.

MacQueen, Lisa Clare. Orange Journal, The (2002). Articles>TC>Collaboration

"Just the Boys Playing on Computers": An Activity Theory Analysis of Differences in the Cultures of Two Engineering Firms      

Using activity theory as a supplement to genre studies, this article explores a case of the disintegration of a traditional engineering firm. It focuses on the causes of such disintegration and the role of different types of communication in serving as sites where contradictions can be brought to visibility and resolution. The authors' goal is both to show the power of activity theory in illuminating issues of tension, contradiction, and dissonance that lead to the breakup of the original organization into two separate firms and point to fundamental differences in the cultures of traditional engineering firms and software design enterprises.

Artemeva, Natasha and Aviva Freedman. Journal of Business and Technical Communication (2001). Articles>Collaboration>Engineering

Keep Pesky Business Types at Bay by Focusing on the Strategic Goal  

If you have ever been forced to deal with business types who have no technical know-how, then you know how these types can work against IT's progress. Here's how to improve your business/IT communication by concentrating on the strategic goals.

Hardin, Ken. TechRepublic (2003). Careers>Business Communication>Project Management>Collaboration

Keeping In Touch--Staying Online  

As technical communicators, we need to reach out and 'keep in touch' with customers if we want to provide truly user-friendly documentation. If we include our customers in the document development process, and convince them that they are an integral part of that process, we increase customer satisfaction. In this panel, writers will discuss practical, step-by-step approaches they use to gather customer comments.

Jacobowitz, Barbara E. and Peggy A. Yates. STC Proceedings (1994). Articles>Collaboration>Correspondence

Key Content: Developing a Personal Tagline

It is a helpful exercise to develop a tagline for yourself, in the same way that professionals in a previous generation were encouraged to develop a mission statement. With shortening attention spans, today's professional needs only a few-word tagline to fit in the sound bite of management's smaller time slots.

Albing, Bill. Carolina Communique (2007). Careers>Portfolios>Workplace>Collaboration

Key Open Source "Best Practices" Supported in the Tigris Project

Software developers spend a large part of their time communicating with each other.  Clear and effective technical communications are needed to keep the team in synch and to allow individuals with key knowledge to apply that knowledge where it is needed. One tenet of the open source community is that techincal communications should take place in public forums.   Mailing lists are the backbone of open source communications.  Beyond that, open source projects need support for precisely communicating technical details and for group decision-making.

Tigris (1994). Articles>Collaboration>Open Source

The Knowledge Editor(SM): Innovative Editorial Solutions to Meet Your Quality Objectives  

This paper represents over 30 years cumulative work experience, as both corporate staff members and as consultants, and shares recommendations for providing highly valuable editorial contributions. The authors also introduce a new concept for innovative editorial methods that meet the technological and productivity challenges facing today’s information design organizations.

Holland, Mary T. and Kristen Sutton. STC Proceedings (2002). Articles>Editing>Collaboration

Knowledge Management: The Collaboration Thread

Knowledge management is a thick web of themes from a variety of professional disciplines. The field is populated with people who resonate with the ideas first articulated by Larry Prusak and Tom Davenport, Tom Stewart, Carla O'Dell and others. "Getting the right information to the right people at the right time." Isn't that what information architecture and the information sciences are all about? "Leveraging the intellectual capital of the organization." Isn't that HR turf? "Harvest and refine reusable intellectual artifacts." Hello? Are there any technical writers out there? "It's about connecting people with people and supporting them with technology." Does anybody know that research in computer-supported cooperative work began in 1984?

Anklam, Patti. ASIST (2002). Articles>Knowledge Management>Collaboration

A Lack of Coordination is Why Technical Support Isn't Working  

Technical support relies heavily on users' abilities to perform tasks, and we're all more than familiar with the difficulty involved with assisting inexperienced computer users. Most widespread worms and viruses take hold and spread due to poorly maintained systems, commonly home systems found on broadband networks.

Yarden, Jonathan. TechRepublic (2003). Articles>Business Communication>Collaboration>Help

Leadership in Collaboration: Film Making and Interaction Design

There are useful parallels between making films and making web sites or software products. We'd be wise to study how they manage creativity, and how our divisions of effort, and means of collaberation, compare and contrast.

Berkun, Scott. UIWeb (2002). Design>Collaboration>Interactive>Multimedia

Leadership in Collaboration: Filmmaking and Interaction Design

For projects of importance, you need divergent skills to succeed. It is not possible to find an individual with all of the skill sets needed, nor would you want to. To create a first rate website or software product, you need many tasks to be done in parallel, which means that more than one person has to be working at them. As soon as two or more people are involved, the dynamic for how decisions are made, and how work gets done, becomes important. Any group of people can do work together, but it takes the right approach and team philosophy for that group to produce good work. Collaboration is critical in any creative pursuit involving groups of people, from filmmaking, to urban architecture or even web and software development.

Berkun, Scott. ScottBerkun.com (2002). Careers>Management>Collaboration>Interaction Design

Leadership Through Empowerment

Assigning responsibility without sharing authority is like making someone a peanut butter and jelly sandwich, but leaving out the bread. They know what they're supposed to chew, but have absolutely no way to handle, no way to manage the project.

Juillet, Christopher. Boston Broadside (1990). Articles>Management>Collaboration

Learning at Work: The Role of Technical Communication in Organizational Learning    

Concludes that technical support is an important audience for customer documentation and a source of knowledge. Proposes that technical communicators produce documentation that meets the needs of technical support and taps into that knowledge.

Wahl, Scott. Technical Communication Online (2003). Articles>Collaboration>Workplace

Learning Discourse Conventions: The Socialization of Technical Writers  

Newcomers learn about the practices and values of an organization through a process called socialization. Organizational socialization research provides useful information on the resources (such as mentors and written materials) that are available to these newcomers within organizations and the strategies (such as indirect questioning and disguised conversation) that new employees can use as they move into unfamiliar settings. At a time when there is a great deal of movement and uncertainty within industry, an awareness of socialization resources and strategies can be critically important in helping technical communicators make the transition to new assignments, divisions, or organizations.

Katz, Susan M. STC Proceedings (1995). Articles>Workplace>Collaboration

Learning from the Work of Others

Rolf Molich has conducted two experiments comparing the work of different usability teams, examining their practices, and looking for patterns and differences. His experiments provide extremely valuable material for sharpening individual usability practices.

Schroeder, Will. User Interface Engineering (2002). Articles>Usability>Collaboration

Learning Languages with Instant Messaging

While e-mail and discussion groups are other popular communication genres on the Internet, instant messaging is the most conducive to learning languages because of its synchronous nature. There are many ways to communicate over the Internet, but instant messaging is unique, because it almost simulates a face-to-face conversation. Unlike e-mail and discussion groups, users are not simply leaving messages to be read later. Users are both present, holding a live conversation. Although some of the subtle features of conversation are lost (such as facial expressions or tone of voice), instant messaging makes up for these disadvantages by being so widely accessible to so many people across the world.

Dean, Heather. Techniques (2003). Articles>Language>Collaboration>Instant Messaging

Learning the Fine Art of Reviewing

If you asked me what the most painful part of being a technical writer is, my answer would be: 'Getting reviews on time. Getting good feedback and inputs on your work.' For me technical writing has been very pleasurable because I hardly got any review comments. My morale has therefore been very high. Project managers, developers and others are so busy trying to come up with good software (read trying to fix all the goof-ups and bugs!) that they usually tend to give documentation lesser importance. User manuals, who reads them anyway? We do not have time for it!

Kamath, Gurudutt R. IT People (2003). Articles>Editing>Collaboration>Technical Writing

Learning to Listen  

We have been given two ears and but a single mouth in order that we may hear more and talk less - Zeno of Citium, ancient philosopher. Listening is our most used communication skill, yet it is the skill that is taught the least. This paper discusses why people don’t listen and how we view those who don’t listen. The paper also covers how to actively listen and the benefits of effective listening.

Scroggs, Debbie L. STC Proceedings (1995). Presentations>Collaboration>Communication

Learning to Use Virtual Team Collaboration to Solve Wicked Problems

The focus of this paper is the ELEARNING RESEARCH PROJECT (hereafter referred to as the EProject), a project to investigate how virtual teams collaborate to solve highly complex or wicked problems. The EProject designed, constructed, and assessed a Web-based collaborative learning environment to support virtual teams of intelligence analysts. The mission of these geo-distributed and cross-disciplinary teams is to learn to collaborate in order to integrate knowledge from diverse domains and thereby produce solutions for wicked problems.

Cupp, Stephanie, Joel Foreman, S. Gievska-Krliu, and Rachelle S. Heller. ACM Crossroads (2004). Articles>Collaboration>Online

Less Than Metcalfe's Law

Metcalfe's Law basically tells us that as you connect n number of machines you get n squared in potential value. So, with 2 machines you get a value of 4. When you connect 10 machines, you get a value of 100. When you connect 200 machines, you get a value of 40,000. People like to apply this idea to the internet. In particular, people claim that the strength of the internet is a direct result of so many machines being connected. I think that this is bullshit.

Rhodes, John S. WebWord (2001). Articles>Collaboration>Online

Liminality and Othering    

Subject matter experts, under the influence of modernist notions of authorship, often view technical writers as mere grammar and punctuation specialists and marginalize them as their ignorant 'other.' Technical writers, on the other hand, as rhetoricians occupying a liminal space between different disciplines, can understand different disciplinary rhetorics. If subject matter experts, instead of marginalizing technical writers, would view them as liminal subjects who are knowledgeable in different disciplinary rhetorics, then technical writers, through liminal practice, may be able to use their knowledge of audience and rhetoric to improve the quality of documentation.

Jeyeraj, Joseph. Journal of Business and Technical Communication (2004). Articles>TC>Theory>Collaboration

Listening: the Often Forgotten Ingredient

If listening isn't in the mix when developing documentation, then the project may not cook.

Allen, Clare. Boston Broadside (1992). Articles>Documentation>Collaboration>SMEs