Advice for New Managers: Part 1

The central mistake new managers make is egoism. On the surface, the change is all about you: you’ve been promoted, you have a new job title, you have a new office. Perhaps you’ve been waiting for this change for some time, while watching peers or friends get promotions, and now finally you feel you’ve received the respect you’ve earned.

Berkun, Scott. ScottBerkun.com (2006). Articles>Management>Collaboration

Be Productive When a Project Stalls    

With more and more companies adopting the Darwin Information Typing Architecture, Baril discusses how to choose a compatible content management system that also supports your company's processes.

Gutowski, Amanda and Lori L. Pennington. Intercom (2008). Articles>Project Management>Planning>Collaboration

Bilingual Team Writing: Planning a Project  

A two-person bilingual writing team enabled a software application development group to produce on-line documentation and a user guide simultaneously in two languages. Team writing in an international environment requires detailed planning, constant monitoring, and continuous communication in order to succeed.

MacKay, Brenda. STC Proceedings (1994). Articles>Project Management>Localization>Collaboration

Breaking the Ice With SIN SIG

SIN stands for Shy, Inactive, or New. I admit that it wasn't my original idea--I appropriated the name and concept from another organization.

Miller, Elisa K. Tieline (2006). Articles>Collaboration>Management

Building and Managing Virtual Teams

Chris Nagele’s run Wildbit, creators of hosted Subversion app Beanstalk, for 8 years virtually. He lives in Philadelphia and his team is all over the world. So, he knows a few things about virtual teams and shares them in this article.

Nagele, Chris. Vitamin (2008). Articles>Management>Collaboration>Online

Can Academic Partnerships in Technical Communication Work?: Lessons from Minnesota  

Interuniversity partnerships are widely encouraged as a way for public universities to pool increasingly scarce resources, to minimize duplication of academic programs, and to cooperate rather than compete. Joint programs in technical communication have not been widely studied, but they seem especially logical for several reasons.

Black, Suzanne. CPTSC Proceedings (2003). Articles>Education>Management>Collaboration

Collaborating in Project Management, Long-Distance  

From early 1993 through July of 1994, three STC chapters jointly managed a research project on Technical Communication in Western Canada. Based in Winnipeg, Calgary and Vancouver, the managers were thousands of miles apart, relative strangers and simultaneously engaged in running their own businesses. In this volunteer assignment, they involved committees within their own chapters. As team building and collaborative arrangements become more prevalent in technical communications projects, it can be instructive to look at how such a farflung research project fared. We will relate this experience briefly to some research results reported in Technical Communication.

Jones, Sheila C. STC Proceedings (1995). Articles>Project Management>TC>Collaboration

Collaborative Document Editing with svk

Say you have a document that needs to be presented in two languages and you are the translator. While the translation is in progress, someone revises the original master document. This means you now might be working with an outdated paragraph or one no longer present in the master version. This article tries to map this problem to parallel development, which version control systems solve with the branch and merge model. You will also see how svk helps you maintain translated documents easily.

Kao, Chia-liang. O'Reilly and Associates (2004). Articles>Content Management>Collaboration>Writing

Comics: Not Just for Laughs!

Every project has its own unique set of 'opportunities'--also known as challenges. Many of these challenges relate not to the quality of our work, but rather to the communication of our ideas. Often in the course of design, you must communicate complicated concepts to a non-technical (and often uninterested) project sponsor, client, or stakeholder. So how do you capture their interest, get their understanding and buy-in, and finally move on?

Sedaca, Rebekah. Boxes and Arrows (2007). Articles>Project Management>Collaboration>Technical Illustration

Conducting Effective Team Technical Reviews

Mention team technical reviews to a group of tech writers and chances are good that you will either get a loud, collective groan, or the group will vie to tell the best review horror story. On the one hand, technical reviews are a vital part of our jobs because they help us to produce high quality product documents. On the other hand, technical reviews gone wrong are the bane of our existence. The good news is that we have the power to conduct consistently effective technical reviews. This article summarizes why we do reviews and what often goes wrong in reviews, and then summarizes steps to take before, during, and after technical reviews that can help you conduct effective team technical reviews. Although your process and team may differ from what's described here, you can apply the information in part or in whole to improve your current review process.

Brown, M. Katherine 'Kit'. TECHWR-L (2008). Articles>Project Management>Collaboration>Assessment

Connectfulness

In the same way that the word 'truthiness' is not a real word but is gaining usage in our culture, so the word 'connectfulness' offers us in the professional arena a way to express an important aspect of our work. Just as truthiness says more than accuracy and is friendlier than truthfulness, so connectfulness says more than networked and is friendlier and more inclusive than connectedness.

Albing, Bill. Carolina Communique (2006). Articles>Content Management>Collaboration

Content Re-Use with the Tools at Hand  

Frequent updates for a swarm of modular plug-ins were interrupting work on larger, higher-value projects. Worse, development was happening in a time zone 12 hours away, making communication a major bottleneck. Faced with fixed resources and growing commitments, our writing group extended existing tools to automate information gathering and rough draft creation, thereby halving the writer time each module required. This paper describes the user interface, tool extensions, and reusable information approach we used to solve the problem.

Carpenter, Cory, Samantha Lizak and Jeffrey Young. STC Proceedings (2005). Articles>Content Management>Collaboration

Do Groups Know What They Don't Know? Dealing With Missing Information in Decision-Making Groups    

Although scholars have examined how individuals deal with information that is unavailable on decision-making tasks, little research has explored how groups deal with missing information. The present study proposes two ways groups can address information that is unavailable: by employing a diminished information set or by inferring the value of missing information. Both of these approaches are tested using an information sharing task. Groups are compared with information unavailable to any member, available but unshared among group members (i.e., hidden profile), and available and shared among all group members. Evidence indicates that group members may utilize both strategies to deal with missing information.

Henningsen, David Dryden and Mary Lynn Miller Henningsen. Visual Communication (2007). Articles>Knowledge Management>Collaboration

Documents That No Project Cannot Be Without

Short deadlines force project teams to quickly design, test, and release the product with little or no design documentation. If these documents are written, they generally are not well-written and are not comprehensive. The fact of the matter is that most project teams do not have enough staff to design the product, let alone write and manage documentation. This situation creates an ideal opportunity for technical writers to assist the project team in more ways than writing a user guide.

Dick, David J. Carolina Communique (2008). Articles>Documentation>Project Management>Collaboration

Easing Into Agile Modeling

Agile modeling started out fairly complex and it grew a bit into its current form.

Ambler, Scott W. Agile Modeling (2006). Articles>Project Management>Agile>Collaboration

Eleven Commandments for Conducting a Business Meeting  

In response to Gary M. Smith's article 'Eleven Commandments for Business Meeting Etiquette,' which focuses on the conduct of those attending meetings, Sullivan presents eleven rules for the organizers and speakers of meetings.

Sullivan, Christine A. Intercom (2000). Articles>Management>Collaboration

Employees Want to be Led by Leaders Who Lead

Virtually every employee in an organization performs a discrete set of tasks. Only the leader sees the big picture -- unless the leader does a good job of conveying that big picture to his workforce. Of course, there's more to leadership than getting people to buy into your vision.

Holtz, Shel. Communication World Bulletin (2003). Articles>Management>Collaboration>Rhetoric

Enabling Information Sharing Integrity

Most companies accept the rapid obsolescence of their documents as an unavoidable cost of doing business. Its not. When dynamic documents replace static documents, users can bring together disparate, distributed data and content and combine it in a single document that is always accurate and up-to-date.

Sorofman, Jake. Content Wrangler, The (2008). Articles>Content Management>XML>Collaboration

Ensuring A Successful CMS Implementation

The single most important factor in a successful CMS implementation lies with you and your people. Your staff members are the principal users of the system, and the SMEs in your organization are the secondary users. It is their adoption of the new processes and governance structures that makes or breaks a CMS implementation. According to some, process and cultural change accounts for 90%, while technology contributes only 10% to the success of a CMS.

Hamer, Emma C. Rockley Bulletin (2007). Articles>Content Management>User Centered Design>Collaboration

FC.Net - Getting Started

Born to lead or learn to lead? Truth is -- no one knows for sure. But there is a small industry of writing, teaching, and speaking built on the proposition that you can at least talk about it. Studies by the Center for Creative Leadership and the Honeywell Corporation suggest that, after direct experience, the second source of learning about leadership is conversation with others.

Breen, Bill. Fast Company (1996). Articles>Management>Collaboration

Filling Knowledge Gaps    

Knowledge gaps arise when a small team in an organization creates or compiles a body of knowledge that needs to be deployed to a larger group of people. A gap then exists between the small team that has the knowledge and the larger group of people who need it. In the normal course of doing business, healthy organizations naturally create knowledge gaps, and the healthiest organizations create the most knowledge gaps.

Reid, Clifford A. STC Proceedings (1998). Articles>Collaboration>Communication>Knowledge Management

The Fox and the Hedgehog Go to Work: A Natural History of Workplace Collusion    

The author argues that an ironic approach to collusion can help shift the focus of resistance away from the relatively rare events surrounding implacable opposition or total unanimity to the quotidian aspects of workplace politics. Collusion is characterized as an outcome of organizational politics conducted between the traditionally opposed parties of radical industrial sociology (i.e., managers and workers) under the guidance of an ironic mode of cognition. Irony is depicted as a foxlike way of gaining 'a perspective on perspectives,' which provides a means of understanding stalemate, accommodation, and collusion by showing how opposing ideological positions are indebted. It also illuminates the moments when collusion breaks down and resisting parties become implacably opposed hedgehogs (one position prevails over the other), leading to overt conflict and resistance.

Sewell, Graham. Management Communication Quarterly (2008). Articles>Management>Workplace>Collaboration

Getting Started with Performance Management  

What are some ways to effectively track and manage a group’s performance? Wiley examines a way to do so using specific requirements designed to measure the success of an STC SIG.

Wiley, Ann L. Intercom (2006). Articles>Project Management>Collaboration>Methods

Getting the Ear of Your CEO

Communication professionals can and should have frequent, direct access to and influence on executive leadership. Your CEO needs you, but are you ready? It is a misperception that CEOs are too busy, uninterested or unreceptive. While some communicators have close contact with executives, many other communication professionals rarely see the CEO and may have many layers of management between themselves and that "C-level" suite. But you don't have to report directly to the CEO to get his or her ear.

Gayeski, Diane. Communication World Bulletin (2003). Articles>Business Communication>Management>Collaboration