Why Your Research Team Falls Apart After the Grant Gets Funded.

You did the hard part.

You assembled the team.

You wrote the collaboration plan. You convinced reviewers that your interdisciplinary group had what it takes to do science that no single lab could do alone. The score came back. The funding came in.

And then — six months in — something shifted.

Meetings got tense. Credit became contested. A co-investigator went quiet. The shared vision that looked so clear in the aims page started fracturing along disciplinary lines.

The clinician and the engineer stopped talking directly. Everything now routes through you.

And it almost always starts before the grant is submitted. Why? Because the Research Plan Is Not a Team Plan.

Most NIH and NSF collaboration plans describe what the team will do together based on the biosketches. They almost NEVER describe how the team will actually function, how decisions get made, how conflict gets surfaced, how credit gets distributed, how disciplinary differences get bridged when the science gets hard.Reviewers reward the vision. Nobody evaluates the team infrastructure.

So teams get funded with a vision and no operating system. And the operating system only becomes visible when it breaks.

What Team Science Research Actually Shows

Research on multi-investigator teams consistently identifies two failure points that have nothing to do with the science itself.

The first is an integration deficit when the team members are coordinating, but not genuinely combining their expertise. Team members divide the work along disciplinary lines and report back to each other rather than building something new together. The grant looks collaborative. But, when taking a closer look, the science isn't really integrative

.The second is capacity imbalance when some team members are carrying disproportionate coordination load without formal authority or recognition. They become the glue. And glue burns out. Both conditions are predictable. Both are preventable. Neither shows up in a collaboration plan.

Now, let’s talk about what changes when you build the team before the work starts

The research teams that hold together through years two and three are the ones that produce the science that the multidisciplinary aims page promised. They tend to share a common pattern: they had the hard conversations before the submission deadline.

What problem are they really solving together?

Whose expertise counts when and why?

What happens when science takes an unexpected turn?

This isn't soft work. It's foundational work that allows the team to build. And it's the difference between a team that performs and a team that survives.

The Course Correction Question: Can the team be saved!?!

If your team is already funded — and already fracturing — it's not too late. But the intervention isn't a better meeting agenda or a team retreat. It's a structured assessment of where your team's integration is breaking down, and a clear plan to rebuild the operating infrastructure before the science suffers.

If you're still in the proposal stage, this is your window. The team management plan isn't a compliance document. It's your moment to build the very architecture your team will actually live inside for the next five years.

Build it like it matters.

Because it does.