|
|
|||||||
|
|
||||||||
fundamentals of grantsmanship |
|||||||||||
|
by Janet S. Rasey, Ph.D.
The Basic Principles of GrantsmanshipA good idea is necessary but not sufficient. A successful grant application is an exercise in communication. The System helps those who know The System. Don't quit; revise and re-submit. Before You Write: Doing Your HomeworkKnow the Grantmaker Grantmakers, whether federal or nonfederal, don't fund what you want to do; they fund work that furthers their mission, which is evidenced in what work they funded recently and in program announcements (PAs), requests for grant applications (RFAs), requests for contract proposals (RFPs), and annual reports. A successful grant proposal submitted by someone else to a specific grantmaker is a good example - analyze what made it successful. Know the funding limits, stated or implied, of the grantor when designing your budget request. Use the telephone to get to know granting officers and solicit their expert advice. Poll your colleagues; consult your institution's Office of Sponsored Projects (or equivalent); use any legal means you can think of to learn the grantmaker's priorities. Know your colleagues, and ask them for help. Colleagues are essential for ideas, critical review, teaching you techniques you don't know, and suggesting funding sources. Colleagues often have experience reviewing grants and may know the work of people who will review your grant. As you mature in your discipline, cultivate relationships with younger scientists with fresh ideas and new techniques. Know yourself: time, capabilities, limitations. Know what you cannot do and seek collaboration. Give yourself far more time to write a proposal that you think you need; six months is a nominal time. If you get your thrills from pushing deadlines, save them for some project other than your grant. NO substitute for a good idea: know your subject. Find a good idea that turns you on - your enthusiasm for the work must show through. Be sure you are up-to-date on techniques, literature, and interpretations of ideas or theories. Specialize enough to develop and maintain your expertise and reputation - don't "subject hop" continuously, but don't get mired in yesterday's research either. |
Writing the GrantIt takes times, and more time... It takes about 120 hours, broken into many segments, to write a typical NIH R01 grant. A primary reviewer, assigned to read the proposal and write a critique, spends an average of 7-8 hours reviewing the grant. A reader, who does not have to prepare a written evaluation, averages less than 1 hour reading the proposal. In the Study Section meeting, the members spend slightly more than 20 minutes discussing the critiques and voting a priority score on the grant. This time compression points out the importance of clear communication of your goals, methods, and the significance of your work. Revise, revise again, and give yourself plenty of time to do it (about two weeks for each draft). There is no substitute for a good idea, but a successful grant application
is an exercise in communication. Get three kinds of reviewers for your proposal drafts: someone very knowledgeable in your field, an intelligent non-expert, and a good scientific editor. Don't ever assume your reader knows what you mean; explain it but do so without insulting his/her intelligence. Keep abbreviations, acronyms, and discipline-specific jargon to an absolute minimum. Answer the questions: Who, What, How, How much, Why are you doing
the work, Why is it worth doing, Where is the work going? When all else fails, read the instructions Don't get creative here - give the reviewers all the information they need in the format they expect to see. Try to get a copy of a successful grant as a model. Tell them what you are going to tell them, tell them, and then tell
them what you told them. Write the abstract last, so that it will be an accurate summary as well as a preview of the grant. Think like a scientist. Keep asking yourself, "What is the simplest experiment I can do that answers my question (i.e., tests my hypothesis)?" Avoid experiments that only collect data. If a reviewer sees a fishing expedition, your proposal is sunk. (There may be an exception to this when investigating a new subject; some baseline data gathering may be needed.) Focus your thinking and writing. KISS (Keep it simple [and short, and succinct], sweetheart.) The Review Process: Knowing What Happens After You Write Helps You WriteGet inside the reviewer's head. What do reviewers really look
for? Some reviewers may not be experts in your area of research, and you are just as obligated to communicate with them as with the leading researchers in your field who know all the techniques and jargon. Little things mean a lot. Reviewers don't like surprises - altered format, instructions ignored,
information missing or abandoned to the appendix rather than placed in
the body of the proposal. A Word About Revising & ResubmittingThe only people who don't make mistakes are the ones who don't do
anything; so spend no more than one day wallowing in discouragement if
your first proposal is rejected. If the reviewers "just didn't understand you", YOU are responsible for that. Try, try again, but remember that there is a point of diminishing
returns. Take reviewers' criticisms seriously but not slavishly - your ideas and your enthusiasm for them must come through in a revision. Sometimes a second or third revision is as good as it is going to get but fails to be funded because the ideas aren't getting any better. This is difficult to recognize by one's self; ask a colleague to help determine if you have reached this point. Copyright 1993 by Janet S. Rasey
|
|
|||||||||
| UW Home | My UW | Researcher's Guide | School of Medicine Research | Schools |