The examples in this newsletter are drawn from real partnership experiences. Names and identifying details have been altered to protect privacy.
Who's This For
I'm writing this for anyone who has watched a partnership fail not because of bad intentions but because of missing infrastructure.
You've secured the letters of support. The advisory board is enthusiastic. Leadership has given the green light. And then the partnership stalls because research compliance takes six months longer than the project timeline allows. Or because no one can figure out who pays for the student transportation. Or because the shared data requires agreements that don't exist yet.
This issue is about the invisible layer that makes visible partnerships possible: structural partnerships.
The Partnership Moment
The proposal read beautifully.
A partnership between a research institution and a regional technical college would create workforce pathways for biotechnology careers. Students would gain hands-on experience in working laboratories. Industry partners would mentor the next generation. Evaluation would document the model for replication.
The letters of support arrived on time. The budget balanced. The logic model connected activities to outcomes. Reviewers praised the integrated approach.
Then the award came through. And everything started to unravel.
The IRB at one institution required full protocol review for any student interaction. The other institution's IRB had never processed a collaborative agreement with that first institution. The timeline said "data collection begins month 3." The IRB coordination, once actually attempted, would take until month 9.
Space allocation that seemed straightforward in the proposal turned complicated when the facilities team pointed out that student access required security clearances, insurance documentation, and supervisor agreements that didn't exist.
The budget assumed a .25 FTE coordinator position. But when the hiring process began, both institutions discovered that their personnel policies treated joint appointments differently. Neither HR department had a clear process for what the proposal described.
This is what happens when surface partnerships try to operate without structural support. The enthusiasm was real. The need was real. The failure was structural.
Under the Surface
Structural partnerships are the institutional infrastructure beneath the visible layer: research office support, compliance processes, IRB agreements, data sharing protocols, space allocation, administrative coordination.
When the structure is strong, surface partnerships thrive. When it's weak, even great partnerships crumble.
Most proposals I review underestimate structural complexity in predictable ways:
Compliance timelines get compressed. Proposals assume IRB approval, data use agreements, and MOU finalization happen quickly because they've never watched these processes in detail. A multi-institutional IRB protocol can take 6-18 months. Proposals often allocate 6-8 weeks.
Capacity gets assumed. Proposals describe activities that require specific personnel or resources without verifying those resources exist. "The partner will provide laboratory space" sounds simple until you discover the space requires renovation, shared access policies, and insurance adjustments that weren't budgeted.
Administrative coordination gets hidden. Every partnership activity requires someone to handle logistics: scheduling, communication, documentation, troubleshooting. Proposals often describe activities without identifying who manages the coordination work or how they're compensated.
Decision-making authority gets blurred. Partnership activities require decisions. Who decides when students can access a facility? Who decides when to modify a program element? Who decides when partnership tensions require escalation? Without explicit governance, decisions get delayed or made inconsistently.
Reviewers have learned to read between the lines. When a proposal describes multi-institutional collaboration without addressing how IRB coordination works, reviewers notice. When the timeline assumes immediate implementation without onboarding or setup phases, reviewers wonder what's being overlooked.
