WORDS YOUR WAY BLOG
Writing on a Team: Lessons from the Founding Fathers
When I started out as a freelance business writer, I didn’t give much thought to anyone’s writing process but my own. Clients would send me assignments to complete independently. I’d cocoon and type. As my practice grew, I got opportunities to take on bigger projects, as a professional writer and editor embedded in work teams. I was eager to help people who said they dreaded writing — but I soon learned why these projects were so painful. At a kick-off meeting for a 20-page paper project, a program manager in a professional services firm warned that the team should expect to churn through 30-40 drafts. A nonprofit vice-president said she’d alerted managers in four agency departments they should allocate 10 percent of their time over the next four months to assembling a grant proposal. How could either scenario be possible? The professional services company expected me to act as note taker and grammarian. The writing process was as follows: A team of seven people would sit in a room for several hours a week, attempting to compose the paper sentence by sentence from beginning to end. It took about a dozen drafts before a basic conceptual framework emerged. They did not know the importance of planning before writing. The nonprofit organization ignored the structure supplied by the grant application itself; in weekly meetings, every invited staff member in every department reopened disagreements about program design, budget, and operations rather than starting from the specific questions in front of them. What they expected from a hired writer was someone who could find the magic words to create sense from their data dumps. Of course, this was nonsense. No writer could make a usable document from such contentious conversations. This team, too, needed an entirely different approach. As a developmental editor, I’m always looking out for simple ways to explain how to avoid these grueling exercises. I found some examples unexpectedly in historian Joseph Ellis’ entertaining books about the birth of the United States. His descriptions of how the founding fathers wrote are wonderful case studies in team-writing best practices. Option 1: Appoint a lead writer to produce the draft, and then let people review. As a kid, I imagined that Thomas Jefferson wrote the Declaration of Independence in a burst of inspiration. Actually, it was a team project. The Second Continental Congress appointed a “Committee of Five,” including Jefferson, who was chosen to compose the public announcement of a prior decision to separate from Great Britain. Jefferson drafted the document and submitted it for review and debate, first by the committee, and then by the whole congress. When to use this strategy:
- A member of your team has the time, skill, and willingness to complete a draft.
- The team trusts that the writer understands the group’s collective view, and the writer is comfortable deferring to the group for the final draft.
- Different sections or passages of the final product naturally call for different styles. For example, a program manager could write a persuasive executive summary for a proposal and a business analyst write the detailed financial planning section.
- You are willing to appoint or hire an editor to ensure cohesion. An editor might devise a template for each writer to follow. Or they might simply write an introduction, conclusion, and connecting text to ease the reader’s journey from one section to the next.
- No one on the team has the writing skills to produce the content that’s needed. For example, the learning curve for responding to a request-for-proposal (RFP) for a competitive federal contract might be very steep. There are experienced writers who specialize in those kinds of proposals.
- You need to combine the work of multiple contributors into a single voice.
- It’s counterintuitive, but if you hire a writer who’s not on your team, you need more clarity about the ideas, not less. Most good writers can generate logically sound copy based on any number of hypothetical concepts or angles. Your document should capture your team’s perspective, not the writer’s.
Barbara Ruth Saunders is a writer, editor, and writing coach.