What NIH Reviewers Actually Look for in a Team Management Plan (And Why Most Miss It)
Your score needs to go up this time, but something about what your work is trying to do just isn't reading clearly to reviewers.
You've read the FOA three times. You're being responsive, to the best of your knowledge. You've looked at funded examples, you feel like you've got the right formula, and you've written and rewritten the sections about the working groups until you're reasonably sure it checks the boxes.
You ask yourself, “What am I missing here?”
What reviewers are actually looking for isn't evidence that you checked the boxes. It's evidence that your team has already solved the problem most multi-investigator grants fail to overcome. It’s not weak science, but collaboration liability.
The team management plan is your chance to prove you've solved it before they fund you. That you've already thought about where things are going to get hard and built the plan with that in mind.
THE PROBLEM BENEATH THE PROBLEM
I work with teams all the time who are looking at the same phenomenon from different units of analysis. A geospatialist, an infectious disease scholar, a pathologist. The perfect mix for studying malaria or coronavirus. And yet, what are the real barriers to combining data, finding an analytical pathway forward, or writing a paper together? What's bubbling up beneath the surface that could take the team down a year or two in? Have these been transparently addressed?
Simple images and figures that make collaboration architecture visible are what move reviewers. Over the years, I've watched a well-placed visual, one showing what integrated team structure actually looks like versus a siloed multi-investigator setup, how the people fit together, where the integration points are — do more for a convergence science score than another page of methods. Reviewers trust what they can see. No one else in this space is showing it.
WHAT THE PLAN ACTUALLY NEEDS
Prepare these five elements, even when the FOA doesn't explicitly ask for them.
Integration architecture. Not just who is on the team, but how the disciplines actually connect. Where the knowledge exchange happens. What the handoff points look like in practice, not in theory.
Decision ownership. Who decides what? How will disagreements get resolved? What happens when the science pulls in two directions at once, and both directions have a champion?
Credit and authorship clarity. How does a contribution get recognized? Whether junior team members are protected. Whether the structure actually incentivizes collaboration or just parallel work that gets listed as collaboration.
Conflict protocol. Not conflict avoidance, but readiness for it. Evidence that the team has named the friction points in advance and built a path through them. An advisory board sometimes does this work.
Leadership capacity. Not just a strong PI with numerous pubs and citations. Evidence that the team has the collective capacity to integrate across disciplines under pressure, a steering committee, a team scientist on staff, letters of support from an advocacy group. Together, these form a leadership body that holds the governance and structure when the PI is stretched.
THE ORGANIZING LENS
Draw on Integrative Capacity as the frame.
Capacity Within is the PI's individual leadership capacity, or their ability to hold the vision, manage the relationships, and keep the science moving when things get complicated.
Capacity Across is the team's integration infrastructure, the integrative mechanisms, such as cross-site meetings and shared agreements, that make genuine collaboration possible rather than assumed.
Both have to be present for a management plan to convince reviewers. A strong PI without integration infrastructure reads as a single-investigator grant with extra names attached. Integration infrastructure without strong PI capacity reads as a governance document nobody will actually use.
WHAT MOVES SCORES
The team management plan that moves scores isn’t about length, but about substance.
It's more honest about readiness, always showing reviewers a team that has already asked the hard questions. Not just the science questions, but the people ones. How do we make sure the collaboration is real and not just listed in biosketches and past publications?
That honesty reads as readiness. And readiness is what reviewers are actually scoring. They want an ROI and assurance that you’re the team that can deliver.
IF YOUR PLAN READS LIKE A COMPLIANCE DOCUMENT
It's not too late to make it an architecture document. That requires a different kind of writing, and it starts with a conversation your team probably hasn't had yet — about the hard parts, before the deadline, not after the score comes back.
That conversation is exactly what I help teams have.
Let me know if you want to talk.
