This weekend I’m writing a short proposal for a research project that will hopefully be funded by an NSF Research Experience for Undergraduates (REU) grant. I wanted to take a few minutes to compile a list of the bits of advice that I’ve come across in the process.
First, I think the advice my advisor gave me is most important. It’s short, but sweet: the idea you propose should be crisp and easy to understand. It should be clear with minimal technical detail why the problem is important and whether it’s reasonable to tackle in the timeframe of the research program.
Now, on to advice compiled from sources on the internet. First, from the HFSP:
- Do you have a clear, concise, and testable hypothesis? (Similar to my advisor’s advice)
- Are your objectives and aims coming into focus?
- What questions are to be addressed?
- Can you define and design specific experiments that will test your hypothesis?
I think 3 is critical for a short proposal like mine. The most important aspect of conveying an idea for a research project is clearly stating and motivating the questions that the work will answer.
Simon Peyton Jones and Alan Bundy also have a great compilation of advice geared towards computer science research. First and foremost, they emphasize the importance of writing an introduction that has wide appeal. The first page or so should not cater only to experts in your field as they will make up a very small percentage of the people who will read it. From a technical standpoint, it’s important that the problem be well-formulated, that the solution require original research (not a mechanical application of existing techniques), and that the solution be important.
More to come as the process continues.