Case Study 1 — Daniel's Specific Aims Page, Annotated Line by Line

A composite, fictional-but-realistic walkthrough. Dr. Daniel Reyes is an early-career principal investigator writing her first independent grant. We watched the full before/after in §17.3; here we slow down and annotate the revision itself — sentence by sentence — so you can see each move doing its job. This is the page that, in the chapter's story, got her work scored well enough to fund.

The revised page, with a reviewer's-eye margin notes

Specific Aims

[1] Gram-negative bacteria resist our last-line antibiotics largely by pumping the drugs back out before they can act, and the AcrAB-TolC efflux system is the workhorse of that defense.

Margin note — the hook, sentence 1. No field history. The very first sentence states the problem mechanism in plain language a reviewer feels immediately. "Last-line antibiotics" signals stakes; "pumping the drugs back out" is a concrete image, not jargon for its own sake. A tired reviewer is already oriented.

[2] Block the pump, and resistant bacteria become vulnerable again — but no efflux-pump inhibitor has ever reached the clinic, because existing candidates are too toxic or too weak.

Margin note — the gap, arriving fast. Sentence 2 does double duty: it states the opportunity (block the pump → restore the drugs) and immediately names the gap (none has reached the clinic, and why). By the second sentence the reviewer knows the problem, the prize, and what's missing. Compare the draft, which spent its first 90 words on textbook background.

[3] A safe, potent pump inhibitor would restore the activity of antibiotics we have already lost.

Margin note — stakes, crystallized. One short sentence that makes the payoff vivid: not "improve treatment" but "restore antibiotics we have already lost." This is the significance promise, planted early, to be redeemed at the bottom of the page.

[4] We have found one.

Margin note — the pivot. Three words. The shortest, hardest-hitting sentence on the page, and deliberately so. After the gap ("none exists"), this lands like a turn in a story. Reviewers remember this sentence; some quote it in their critiques. This is BLUF (Ch 4) operating inside a paragraph — the bottom line, up front, unmissable.

[5] In a screen of 50,000 compounds, we identified FX-11, a small molecule that inhibits AcrB at sub-micromolar concentrations and restores ciprofloxacin sensitivity in resistant E. coli by 32-fold (preliminary data, Fig. 1) — with no measurable toxicity to human cells at effective doses.

Margin note — preliminary data as proof. The claim "we found one" is instantly backed by numbers: 50,000 compounds (scale → rigor), sub-micromolar (potency), 32-fold (effect size), no toxicity (the exact thing that killed prior candidates), and a figure reference. This single sentence pre-empts the reviewer's reflex — "prove it" — before they can finish the thought. Note the calibrated tone: every claim here is a result, stated flatly, because Daniel has the data.

[6] We hypothesize that FX-11 restores antibiotic efficacy by binding the AcrB drug-binding pocket and arresting the pump's conformational cycle.

Margin note — the hypothesis, stated outright. The draft never had one. Here the central bet is explicit and mechanistic, which makes the aims that follow feel like a test of an idea rather than a list of chores. Tone shifts correctly to hedged ("we hypothesize") — this is a prediction, not yet a proven fact.

[7] This proposal will establish how FX-11 works, whether it potentiates antibiotics broadly, and whether it is effective in vivo — the three things that must be true before it can become a drug.

Margin note — the aims, previewed in one sentence. Before listing the aims, Daniel tells the reviewer the logic connecting them: mechanism, spectrum, in vivo — "the three things that must be true before it can become a drug." Now each aim has a reason to exist, and the reviewer can see the whole arc in one line.

[8] Aim 1. Determine how FX-11 binds and inhibits AcrB. Using cryo-EM and binding assays, we will test the hypothesis that FX-11 occupies the distal drug-binding pocket and locks the pump's resting state. Expected outcome: a structural mechanism that explains the inhibition and guides optimization.

Margin note — objective, method, outcome. Objective-first (Determine), method named briefly (cryo-EM, binding assays), expected outcome stated. A reviewer sees the question, the test, and the deliverable at a glance.

[9] Aim 2. Establish the spectrum of antibiotic potentiation. We will test FX-11 in combination with five antibiotic classes across a panel of 30 resistant clinical isolates to determine which drug–bug combinations it rescues. Expected outcome: a defined potentiation profile identifying the most promising therapeutic pairings.

Margin note — independence. Crucially, Aim 2 does not depend on Aim 1 succeeding. If the structure proves hard to solve, the potentiation panel still runs and still delivers value. A single failure can't sink the project — a quiet signal of an experienced design.

[10] Aim 3. Test whether FX-11 restores antibiotic efficacy in vivo. In a murine thigh-infection model, we will determine whether FX-11 plus ciprofloxacin clears resistant infections that ciprofloxacin alone cannot. Expected outcome: proof-of-concept efficacy and a preliminary therapeutic window.

Margin note — the highest-stakes aim, also independent. In vivo proof-of-concept is what a reviewer most wants to see promised. It stands alone, and its expected outcome ("therapeutic window") speaks the language of where this could go next.

[11] Together these aims will deliver the mechanism, the spectrum, and the first in vivo evidence for a new class of antibiotic adjuvant — the foundation for developing FX-11 toward a therapy that reclaims antibiotics resistance has taken from us.

Margin note — the payoff. The closing redeems the promise from sentence 3. It names exactly what the field gains (mechanism + spectrum + in vivo evidence for a new class) and ends on the vivid stakes ("reclaims antibiotics resistance has taken from us"). The reviewer finishes able to state, in one sentence, what Daniel proposes and why it matters — which means they can advocate for it in the panel.

What the annotation teaches

Read the eleven sentences as a sequence and you can feel the engine: problem → opportunity → gap → pivot → proof → hypothesis → aim-logic → three objectives → payoff. Nothing is decorative. Every sentence either orients the reviewer, earns their trust, or tells them what they get.

Now recall the draft Daniel started with. It had the same science — the same molecule, the same three experiments. What it lacked was all of this: it opened with background experts already knew, buried the discovery in hedged mush, never stated a hypothesis, showed no data, phrased the aims as activities, and closed with throat-clearing. The science didn't change between draft and revision. The writing about the science did, and that is the entire difference between a page that gets triaged and a page that gets funded.

Try it yourself. Take Aim 1 in the draft — "We will characterize the binding of the small molecule to the efflux pump" — and, covering the revision, rewrite it as an objective-first aim with a method and an expected outcome. Then compare. The hardest part isn't the wording; it's that the strong version forces you to commit to a hypothesis and an expected result the weak version let you dodge. That commitment is the thinking the page exists to extract from you — Chapter 1's thesis, on the highest-stakes page you'll write.

Back to: Chapter 17 · Case Study 2 · Exercises · Key Takeaways