Week 7: The Team You Build Is the Argument You Make

Last week, I walked you through the program officer conversation — when to reach out, what to ask, and how to frame it as a collaboration rather than a petition.

Now I want to talk about the part of the resubmission that most researchers underestimate. Not the aims. Not the methods. Not the response to reviewers.

The team.

I have watched strong applications score poorly because the investigative team did not match the science. And I have watched mediocre ideas get funded because the team configuration told reviewers everything they needed to know about feasibility before they finished reading the first aim.

Your team is not a staffing list. It is an argument. And reviewers read it as one.

What reviewers actually evaluate when they look at your team

Under the Simplified Review Framework, team composition lives in Factor 3 — Expertise and Resources. It is not numerically scored the way Importance and Rigor and Feasibility are. Reviewers make a sufficiency assessment: are the investigators and environment appropriate for the proposed work, or not? But that binary framing understates its influence. In practice, a finding of "additional expertise and/or resources needed" signals to the room that the team cannot execute the science — and that signal shapes the overall impact discussion in ways that reach well beyond a single factor. The team may not carry a numerical score, but it carries weight.

A team that maps precisely onto the aims tells a reviewer that you have thought carefully about what each component of the science requires. A team that looks like it was assembled from existing relationships rather than scientific need tells a reviewer that you may not have.

This is a quiet evaluation. Reviewers rarely write "the team does not match the science" in those words. What they write instead is "concerns about feasibility," or "unclear whether the investigative team has sufficient expertise in [specific area]," or "the collaborative structure is not well articulated." These are team critiques wearing methods language.

If your summary statement flagged feasibility and you are planning a resubmission, look at your team before you look at your methods section. The methods may be sound. The problem may be that the people responsible for executing them did not convince the reviewers they could.

The three team problems that sink resubmissions

The first is the gap. Your application proposes a mixed-methods aim, but no one on the team has a track record in qualitative research. You propose a community-engaged approach, but the team is entirely academic. You include a biostatistician, but their expertise is in a different analytic tradition than what your design requires. Reviewers see these gaps immediately — not because they are looking for flaws, but because they are asking themselves a simple question: if this is funded, would these people be able to do it?

The second is the name. This is the one nobody talks about honestly. Someone is on your team because of a relationship — a mentor, a department chair, a collaborator who helped you before and expects to be included. Their name may carry weight in the field. But their expertise does not map onto what the application needs. Reviewers notice when a co-investigator's biosketch does not connect to any specific aim. They may not penalize it explicitly, but it introduces noise into an evaluation where clarity is everything. Every person on the team should have a reason a reviewer can see.

The third is the architecture. Your team has the right people, but the roles are not defined in a way that tells reviewers how the collaboration will actually function. Who leads what? How do the co-investigators interact? If you have a multiple PI structure, what is the scientific rationale for shared leadership — and what is the leadership plan if the PIs disagree? Reviewers have seen enough collaborative grants dissolve into administrative confusion that they are looking for evidence you have thought about governance, not just expertise.

Rebuilding a team for resubmission

Here is where it gets uncomfortable.

A resubmission sometimes requires changing your team. Not just adding someone to fill a gap the reviewers identified — that is the easy part. Sometimes it means having a conversation with someone who was on the original submission about why their role is changing or why they are no longer the right fit.

This is one of the hardest conversations in academic science. It sits at the intersection of professional judgment, personal loyalty, and institutional politics. And I am not going to pretend there is a formula that makes it painless.

What I can tell you is this: the conversation is always better than the avoidance. Keeping someone on a team because you do not want to have the conversation — and then watching the application score poorly again for the same feasibility concerns — serves no one. Not your science, not your career, and ultimately not the relationship either.

When you need to change a team member's role, be direct about what the summary statement said and what the resubmission requires. Frame it as a scientific decision, because it is one. Most colleagues will understand that a resubmission demands a different team configuration than the original submission — especially when you can point to specific reviewer critiques that support the change.

And when you need to add someone new, approach it with the same specificity. Do not ask someone to "be on your grant." Tell them exactly which aim their expertise supports, what their role would entail, and what the timeline looks like. The best collaborators — the ones whose involvement actually strengthens an application — want to know that their contribution is defined and meaningful, not ornamental.

The consultant question

One decision that comes up frequently in resubmissions is whether to add a new team member as a co-investigator or a consultant. This is not just a budget line distinction. It signals different things to reviewers.

A co-investigator is someone whose expertise is essential to executing the science. Their role is continuous. They appear in the leadership structure. Their biosketch is part of the application's argument for feasibility.

A consultant is someone whose input is needed at specific, bounded moments. An external methods expert who reviews your analytic plan. A content specialist who advises on instrument development. A collaborator whose role is real but circumscribed.

The mistake I see is using the consultant designation to include someone whose contribution is actually at the co-investigator level — usually to avoid the budget implications or the complexity of a subcontract. Reviewers can see this. If someone's expertise is woven through multiple aims and their contribution spans the full project period, calling them a consultant undercuts your own feasibility argument. It tells the reviewer that a critical piece of the science is being treated as optional.

Match the designation to the reality of the role. If you need someone deeply, make them a co-investigator and build the budget around it. If you need them episodically, a consultant is appropriate and reviewers will read it as such.

When the team critique is really a you critique

There is one more version of the team problem, and it is the one that requires the most honesty.

Sometimes the feasibility critique in a summary statement is not about who is on the team. It is about the PI. The reviewers may not say this directly — "the PI is not ready for this scope of work" is a sentence that rarely appears in a summary statement. But it lives underneath language like "limited preliminary data from the PI's own lab," or "the PI's track record does not yet demonstrate experience with [specific method or population]," or concerns about the PI's percent effort relative to the scope of the aims.

If the critique is really about your own readiness, the response is not to add more people. It is to either scale the work to match where you are now, or to invest in the preliminary data and experience that would make the next submission credible. This is where the program officer conversation from last week becomes especially valuable — a good program officer can help you distinguish between "you need a stronger team" and "you need a stronger foundation before this mechanism is the right fit."

This is also where the Lost In Translation curriculum was designed to help. The self-assessment framework in Module 7 walks you through evaluating whether the gap between your current position and your proposed work is something a team can bridge — or something you need to close yourself first. It is one of the more uncomfortable exercises in the curriculum. It is also one of the most useful.

The team as a living document

Here is the principle I want to leave you with.

Your research team is not a fixed entity that you assemble once and defend forever. It is a living argument that should evolve as your science evolves. The team for an R21 is not the team for the R01 that follows it. The team for a first submission may not be the right team for the resubmission. And a team that was perfect three years ago may no longer reflect the direction your work has taken.

The investigators who sustain funded research programs over time are the ones who treat team-building as an ongoing scientific decision — not a social obligation, not a political calculation, not a fixed roster. They ask, for every submission: who does this specific science require? And they have the courage to let the answer change.

That courage is not about being ruthless. It is about taking your science seriously enough to give it the team it deserves.

What is one team decision you made — or avoided — that changed the trajectory of a submission?

Next week: the revision itself — how to restructure an application that needs to change without losing the science that reviewers valued. The architecture of a resubmission that reads as stronger, not just different.

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

Lost In Translation grantsmanship curriculum is available as an institutional cohort for cancer centers, training programs, and research-intensive departments. The Founders 5-week live session Cohort launches in August, and an October cohort is open to individual researchers who want the cohort experience outside of an institutional partnership. Applications for the August and October cohorts are live. Contact lisa@soultosoulleadership.com.