Your grant – the rejected recipe or the funded menu
15 December, 2010 | Morgan Giddings |
|
|
Imagine you’re a hungry restaurant patron, and when you walk in the door, the waiter hands you a stack of recipes, instead of a menu, to choose your food from.
The recipes don’t do anything to describe how the food will look or taste, they only tell you how the chef will make that particular item. They go into detail about how the potatoes must be skinned, the batter must be mixed, and so on. Because they waste so much space on the recipes, there’s not much attention paid to explaining the finished culinary characteristics.
The above scenario might be great for the true foodie who understands what all the ingredients are doing for the dish, but for everyone else it would be a turn off. It’s likely the restaurant would go out of business (unless it had a weird sort of success by generating a cult/alternative following… you never know).
How this relates to your grant
This example is important to understand if you’re writing grants and want them funded.
Many grant writers I encounter are totally focused on the details of how they’re going to do the work. They’re so focused on those details that they give short shrift to other key elements. Basically, what they end up writing is one big long “recipe.”
Jane the restaurant-goer
To understand the problem with this, let’s go back to the restaurants for a moment. Imagine Jane, with a stack of 12 menus to read before she can decide which restaurant to go to.
Let’s say that two of those menus are well-written. They are clear, well-organized, and most importantly, they explain the finished culinary characteristics of each item. They list (in small print below each item) the important ingredients, but they don’t go into details about exactly how those ingredients are prepared (i.e. they don’t mention skinning the chicken or pressing the soybeans before cooking them, because the patron doesn’t need to know those things). They also have appealing names for each item.
The other ten of those twelve menus are a bunch of recipes for plain-sounding dishes like “chicken soup” and “chocolate chip cookies”. They might occasionally mention a culinary characteristic, but because the recipes are so detailed, there’s not much room for describing anything but the cooking steps.
If Jane is an average human, she’s going to be far more likely to pick one of the restaurants that has a normal menu. She’ll be more excited about them, because the menu has helped her visualize how the food items will look and taste.
Bob the grant-reviewer
Bob also has a set of menu choices, but in this case they’re grant proposals. Like Jane, he is limited to choosing one or at most two to advocate for – and he must be excited about that one if it is going to have a hope of being considered in the larger study section.
Guess what type of grant proposal Bob is more likely to get excited about? Will it be the one that just focuses on all the details of the recipe(s)? Or will it be the one that starts with a clear explanation of why the project is appealing in the first place, what it will do for the world (or agency), leaving the “recipe” for a smaller portion of the proposal?
If Bob is an average human, he’s going to go for the grant that most appealingly presents the project, and backs it up with evidence that the applicants are likely to succeed at that project. He doesn’t care too much about the recipe’s details. Perhaps he needs to know a few key details (are they using lard or olive oil in the recipe?), but he doesn’t need to know everything.
You may object: what about the people who do want to know all the details? There are the occasional reviewers who love to dive into the details of how (the recipe), without knowing why (will the finished food be good?) – but those are in the minority.
Since each grant is usually reviewed by 2-3 people (sometimes more), it is rare indeed that all of them are interested in the minutiae of how.
Why this concept is vital
If you deeply understand this one concept, you get what differentiates a great proposal from one not so great. It is at the core of all great grant writing, because it is all about helping your reviewer make an “easy choice” of your project. You can only do that if you step beyond the recipe, and help the reviewer form an exciting picture of your successful project in their mind – much like the restaurant patron anticipating a great meal.
For more free grant writing tips
For a series of new, free videos, including a free NIH specific aims template and video showing you how to use it, browse over here.
———-
Morgan Giddings, PhD is the author of Four Steps To Funding, and has been tenured faculty at UNC Chapel Hill in three departments with fancy sounding names. She will soon be moving to a smaller institution to free up a bit of time to help others optimize their career success.
|
Effective analogy. Maybe restaurants could learn from this and change their menus to grant us more upfront satisfaction. Once the grant is completed, though, and the promised gourmet food appears on the table, woe to those who have whetted our appetite and delivered fast food with relish instead of the chef’s specialty with sauce. If we continue to milk the analogy, we maybe want to include the term “fresh” in the names of our menu dishes. The catch of the day is so much more interesting than the parsley-sprinkled caught-last-year.
While this sounds nice and interesting, I have my reservations. So who will get the grant at the end? Most probably, or at least in most cases the guy with the “big name”, no matter how boring, not novel and uninteresting is his proposal.
@Jean-Luc But if the menu describes food in a way that mismatches with reality, then the patrons will never come back again. The “product” must be good, and it must also be described well. There are two necessary parts to this equation, and it won’t work if one is missing. Many scientists I know have the first part (good science) but are lacking the second part (an appealing description). But, of course, there are some people with the opposite problem (not good science but a good ability to describe it). I believe they fare no better in the long run.
@avri I was an “unknown” when I got my first and second R01’s funded. Before that happened to me, I also took the cynical negative view that you have. But I’ve come to be not so cynical, because I’ve seen reviewers respond to clear descriptions of good science far more than they appear to “whose name is on the proposal”
A nice to read article. But I am afraid that this oversimplification may mislead the aspiring younger researchers. I have been funded by both NIH and VA, and had been on study sections of both. My experiences are not at all comparable to the menu vs. recipe scenario. It is not just grantsmanship, which is like icing on a base of cake, that helps to get funded. The base of the cake is very important. That is constituted by: 1) Significance of the project; 2) Convincing preliminary data; 3) Approach and feasibility; 4) Investigator’s ability to carryout the studies; 5) Enviroment. If these are sound, no grant will be rejected just because the grantsmanship is not so sound. On the other hand, if these are weak, no grant will be funded just because it has great presentation with grantmanship. Let us be clear and honest that grant reviewers are not comparable to hungry restaurant customers, whose minds and patience are clouded by biological instict of hunger. Having said that, good grant writng and presentation are also important ingredients. But they alone do not decide success of getting funded.