Quiz — Chapter 9: The Project Narrative / Research Approach
Question 1. What question does the approach answer, and why do strong-significance proposals often die here?
Answer
"Can you actually do this?" Strong-significance proposals die in the approach when the plan is vague, overreaching, or naive — a reviewer who wants to fund an important problem still won't stake their credibility on a plan they don't believe. Significance gets you excited; the approach gets you funded.Question 2. State the threshold concept and the three reasons disclosing a weakness strengthens a proposal.
Answer
Name your weaknesses before the reviewer does. It strengthens because: (1) it removes the reviewer's ammunition (an addressed weakness can't be an unanswered critique); (2) it signals expertise (only an insider knows where the real risk is); (3) it builds trust through honesty (candor about risks makes you believable about strengths).Question 3. Define "strategic detail" and the failure it prevents.
Answer
Lavishing detail on the critical and risky parts while summarizing the routine. It prevents the "wall of methods" — uniform dense detail with no emphasis, which buries the load-bearing logic and reads as camouflage for the absence of judgment. The details you choose reveal whether you know where the risk is.Question 4. Why structure the approach to mirror the aims?
Answer
Two benefits: navigability (the reviewer finds the plan for each aim in order) and coherence (visibly tying each part back to a specific aim shows the proposal is one connected argument — aims promised, approach delivers, aim by aim).Question 5. What does preliminary data (research) or track record (programs) prove, and how should it be placed?
Answer
That you can already, in part, do the work — answering feasibility doubt with evidence rather than promises. Place it where the reviewer's doubt is strongest (if recruitment is risky, show you can recruit; if the method is novel, show it working). Evidence placed against its doubt is far stronger than evidence scattered without reference.Question 6. How do you write a pitfalls-and-alternatives passage, and which risks should you address?
Answer
Three parts: name the honest pitfall, assess its likelihood/impact briefly, and give a specific contingency. Address your two or three *genuine* risks — the ones a knowledgeable reviewer would actually worry about — not trivial or invented ones (which waste space and insult the reviewer) and not silence where the obvious risk should be.Question 7. What makes an innovation claim strong rather than weak?
Answer
Specificity: name the specific new element and the specific advance it enables ("fully automated, which for the first time makes population-scale deployment feasible at near-zero cost"), ideally with "why now" and pilot evidence the novelty works. "Innovative" as a bare label is an assertion the reviewer must take on faith; show it, don't assert it.Question 8. Why does the chapter say "the needs section makes them care, the aims make them understand, the approach makes them believe"?
Answer
Because caring and understanding are necessary but insufficient — a reviewer can care about the problem and understand the goal yet not believe you can deliver, and belief is what funding requires. Everything in the approach (detail, evidence, pitfalls, timeline) serves belief.Question 9. For a program proposal, what operational questions must the implementation plan answer?
Answer
Who delivers the services (and are they qualified); how you'll reach the target population (recruitment/referral — the part that often fails); what exactly happens, how often, and for how long (dosage); where it happens (is the space secured); and what partners contribute and have they committed. A reviewer who can answer these believes you can run it.Question 10. Why is a realistic timeline more persuasive than an aggressive one?
Answer
Reviewers discount obviously over-optimistic schedules and read them as inexperience or telling them what they want to hear. A realistic timeline — slow recruitment ramps, slack for delays, sensible sequencing — signals competence (what's being scored) and sets honest milestones you can actually meet in your future progress reports.Question 11. How does innovation trade off against feasibility, and how do strong approaches manage it?
Answer
More novelty raises the reviewer's worry that it won't work; more proven safety risks looking incremental. Strong approaches pair genuine innovation with pilot evidence that the novel element works in their hands — offering the upside of innovation without the usual unproven-risk downside — or, if they can't yet show it works, acknowledge the risk via pitfalls-and-alternatives.Question 12. An applicant presents five pages of preliminary results and one page on the proposed work. What's the problem?