Key Takeaways — Chapter 9: The Project Narrative / Research Approach
-
The approach answers "can you do it?" — the hardest reviewer question, and where credibility is won or lost. The needs section makes them care, the aims make them understand, the approach makes them believe. Strong significance dies here if the plan is vague, overreaching, or naive.
-
Balance credibility and readability with strategic detail: deep on the critical and risky parts, summary on the routine. Avoid the "wall of methods." The details you choose to emphasize reveal whether you know where the real risk is.
-
Structure by aim/objective so the section is navigable and visibly delivers each promise (coherence, Ch 5). For programs, include a concrete implementation plan (who delivers, how you reach the population, what/how-often/how-long, where, partner contributions).
-
Show feasibility, don't assert it. Deploy preliminary data (research) or track record + evidence-based model (programs) exactly where the reviewer's doubt is strongest. Calibrate: enough to convince, not so much the approach becomes a results section.
-
Pre-empt your weaknesses (threshold concept). Name your two or three genuine risks and give a specific contingency for each. A disclosed-and-addressed weakness builds trust and removes the reviewer's ammunition; a hidden one the reviewer finds reads as naivety or evasion. Find your real risks by having a colleague play skeptic.
-
State innovation specifically — the new element, the advance it enables, and "why now" — ideally paired with pilot evidence it works. Manage the innovation-vs-feasibility tension; don't assert "innovative," show it. If incremental, lean on other strengths honestly.
-
Include a realistic timeline with milestones. It signals competence (over-optimism signals inexperience), and its milestones become your future progress-report markers (Ch 26) — promise a schedule you can keep.
Common Mistakes
- The "wall of methods"; equal detail on everything.
- Hiding weaknesses instead of addressing them.
- Vague innovation claims; an approach that's really a results section.
- A vague program narrative (a hope, not a plan); an over-optimistic timeline.
Decision Framework — Is your approach ready?
(1) Does it deliver every aim, structured so the reviewer can see it? (2) Is the detail strategic? (3) Is feasibility evidence placed where the doubt is? (4) Have you named and addressed your genuine risks? (5) Is the innovation specific and the timeline realistic? Any "no" is your next revision.
Your Project
You should now have an approach structured by aim, with strategic detail, feasibility evidence placed against doubt, a pitfalls-and-alternatives passage, a specific innovation statement, and a realistic timeline with milestones — checked against your aims (delivers each?) and previewing the budget (every activity costed?).