Give reviewers a road map

Reviewing grant proposals this week, I realized the importance of "road maps." Too often, PIs are so immersed in their research and quick to jump into their project, they forget that their reviewers haven't been beside them as they've developed their research. From the reader's perspective then, they begin reading your proposal and they feel as if they've been dropped off in the middle of the jungle and told to figure out how to get home. So, what do they need...? a road map. Here's how you create a road map in your proposal so you don't leave your reviewer stranded and frustrated.

Start with a map
To return to my jungle metaphor, think about how reading your proposal is like dropping your reviewer into uncharted terrain; uncharted unless you chart it. Although, the first thing you want to do in your proposal is create a hook, i.e., describing the great big problem your project will address, you want to quickly show your reader what your project is about and how it's going to solve the big problem. This serves as an overview or a bird's eye view of your project. This gives your reviewer a sense of what they're going to come away with. Tell them what you'll convince them of before you try to convince them. This way they are less likely to get lost in your discussion.

Use Signposts
Now, the road map of your introduction will be helpful, but in the jungle or your research, things start to look a lot alike, a how do I tell this swamp from that swamp sort of thing. This is where signposts or headings become useful. Signal your reader that you're about to describe the cutting edge research or you're about to delve into the methodology. If your reviewer has a heading to guide them, again they'll be more likely to follow you through the section and see how the sections fit together into the larger map or proposal.

Review and reiterate important directions
If you're like me, when someone gives you directions and you follow the first two, you've forgotten the rest of them (if you're really like me, you probably didn't even make it past the first direction). Similarly, in grant proposals, you can't assume that your reader/reviewer will remember everything you've already told them. We've heard heartbreaking stories from PIs who received comments back with a rejected grant, saying they hadn't outlined this or that. The PI woefully describes how the requested information was on page eight! And, although we don't tell these frustrated PIs this at the time (better not to rub salt in the wound), it's still their fault for not reminding their reviewer about this critical information more than once.

So, when things are important in your project or related to the problem you're pursuing, say it at least twice in different areas. Now, this doesn't mean you should copy and paste. Instead, you just want to re-emphasize important points using different examples or even statistics. One successfully-funded PI described how she would give national statistics about how bad the disease she was studying was in one section and then global statistics in the next section, just to remind the reviewers about how bad the problem was.

These three tips can help keep your reviewers on top of the information you're providing them instead of making them wade through the unknown depths of your research.

Resources:
7 Strategies for Writing Successful Grant Proposals - Professor Claudia Sanchez
Grant Proposals - or Give me the money! - University of North Carolina, Chapel Hill