1/n I experienced the rare victory of seeing “Selected” in the @NASA #proposal system this week. So I’m going to celebrate by jotting down a few notes that I hope will help others... especially those for whom the grant process might be intimidating:

2/n Learn and practice. I started with a huge advantage thanks to proposal-writing classes and clinics during my graduate studies, by @hauck , Curt Niebur, and Susan Niebur. I’ll avoid repeating this information, but I can’t emphasize enough how critical these insights have been.

3/n It’s all about #tenacity. You will be rejected... for great ideas... often. Have a drink, go for a run, take a day to mope, and move on. This award was my third attempt for the same concept. Overall, I’m at 40% success (as P.I.), which I’m thrilled with.

4/n Stick to the script. There absolutely is a formula for success... like a Hollywood blockbuster. It has to grab attention and be compelling. A proposal is a poem, short story, and thesis all in one. The Required Sections are your outline, every time.

5/n Make it obvious. Reviewers will miss obvious points. They have a million other things to do. Add an Executive Summary to the outline. Tell them all the great things about the proposal up front... and then tell them again in the proposal body. Use highlights and callouts.

6/n Buddy up. I work with a ton of brilliant engineers and technologists who have great ideas, but little interest or awareness of the grant process. The selection rates for science programs are pretty terrible, but there are often lots of opportunities in technology programs.

7/n Start early. Especially the budget. You might be able to pull an all-nighter to write the proposal, but the budget people have their own schedules, and they. will. not. be. rushed. It takes me ~3 weeks to write a proposal, but ~2 months to close the budget.

8/n End early. Unless you’re the VP/CEO of your own organization your employer will need to do the final submit to the @NASA #NSPIRES system. Getting all the information into the online forms can be challenging and slow. Office managers aren’t keen on last minute submissions.

9/9 It takes all types. I’ve never been a great student, and wouldn’t consider myself to be an particularly outstanding scientist. But I *am* pretty good at synthesizing information and pulling together a story and team. This is a useful skill for a PI. Build on your strengths.

10/9 Oh! I can't believe I forgot the most important one:
Serve on a review panel! The BEST way to learn to craft successful proposals is to see lots of good and bad ones and learn how fellow panelists judge them *and* meet future Co-I's.
Volunteer here: https://science.nasa.gov/researchers/volunteer-review-panels