Thursday, June 15, 2017

What's in an abstract?

This week I was working with a PI on her proposal, and found myself considering what exactly should go in a proposal abstract. This may seem a question with an obvious answer, but oftentimes a PI will write their abstract as an afterthought to their larger proposal. The trouble with shirking an abstract is that although it might be the last thing a PI writes (which makes sense), it is the first thing that reviewers see. So, even if you wrote the clearest, most compelling proposal in history, if your abstract is lackluster, the reviewers will have a bad taste in their mind when they get to the main body of your proposal, if they even get that far.

Hopefully that's enough to convince you to give your abstract some serious thought. To help you with this, I thought I'd identify some dos and don'ts (in reverse order) for your abstract based on the errors and strengths I commonly see in proposal abstracts.

Don't

  • Make the intro to your proposal and the abstract the exact same language. Remember, the reviewer who just read your abstract will now start reading the body of your proposal. It looks sloppy if you just do a cut and paste, even if it's using brilliant prose
  • Give extraneous details/examples: remember you don't have much room. Make every word count
  • Include an equation: Even if it's the key to your entire project, an equation cannot be fully explained in an abstract to justify its use
  • Use jargon/excessive acronyms: Remember, even if your proposal has to be very technical, the abstract should still be understandable by the layperson
Do
  • Describe the problem you're trying to address and how bad it is
  • Show how your project will help solve the problem
  • Give a brief summary of your project and your goals
  • End with the vision or broader impacts of your project
  • Use the first and last sentences of your abstract to drive home the importance of your project
I first learned to write an abstract in my freshmen biology lab. I remember our TA telling us that lab reports were not mystery novels, and that we needed to lay everything that was important out in the abstract, including our results. Don't treat results like the surprise ending to a novel; tell your reader the conclusion right at the start. This was good advice that I still remember today, and I share it with you to encourage you to put all you have into your abstract, so your reviewer is excited to read the rest of your proposal!

Resources

No comments:

Post a Comment

Thanks for your comment; it will be posted shortly. - Naomi