Key Takeaways — Chapter 17: Grant Proposals
The summary card. Read this to re-ground before the quiz, before a writing task, or weeks later.
The one idea
A grant proposal is not a description of work you'll do; it is a persuasion document aimed at a tired, overloaded reviewer. That reviewer gives you fifteen to thirty minutes, reads the first page and the headings most carefully, and is looking for a reason to decide. Every choice — what goes first, how aims are phrased, what you cut — follows from that one reader. Most proposals are rejected for writing problems, not idea problems, which is the bad news and the good news at once: it's your fault, and it's fixable.
The Specific Aims page (the single most important page)
Whatever the funder calls it — NIH Specific Aims, NSF Project Summary, a case for support — it's the page every reviewer reads carefully and the one that frames how they read everything else. Build it in four moves:
| Move | Job | Key rule |
|---|---|---|
| 1. Hook | Big problem → specific gap, fast | Open with the problem, not the field's history |
| 2. Pivot | "We propose…" + preliminary data + hypothesis | One clean, confident sentence; data prove it's real |
| 3. Aims | 2–4 testable objectives | Objective-first + method + expected outcome; independent |
| 4. Payoff | What changes if you succeed | Redeem the importance you promised in move 1 |
Aims are objectives, not activities. Determine / Establish / Test (verbs of knowing) beat Perform / Run / Explore (verbs of motion), because a grant funds the reduction of uncertainty, not the expenditure of effort.
Significance vs. innovation vs. approach
Three questions, scored separately:
- Significance — why does this matter? Name the specific consequence of this project's success, not "the topic is important."
- Innovation — why is this new? State what's new and what the newness enables.
- Approach — will it work? Design + expected outcome + pitfalls and alternatives (your strongest trust signal) + preliminary data.
The disciplines that decide it
- Run the "so what?" test on every sentence, paragraph, and section — because the reviewer is.
- Tie every budget dollar to an aim and a task. Money in the abstract looks like greed; money tied to work looks like planning.
- Make broader impacts concrete and resourced. Platitudes ("committed to diversity") lower trust; named programs and real numbers build it.
- Talk to the program officer before you write — fit is the most wasteful failure to discover late.
- Write the aims page first, revise it for weeks, and read the current solicitation — never your memory of last year's.
If you remember three things
- The reviewer is exhausted and reading the first page most carefully — lead with the proposal, not the background.
- Aims are objectives with expected outcomes, and they should stand independently.
- Ideas rarely get rejected; writing about ideas does — so the fix is in your control.
Themes this chapter surfaced: #2 audience-is-everything (central — the reviewer) · #5 structure-serves-the-reader (the four moves) · #6 every-sentence-earns-its-place (the "so what?" test) · #1 writing-is-thinking (the aims page extracts the hypothesis you didn't know you hadn't committed to).
Threshold concept: A grant is a persuasion document aimed at a specific, exhausted reader — not a description of work.
Anchor advanced: Dr. Daniel Reyes writes her first Specific Aims page (weak → strong).
Back to: Chapter 17 · Exercises · Quiz · Further Reading