From the Lamppost: Making Proposal Feedback Work For You
Constructive criticism is what you get when your husband tells you, “Yes, those jeans do make you look fat.” This is separated from regular criticism which is severe eye-rolling and/or covering of one’s eyes. It’s ok to get mad at the latter but constructive criticism? Mature people take it in the kind spirit in which it is intended. Or do they?
As one author noted, “Asking a working writer what he thinks about critics is like asking a lamppost how it feels about dogs.”
One experience that I and many of my peers share is having people review drafts of funding proposals. Over the years, this has been a painful or productive process, depending on the proposal, how decent a draft I’ve given people, and whether they (the reviewers) know what they’re doing.
I’ve learned some things about the proposal draft review process which I happily put to use this past weekend on a proposal for a very important community project. Here are my tips for not only surviving, but benefiting from, a proposal draft review.
1. Start the proposal development process with the group in a face to face meeting.
2. Review the proposal requirements, paying special attention to significant policy/program decisions.
3. Get agreement on the major issues at the beginning – don’t let things ride.
4. Share two drafts. An early draft with a lot of holes forces discussion about critical issues — this draft should be reviewed in a group meeting. The second draft is the ‘close to finished’ draft – unless there are big issues, getting individuals’ feedback is sufficient.
5. Tell your reviewers when you will be sending the draft out and stick to that schedule — even if you are not entirely happy with your progress.
6. Ask people to send their feedback/comments to you directly. One thing you don’t want in the late stages of a major proposal is outside kibbutzing – where some people in the group are talking to each other but not registering their issues with the proposal developer.
7. Take all the comments in before making changes. Get a sense of where your reviewers are – are they all focusing on the same 3 issues or are they finding things all over the place to change?
8. Schedule your review so there is actually time to influence the final product. Asking someone to review a proposal that’s due tomorrow is a transparent attempt to avoid having to change anything. I say you need to have a close to final draft at least a week in advance of the due date. Inconsequential stuff can be missing but 90% should be available to solid review/critique.
9. Alert the group when the concerns of a reviewer are such that the future implementation of the project could be impaired should it be funded as proposed. This is tricky because you don’t want to disrupt the proposal process but you have to insure core agreement on the design.
10. Advocate only for the competitiveness of the proposal and do that sparingly. Sometimes ‘regular’ people don’t understand what needs to be done to land major federal money. However, they still know what will fly in their world. A good proposal developer strives for balance here. That’s hard — because it also means the you cannot be defensive or argumentative. When you’ve spent days and weeks on a proposal, it’s hard not to defend every word. But that’s a mistake and we all know it.
I used to be very reluctant to have people review my work. Last minute scenes with supervisors and colleagues ripping the draft from hands were common. Figuring if I gave them no time to critique I could avoid criticism, I completely missed the boat on the whole purpose of external review. I had to learn it the hard way — it’s not about me. It’s about getting the money to make something important happen. So I have to suffer a little…..




Growing up, my family owned a dime store – just like this one – and we all worked in it. I started working when I was 12. Before that I would go to the store, get a bag of dimes from my Dad and ride the mechanical horse parked near the front window. So I guess that was kind of a job — being the object of envy for all the little kids begging their moms to let them ride the horse. I’d also do other key jobs – like feeding the little 29 cent turtles or cleaning the parakeet cages. Never mind that the turtles were probably loaded with salmonella – nobody cared about that. It was important to keep little Janice busy.













