Quiz — Chapter 6: The Specific Aims Page


Question 1. Why does one page — the specific aims — decide a research proposal's fate more than the other thirty-nine?

Answer It is read by everyone (often the only page non-assigned panelists read), it determines whether the proposal survives the first cut, and assigned reviewers form their thesis here and read the rest looking for confirmation. An excited reviewer advocates; a confused one scores you in the bottom half before the approach gets a hearing.

Question 2. Name the six moves of an aims page in order.

Answer Hook (problem + why it matters to the mission + why now) → gap (what's missing) → long-term goal + overall objective → central hypothesis + premise → 2–4 specific aims → payoff (impact + innovation).

Question 3. What makes a hook strong versus generic? Give the test.

Answer A strong hook names a specific, quantified, mission-relevant problem with an unsolved tension; a generic one recites background the reviewer already knows. Test: if your first sentence could open a dozen unrelated proposals unchanged, it's too generic — make the first sentence yours alone.

Question 4. Define the dependency trap and give the test for it.

Answer Aims are dependent when a later aim collapses if an earlier one fails (e.g., "Aim 1: show X works; Aim 2: find X's mechanism" — meaningless if X doesn't work). Test: for each aim, ask "if the prior aim disappoints, is this still worth doing?" A "no" is a dependency to restructure so each aim yields useful knowledge regardless of the others.

Question 5. Distinguish a hypothesis from a topic, and explain why reviewers want a hypothesis (for most research).

Answer A topic is an area ("we will study X"); a hypothesis is a testable claim that could be true or false ("we hypothesize X causes Y via Z"). Reviewers want a hypothesis because a page that only describes activities reads as a fishing expedition; a testable claim shows focused, falsifiable thinking and tells the reviewer what success would look like.

Question 6. How many aims should an aims page typically have, and what does having five or more usually signal?

Answer Two to four (three is most common for a full research grant). Five or more usually signals an unfocused or overreaching project — a classic novice error. Fewer, well-scoped, independent aims beat a large interdependent pile.

Question 7. What is the role of the premise / preliminary data on the aims page?

Answer It makes the hypothesis credible (a guess becomes a grounded, testable claim) and the aims believable (evidence you can do the hard early part makes ambitious aims feasible). An ungrounded hypothesis triggers the reviewer's fear of championing the flimsy.

Question 8. Resolve the tension: aims must be ambitious enough to matter but modest enough to be believable. How?

Answer Aim for significance-if-successful plus clear feasibility given resources and preliminary data. Too modest invites "incremental"; too ambitious invites "overreaching." Preliminary data resolves the tension by warranting that you can achieve ambitious aims.

Question 9. What is the difference between a page that describes a project and one that argues for it?

Answer A describing page neutrally lays out background and activities; an arguing page makes every move advance the case "fund this over the others." Description is necessary but insufficient; on one page with a tired reader, any sentence that doesn't push toward "yes" hurts you.

Question 10. Describe the non-expert test and why it works.

Answer Give the aims page to an intelligent colleague outside your subfield and have them tell you back what you'll do and why it matters. It works because the in-field expert fills gaps from their own knowledge and forgives ambiguity, while the non-expert (like a tired, cross-field reviewer) reveals where the page actually fails to communicate.

Question 11. Why should the payoff paragraph make the reviewer "feel the cost of not funding you," and how does this connect to Chapter 2?

Answer Because the payoff is the reviewer's last impression of the page, and Chapter 2's "two fears" include the fear of *missing a great proposal*. A vivid impact statement triggers that fear, making the reviewer want to fund you rather than risk passing on something important.

Question 12. True or false: You should write the aims page last, after the approach is finished. Explain.

Answer False. Draft it early — it organizes the whole proposal ("aims drive everything," Ch 5) — and revise it more than any other page. Writing it last (and rushing it) inverts the leverage, starving the highest-stakes page while over-polishing lower-leverage sections.