Week 5: The Three Doors

Last week, I walked you through how to read a summary statement — not for emotional confirmation, but for strategic intelligence. How to distinguish observations from concerns from foundational critiques. How to find the signal in reviewer disagreement.

Now comes the harder question. What do you do with what you found?

You have three options, and only three. You can revise — take the same application, address the critiques, and resubmit it. You can reframe — keep the science but fundamentally restructure how the application presents it. Or you can walk away — redirect your energy toward a different project, a different mechanism, or a different question entirely.

Most investigators treat this as a single decision: resubmit or don't. But "resubmit" contains two very different paths, and choosing the wrong one is how strong scientists waste a cycle.

When to revise

A revision is appropriate when the core argument of your application held. The reviewers understood what you proposed. They found the research important. Their critiques were about execution — the analytic plan, the sampling strategy, the power analysis, the timeline, the feasibility evidence. These are concerns about Rigor and Feasibility, and they live in the specifics.

The tell is convergence. If two or three reviewers raised the same methodological concern, and the Resume captured it, the room agreed that your approach needs strengthening in a specific, identifiable place. That is a revision. You know where the problem is. You know what kind of fix it requires. And you can make the fix without dismantling the architecture of the application.

A revision also applies when a critique reflects a communication failure rather than a design flaw. If a reviewer wrote that your rationale for the intervention was "not well articulated," go back to what you actually wrote. Is the rationale there but buried? Is it implicit where it needed to be explicit? Did you assume the reviewer would connect dots that you needed to draw for them?

Communication failures are the most common reason applications score lower than the science deserves. They are also the most fixable — but only if you recognize them for what they are. The temptation is to add more science. The fix is usually to say what you already know more clearly.

When to reframe

A reframe is necessary when the critiques are not about your methods but about your premise.

This is harder to see, because premise-level critiques do not always announce themselves as such. A reviewer might write that the "conceptual basis for the intervention is underdeveloped" or that the "significance of the proposed work is not clearly established." Those sound like they could be fixed with a stronger paragraph. They usually cannot.

When reviewers question your premise, they are telling you that the foundational argument — why this research matters, why this approach is the right one, why this question is the one to ask right now — did not land. That is not a paragraph problem. That is an architecture problem.

A reframe means stepping back to the level before structure. It means returning to the question underneath the application: What am I actually trying to do, and what is the clearest, most honest case for why it matters? [If you have done the Coffee Conversation exercise from Module 1 of the Lost in Translation curriculum, this is when you return to it — not to your last draft, but to your plain language version of the science.]

In practical terms, a reframe often means rewriting the Specific Aims page from scratch. Not editing it. Starting over. Because the Aims page is where your premise lives, and if the premise did not hold, editing around the edges will produce an application that looks revised but reads the same.

A reframe may also mean changing the mechanism. If your summary statement suggests that reviewers found the scope too ambitious for the preliminary data you have — or too narrow for the mechanism you chose — the issue may not be the science. It may be the container. An R01 that should have been an R21. An R21 that was really an R34. Module 11 of the curriculum addresses this directly, but the summary statement is often where the mismatch becomes visible for the first time.

When to walk away

This is the one no one wants to talk about.

Walking away does not mean giving up on your science. It means recognizing that this particular application, for this particular mechanism, at this particular moment, is not the right vehicle for what you are trying to do.

There are several signals. The most important one is when the foundational critique in your summary statement is something you agree with — not something you want to argue against, but something that, when you sit with it honestly, reflects a real limitation in the current state of your work. Maybe you do not yet have the preliminary data to support the scope you proposed. Maybe the team configuration does not match the complexity of the aims. Maybe the question itself has shifted since you wrote the application, and what felt urgent six months ago no longer feels like the right next step.

The other signal is when the critiques across all three reviewers point in fundamentally different directions. If one reviewer wants more mechanistic depth, another wants a stronger community engagement rationale, and the third questions whether the population is the right one to study — that is not a coherent set of instructions for revision. That is an application that did not give the room a stable foundation to evaluate. Trying to address three divergent critiques simultaneously usually produces an application that satisfies none of them.

Walking away from an application is not walking away from your research program. Sometimes it is the thing that saves it.

The resubmission introduction

If you decide to revise or reframe, the introduction to your resubmission is the first thing reviewers will read — and it sets the tone for everything that follows.

Most resubmission introductions read like one of two things: a defense or a capitulation. The defense argues with the reviewers, explaining why their critiques were wrong or based on a misunderstanding. The capitulation accepts every critique without distinction and lists the changes made in a way that signals compliance rather than scientific judgment.

Neither serves you.

A strong resubmission introduction does something specific: it demonstrates that you understood the critiques, exercised judgment about which ones required substantive changes, and made those changes in ways that strengthened the science — not just addressed the feedback. It is responsive without being defensive. It is specific without being exhaustive. And it is brief.

Reviewers do not want to read a four-page point-by-point rebuttal. They want to know, in a page or less, that you heard them, that you thought carefully about what they said, and that the application they are about to read is better because of it. The introduction should make the reviewer want to read the rest — not feel like they already have.

One practical guideline: address convergent critiques first and most substantively. If all three reviewers raised the same concern, lead with how you resolved it. If one reviewer raised something the others did not, a sentence or two of acknowledgment is usually sufficient — especially if the Resume did not capture it as a panel-level concern.

Do not use the resubmission introduction to argue with a critique you disagree with. If a reviewer misunderstood something about your design, the fix is not to explain in the introduction why they were wrong. The fix is to rewrite the relevant section of the application so that the next reviewer cannot misunderstand it. Then note in the introduction that you "clarified" or "revised" that section. Let the application do the arguing.

The decision underneath the decision

Here is the thing I want you to carry with you.

The resubmission decision is not really about the summary statement. It is about whether you still believe in the question. Not whether the reviewers believe in it — whether you do.

If you read your summary statement and your first instinct is to fight for the application — not out of ego, but because the science matters and you know how to make it clearer — that is information. That is the energy a resubmission requires, and it is not something you can manufacture.

If you read your summary statement and feel relief that someone finally named the thing you have been sensing but could not articulate — that is information too. It does not mean you failed. It means the application taught you something about your own thinking that you could not have learned any other way.

Either response is honest. Either one can lead to funded science. The only response that does not serve you is the one where you resubmit out of obligation — because you feel like you should, because your department expects it, because you have already told people you would — without genuinely believing the next version will be stronger.

A resubmission is not a second chance. It is a new argument. Make sure you have one.

Next week: the program officer conversation — when to reach out, what to ask, and what they can and cannot tell you.

~Lisa Carter-Bawa, PhD, MPH, APRN, ANP-C, FAAN, FSBM

Lost in Translation is available as an institutional cohort for cancer centers, training programs, and research-intensive departments. Contact lisa@soultosoulleadership.com.