Online Technical Writing:
Note: I'm still gathering information for this section; stay tuned...
Peer-reviewing (also called peer-editing) means people getting together to read, comment on, and recommend improvements on each other's work. Peer-reviewing is a good way to become a better writer because it provides experience in looking critically at writing.
Team-writing, as its name indicates, means people getting together to plan, write, and revise writing projects as a group, or team. Another name for this practice is collaborative writing-collaborative writing that is out in the open rather than under cover (where it is known as plagiarism).
Strategies for Peer-Reviewing
When you peer-review another writer's work, you evaluate it, criticize it, suggest improvements, and then communicate all of that to the writer. As a first-time peer-reviewer, you might be a bit uneasy about criticizing someone else's work. For example, how do you tell somebody his essay is boring? Read the discussion and steps that follow; you'll find advice and guidelines on doing peer reviews and communicating peer-review comments.
Initial meeting. At the beginning of a peer review, provide your peer-reviewers with notes on the writing assignment and on your goals and concerns about your writing project (topic, audience, purpose, situation, type), and alert them to any problems or concerns. Alert reviewers to these problems; make it clear what kinds of things you were trying to do. Similarly, ask writers whose work you are peer-reviewing to supply you with information on their objectives and concerns. Specifically, give peer-reviewers information on any of the following about which you think there may be problems:
Peer-reviewing strategies. When you peer-review other people's writing, remember above all that you should consider all aspects of that writing, not just—in fact, least of all—the grammar, spelling, and punctuation. If you are new to peer-reviewing, you may forget to review the draft for certain aspects:
Peer-review summary. Once you've finished a peer review, it's a good idea to write a summary of your thoughts, observations, impressions, criticisms, or feelings about the rough draft. See the peer-reviewer note, which summarizes observations on a rough draft. Notice in the note some of the following details:
Excerpt from a note summarizing the results of a peer review. Spend some time summarizing your peer-review comments in a brief note to the writer. Be as diplomatic and sympathetic as you can!
Strategies for Team-Writing
As mentioned earlier in this chapter, team-writing is one of the common ways people in the worlds of business, government, science, and technology handle large writing projects.
Assembling the team. When you begin picking team members for a writing project, choose people with different backgrounds and interests. Just as a diverse, well-rounded background for an individual writer is an advantage, a group of diverse individuals makes for a well-rounded writing team.
If you are the team leader, you might even ask prospective team members for their background, interests, majors, talents, and aptitudes. These following writing teams combine individuals with diverse backgrounds and interests:
Planning the project. Once you've assembled your writing team, most of the work is the same as it would be if you were writing by yourself, except that each phases is a team effort. Specifically, meet with your team to decide or plan the following:
Much of the work in a team-writing project must be done by individual team members on their own. However your team decides to divide up the work for the writing project, try for at least these minimum guidelines:
Some of the work for the project that could be done as a team you may want to do first independently. For example, brainstorming, narrowing, and especially outlining should be done first be each team member on his own; then get together and compare notes. Keep in mind how group dynamics can unknowingly suppress certain ideas and how less assertive team members might be reluctant to contribute their valuable ideas in the group context.
After you've divided up the work for the project, write a formal chart and distribute it to all the members.
Scheduling the project and balancing workload. Early in your team writing project, set up a schedule of key dates. This schedule will enable you and your team members to make steady, organized progress and complete the project on time. As shown in the example schedule, include not only completion dates for key phases of the project but also meeting dates and the subject and purpose of those meetings. Notice these details about that schedule:
When you work as a team, there is always the chance that one of the team members, for whatever reason, may have more or less than a fair share of the workload. Therefore, it's important to find a way to keep track of what each team member is doing. A good way to do that is to have each team member keep a journal or log of what kind of work he does and how much time he spends doing it.
At the end of the project, if there are any problems in the balance of the work, the journal should make that fact very clear. At the end of the project, team members can add up their hours spent on the project; if anyone has spent a little more than her share of time working, the other members can make up for it by buying her dinner or some reward like that. Similarly, as you get down toward the end of the project, if it's clear from the journals that one team member's work responsibilities turned out, through no fault of his own, to be smaller than those of the others, he can make up for it by doing more of the finish-up work such as typing, proofing, or copying.
Setting up a style guide or style sheet. Because the individual sections will be written by different writers who are apt to have different writing styles, set up a style guide in which your team members list their agreements on how things are to be handled in the paper as a whole. These agreements can range from the high level, such as xxxxxxxxxxxx, all the way down to picky details such as xxxxxxxxxxxx. See the example of such a project style sheet.
Before you and your team members write the first rough drafts, you can't expect to cover every possible difference in style and format. Therefore, plan to update this style sheet when you review the rough drafts of the individual sections and, especially, when review the complete draft.
Excerpt from a style guide for a writing project. The items listed represent agreements team writers have made in order to give their paper as much consistency as possible.
Reviewing drafts and finishing. Try to schedule as many reviews of your team's written work as possible. You can meet to discuss each other's rough drafts of individual sections as well as rough drafts of the complete paper. When you do meet, follow the suggestions for peer-editing discussed in the previous section of this chapter, "Steps for peer-reviewing."
A critical stage in team-writing a paper comes when you put together into one complete draft those individual sections written by different team members. It's then that you'll probably see how different in tone, treatment, and style each section is. You must as a group find a way to revise and edit the complete rough draft that will make it read consistently so that it won't be so obviously written by three or four different people.
When you've finished with reviewing and revising, it's time for the finish-up work to get the draft ready to hand in. That work is the same as it would be if you were writing the paper on your own, only in this case the workloads can be divided up.
Information and programs provided by firstname.lastname@example.org.