As the author of a grant proposal, is this the process you're hoping will happen?
1. Two or more people working for the funding program separately read your proposal
2. A day or more after reading it, the group discusses a big stack of proposals. Buried in that stack is yours. One of them says to the other(s), "Which proposal are we going to talk about now?"
3. Someone replies, "Oh this is the one that (and they summarize it in only 2-3 sentences, concluding with what they like about it, compared with the others in the stack.)
4. The first person replies, "Oh yes, I remember that one now! Here's what I think."
5. Hopefully the discussion advances your proposal toward funding.
Focus on step #3. How likely is that to happen? Is what you're proposing so clear and compelling that a day later, your 'distant learner' will remember what they liked about it?
Try an experiment. Give your draft proposal to a stranger who knows nothing about it (tell them nothing except that this is a grant proposal), have them read it, give them a day, and then ask them to summarize briefly what you've asked for and what they think of the proposal. If they can't do it to your satisfaction, consider rewriting the proposal.
If you like this idea, don't do what most people do -- don't let the writing process lag so near to the deadline that there's no time to get this kind of review and then (if need be) reorganize and rewrite the text. Hint: if you have time for nothing else, focus on the title and the abstract.
If you like this note and would like to see more on how to write successful grant proposals, please let me know!
If you missed Advice #1, here it is in a nutshell: Don't use the saying I invented, "So far as I know, no one has ever done this"),
Showing posts with label grant-writing. Show all posts
Showing posts with label grant-writing. Show all posts
Tuesday, August 19, 2008
Wednesday, September 26, 2007
"So far as I know, no one else has ever done this."
I can remember when I was in my 20s, writing my first grant proposal. I was writing to the Fund for the Improvement of Postsecondary Education (FIPSE). Somehow I knew that it was important to be able to write in my proposal, “So far as I know, no one else has ever done this before.”
A year later, I’d crossed to the other side of the desk, to become a FIPSE program officer, and soon realized how silly my assumptions had been. In fact, my claim might even have been a reason that my proposal had been turned down.
- Writing “so far as I know” was important, because I didn’t want anyone to be able to say my magical sentence was false. And, in fact, writing ‘so far as I know’ helped me justify not doing any search for existing practice. Because, if I looked hard enough, I might discover that my idea wasn’t unique.
- It was important to write, “No one else has ever done this before,” because that’s what funders value, I assumed: uniqueness, newness, innovation. If someone else is doing this, I shouldn’t be wasting my time with a proposal.
A year later, I’d crossed to the other side of the desk, to become a FIPSE program officer, and soon realized how silly my assumptions had been. In fact, my claim might even have been a reason that my proposal had been turned down.
- An idea that is truly unique is probably responding to a problem or opportunity that no one else has ever faced. Few foundations are interested in supporting such tiny problems or opportunities.
- Someone who is as isolated as I was (or, worse, as isolated as I was pretending to be), has no opportunity to learn from the achievements and mistakes of others.
- Someone that isolated is also unlikely to find it easy to disseminate the results of their work. Dissemination generally is part of what funders consider to be the payoff to their gifts or investments: wider impact and visibility for their work. That was certainly true for FIPSE.
Labels:
FIPSE,
foundations,
grant-writing,
seed grants
Thursday, September 20, 2007
Four pieces of advice on writing persuasive grant proposals
I spent 19 years reviewing grant proposals for the Fund for the Improvement of Postsecondary Education (FIPSE) and Annenberg/CPB at the Corporation for Public Broadcasting. Here are four pieces of advice about writing proposals to grant competitions (internal or external) where the goal is to improve learning and where the competition is intense.
First and most important, grant proposal is an exercise in teaching at a distance. The desired learning outcome of your distance teaching is for two reviewers to meet, a day or two after they’ve each read the proposal, perhaps shortly before their review panel meets to discuss your proposal.
One panelist says to the other, “I don’t remember this proposal. What’s it about?” Panelist #2 replies, “Oh this is a good one. It’s about X and here’s why I think we should support it.” Panelist #2’s comments are no more than 60 seconds long, typically.
So what should panelist #2 remember to say about your proposal, a day or two after reading a stack of proposals of which yours was just one? That’s your challenge: teach these reviewers a few memorable things about your proposal, things that are important enough to excite the reader. If the reviewer thinks to herself, "I could borrow a couple of those ideas!" so much the better. Don't hide the good stuff.
Second, avoid passive verbs. Don’t be shy about saying “I” or “we.” It helps you use your own experience to a) explain why this is important, b) help educate the reader about whether and how much to trust your skill and insight (because you’re exposing more of your self and your experience.) Proposal reviewing is a confidence game.
Third avoid the current jargon, especially if the grant competition has an explicit goal– if everyone uses the same jargon, all the proposals sound alike.
Put those three things together, and you have the beginnings of a proposal that can persuade reviewers that you’ll be good at educating the world about what you’ve achieved with their money.
That's the fourth, and final, point. Whether far-reaching impact is an explicit goal or not, funders generally like it when other people can learn from the experience they’re paying you to gain. If you’re good at explaining (across disciplines and institutions) what you’ve learned, and being credible in the process, you’re a more valuable person/institution to fund.
Good luck, and please let us know if we can help with your proposal: evaluation planning? help you disseminate to other institutions? help plan faculty development? If you'd like to chat about grants, especially those having to do with improving teaching and learning with technology, please e-mail us at info@tltgroup.org.
PS Here's a chapter from the Flashlight Evaluation Handbook on how (not) to evaluate grant-funded technology projects.
First and most important, grant proposal is an exercise in teaching at a distance. The desired learning outcome of your distance teaching is for two reviewers to meet, a day or two after they’ve each read the proposal, perhaps shortly before their review panel meets to discuss your proposal.
One panelist says to the other, “I don’t remember this proposal. What’s it about?” Panelist #2 replies, “Oh this is a good one. It’s about X and here’s why I think we should support it.” Panelist #2’s comments are no more than 60 seconds long, typically.
So what should panelist #2 remember to say about your proposal, a day or two after reading a stack of proposals of which yours was just one? That’s your challenge: teach these reviewers a few memorable things about your proposal, things that are important enough to excite the reader. If the reviewer thinks to herself, "I could borrow a couple of those ideas!" so much the better. Don't hide the good stuff.
Second, avoid passive verbs. Don’t be shy about saying “I” or “we.” It helps you use your own experience to a) explain why this is important, b) help educate the reader about whether and how much to trust your skill and insight (because you’re exposing more of your self and your experience.) Proposal reviewing is a confidence game.
Third avoid the current jargon, especially if the grant competition has an explicit goal– if everyone uses the same jargon, all the proposals sound alike.
Put those three things together, and you have the beginnings of a proposal that can persuade reviewers that you’ll be good at educating the world about what you’ve achieved with their money.
That's the fourth, and final, point. Whether far-reaching impact is an explicit goal or not, funders generally like it when other people can learn from the experience they’re paying you to gain. If you’re good at explaining (across disciplines and institutions) what you’ve learned, and being credible in the process, you’re a more valuable person/institution to fund.
Good luck, and please let us know if we can help with your proposal: evaluation planning? help you disseminate to other institutions? help plan faculty development? If you'd like to chat about grants, especially those having to do with improving teaching and learning with technology, please e-mail us at info@tltgroup.org.
PS Here's a chapter from the Flashlight Evaluation Handbook on how (not) to evaluate grant-funded technology projects.
Labels:
FIPSE,
foundations,
grant-writing,
seed grants
Subscribe to:
Posts (Atom)