Case Study 2 — A Graduate Student's First Fellowship Aims Page
Composite, for teaching. Sam and the fellowship are illustrative; verify current NIH fellowship guidance with the agency.
The Situation
Sam Okonkwo (composite) is a third-year doctoral student writing a first NIH predoctoral fellowship (F-series) application. Sam has a dissertation project but only modest preliminary data — a common, anxiety-inducing situation for early applicants. Sam's instinct is to compensate for thin data by writing an ambitious aims page that promises a great deal, hoping breadth will impress. This chapter warns that breadth is exactly the wrong move.
Applying the Chapter
The feasibility tension is acute for a student. A fellowship reviewer knows Sam is early-career with limited data, and is therefore especially alert to overreach. Sam's draft has four broad aims spanning more than a dissertation could deliver. Applying the scope test (significant? feasible? independent?), Sam finds the aims fail on feasibility — they cannot all be done in the project period with the available preliminary support. The fix is counterintuitive for an anxious student: cut, not add. Sam reduces to three focused, clearly feasible aims, each backed by what little preliminary data exists or by well-established methods. The page becomes more convincing by promising less.
Preliminary data does double duty. Sam has one small pilot result. Rather than burying it, Sam features it in the premise: "Preliminary data from [small pilot] show [specific result], supporting the central hypothesis and demonstrating feasibility of the key method." Now the modest data is working hard — it grounds the hypothesis and warrants that Sam can execute the aims. The chapter's point lands: preliminary data is not just support for the idea, it is the evidence of feasibility that makes a student's aims believable.
The hook is framed for the mission. Sam's first draft opened with general background on the disease. Revised, it opens with a specific, mission-relevant gap that the dissertation addresses, immediately answering "why does this matter and why is it unsolved?" Even a student's first page must open an argument, not a textbook.
The fellowship twist: the applicant is part of the case. Unlike an R01, a fellowship funds a person's training. So Sam's aims page, while following the standard structure, is also implicitly arguing that this project is the right vehicle for Sam's development — feasible enough to complete, rigorous enough to train strong skills, significant enough to launch a career. (The full training-plan dimension is developed in Chapter 27.) Sam keeps the aims tightly scoped partly because a fellowship reviewer wants to see a project a student can actually finish and learn from.
The Payoff
Sam's anxiety pushed toward an impressive-looking, over-broad page; the chapter pushed toward a focused, feasible, well-grounded one. The focused version is far stronger: three independent, achievable aims, a hook that opens an argument, and a premise that turns one modest pilot into evidence of both credibility and feasibility. Sam learns the lesson that surprises most first-time applicants — on the aims page, the discipline of less is a strength, not a confession of weakness.
Discussion Questions
- Sam's instinct was to compensate for thin data with ambitious breadth. Why does that instinct backfire, especially for an early-career applicant?
- How does preliminary data function differently in a fellowship aims page than the applicant initially assumed — what are its two jobs?
- Compare Sam's situation to Dr. Hernandez's (Case Study 1). Both revised toward focus and independence, but for partly different reasons. What is the same lesson, and what is fellowship-specific?