Featured Post

Dreams are Confused

Dreams are confused, yet men seek clarity there Oracles speak with twisted tongues; men trust them and do not despair From confusion--do...

Wednesday, April 20, 2011

How to Give Feedback on a Grant Application

Grant and fellowship applications are the most difficult thing to write. It is easier to do the actual scholarship, in many cases. I spent a few hours last night helping out someone with one of those, as a favor (though I will also do it for a stranger for a fee). Here's how I approach this kind of task.

The most difficult thing is to address a broad audience. In our scholarship we address other experts, but for a fellowship we need to emphasize the significance of the project, why anyone outside the narrow sub-speciality should care. Part of my task, then, is to help the person clarify specialized terms. Some people make a ritual gesture in saying that their work will be of interest to those in Comparative Literature, Sociology, disability studies.... In other words, they make a list of fields that are tangentially related to their project. This does not work unless there is a specific link articulated to one of these fields. For example, just because your work deals with performance does not mean that those in performance studies will be interested. You have to say what contribution you are making to this other sub-discipline. For example, you could make the argument that disability studies has never considered the influence of a certain cultural dynamic that your work brings out.

I've often said that people think of themselves as more anti-canonical than they really are. To write about obscure writers requires extra justification. And by obscure, I mean almost any writer at all aside from the few supercanonical ones. Nothing is supercanonical in my field except maybe Borges, Cervantes, and Lorca, and maybe a few boom novelists who've won the Nobel prize.

Since proposals are very condensed, it is difficult to avoid some vagueness and lack of clarity. At the same time, I am very harsh with vagueness in my comments, since this is a potentially fatal flaw. You can be concise and still precise. A summary of chapters of the proposed book is always helpful, with as much detail as possible.

Theoretical language, or jargon, is usually not welcome in grant applications. I usually tell people to cut that to a minimum.

It is good to read a proposal from the point of view of ignorance. In other words, the less I know, the more I can put myself in the position of the average historian or English professor with no specific knowledge of the topic. Of course, I won't necessarily catch mistakes that would be visible to a specialist reader, but a specialist might not realize what is unclear to the non-specialist.

3 comments:

brownstudy said...

I helped a friend write an essay applying for a fellowship.

To get the right perspective, I told her to remember that everyone has to answer to someone. The people granting the fellowship money would need to report to their funders justifying the disbursement of their money. They would have to report, say, that the money would support activity X that would provide benefit Y and this is of importance because Z (or some such dopey formula like that).

I told her to write the essay such that it could help the fellowship people make that case to their funders. Imagine they would excerpt bits of her essay for their report to their funders or in an annual report advertising the good work they do, so think about what would speak to them in that context.

I recall I really tried to eliminate the sort of gaseous vagueness from her jargon to make the ideas something that could actually be graspable.

I also tried to make sure her ideas were linked together like boxcars, so that this idea led to that idea, made sure the transitions were sensible and not surreal, etc.

sptc said...

Do you do feedback for institutional grant proposals, too? I mean, as part of your peer review service. I might engage you.

Jonathan said...

I could do institutional grants too.