Finding Clarity in Project Descriptions/Narratives

The season of internal grant proposal review is upon us, or upon me anyway. And, as always, I use my experience reviewing to draw blog inspiration. What's been jumping out at me most is the importance of offering a clear project description or project narrative in your grant proposal.

In the grant development world, our conversation often focuses on the importance of making a case for your project - explaining what's been done already and why your research is so important. And while making a case for your research is essential in securing grants, it is equally important to very clearly show your reviewers what you're going to do.

In the last week, I've seen proposals that made an excellent case for their research, and got me on board, thinking "yes, I agree, this research needs to move forward." But, at the same time, more than once, I found myself asking "But what are they going to do?" They might have done a nice job of telling me what's been done already, including what they've done, but that does not serve as a substitute for telling me what they will do next with the funding for which they're applying.

Below, I offer some tips to clearly convey your project narrative.

Give an overview

Most research is complex; there is a reason that most researchers in academia have a terminal degree. But therein lies the rub when trying to synthesize your doctoral level work to someone who has a doctorate in something else. Offering an overview of your project is thus a good way to ease your reviewers into understanding your project. If you begin by giving them a summary of what your project is about before giving them the details, they're more likely to be able to follow you into and through some of the more technical project details.

Use numbers

Giving specific numbers of things can help reviewers get a picture of your project. How many subjects? How much time? How many groups? Answering these type of questions can give your reviewers clarity around the scope of your project. Having said that, although numbers can be helpful, be careful about including equations or formulas in your grant proposal unless absolutely necessary and only when you can be sure that reviewers will be able to make sense of them.

Give a timeline

People, including reviewers, tend to think chronologically, so offering a timeline image in your project narrative can give them clarity around what step you'll be doing when. It also offers a concrete snapshot of your entire project.

Use plain language in Methods

Methods tend to be the most technical part of any research proposal. These are where the acronyms, formulas, and algorithms are unleashed, making it treacherous reading for reviewers whose expertise does not lie in your exact area. So, write it carefully. Think before every step, is there a clearer, more accessible way to say this. If the answer is yes, rewrite it in that way. All of your reviewers, including your technical experts, will thank you for going the extra mile to write a clear and understandable methods section.

Remember, even if you've convinced your reviewers that the world will end if research doesn't move forward, they will still not recommend funding if they don't understand your project. Follow-up that case with a clear solution.

Resources

Project Summary/Abstract and Narrative - NIH