Strategies for revision

December 17, 2009 at 10:46 am Leave a comment

Scientific writing can be thought of as a two-stage process in which we first write for ourselves to discover what we think, and then transform our writing through revision, so that it works for others, too. Below are some ideas and strategies for tackling the revision process with success.

Deducing readers’ needs

Are you a genomics researcher who’ll be submitting to a computational biology journal read by biologists and mathematicians alike? Or an environmental engineer hoping to publish in a restoration ecology journal? As science becomes increasingly interdisciplinary, we often find ourselves writing for audiences that have very different perspectives and goals from our own. So, if one goal of revision is to produce prose that serves these diverse readers, how do we decide what readers need?

  • Choose the journal you’ll submit to before you start writing. Then, read the guidelines for authors or analyze the writing of a few papers from the journal (preferably well written ones!) to get a feel for how authors frame their work, the background they include and the language they use.
  • As Paul Halmos says in How to Write Mathematics, ask yourself who you want to reach and then write to that person. That is, picture a smart, interested reader who has little background in your field and is skeptical of your approach. Then ask yourself: What extra information might s/he need to grasp the significance of my research problem? What hard questions might this person ask about my methods or results? Or, on a more basic level, what difficulties might this person have understanding my work, and how can I phrase things to avoid these difficulties?
  • Ask a general reader to review your writing before you revise. Your advisor and co-authors are excellent reviewers of the scientific content of your paper. But because they’re just as familiar with the research as you are, they may miss places where you aren’t being clear, are making leaps in logic, or using too much jargon. That’s where a general reader – your spouse, a graduate student friend in another field – can really help.

Think globally, then locally

It’s always preferable when revising to focus on “global” issues first – those concerned with the overall message, argument and organization of a piece – before addressing “local” problems, such as grammar, word choice, sentence structure and so on. Nevertheless, less experienced writers – and reviewers – often have a difficult time letting local issues go; their tendency instead is to polish, polish, polish as they write, or to correct these matters compulsively as they review someone else’s work.

What’s wrong with this? The main problem is that it can be very inefficient. Often we spend a lot of time refining a sentence, paragraph or section only to throw it out later because it doesn’t fit. What’s more, focusing on local issues too early can interrupt our train of thought, so that we end up forgetting where we’re going overall, or fail to capture key insights on paper.

Doing some polishing as we write is inevitable. But during the early stages of drafting and revising, try to stay focused on the big picture by asking yourself these kinds of questions:

  • What am I trying to say? Have I discovered my main point or “bottom line” yet?
  • How is my overall argument or message taking shape? Where am I including too much information – or not enough? Are there any leaps in my logic?
  • Is the content organized in support of my main point or message?
  • Am I serving the needs of the reader? (See the discussion above and the handout “Turning writer-based prose into reader-based prose.”)

I just can’t see what’s wrong…

Putting “fresh eyes” on a piece of our writing, so that we recognize where the problems lie and can fix them, is tough. If you count yourself among those who just can’t tell where and what to revise (and you’re not alone), here are a few strategies to help you:

  • Put your work aside for a time. At least a week is good, longer if you can spare the time. Try it, and you’ll likely find yourself saying, “I wrote that? It doesn’t make any sense!”
  • Ask a friend or colleague to read a passage from your work, and then explain out loud what s/he thinks you were trying to say. This should not only give you a sense of how clear your main points are, but it should also help keep the reviewer from picking on grammar, word choice and other “local” issues (see above).
  • Read your writing aloud to yourself. Nothing reveals convoluted, wordy and confusing prose faster than hearing it spoken aloud.
  • Get a good critique. Although we can all learn to better evaluate our own work, nobody in the end can do without a good editor or reviewer. Just make sure you pick yours carefully: Someone who’ll focus on larger issues rather than local ones; who’ll give specific feedback (Comments like, “I get lost in this section,” or “This great!” don’t cut it); someone, in short, who is exacting and honest but kind, whose feedback encourages rather than discourages you from revising. Note that you may need to explain to this person what you’re looking for in a critique.

References

N Sommers (1980) Revision Strategies of Student Writers and Experienced Adult Writers. College Composition and Communication 31(4): 378-88

Advertisements

Entry filed under: Audience, Revision.

Exploratory writing in scientific writing

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Trackback this post  |  Subscribe to the comments via RSS Feed


Science of Scientific Writing

This article describes what readers expect when they read - and how scientific writing often violates those expectations.

%d bloggers like this: