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 ever written a sustainability section in a grant proposal and wondered whether any of it was true.
You know the formula. "The partnership will be sustained through continued institutional commitment, diversified funding sources, and embedded organizational processes." The language is familiar because everyone uses it. And everyone uses it because it's what reviewers expect to read.
The problem is that most sustainability sections are aspirational rather than designed. They describe what you hope will happen, not what you've built to ensure it happens.
This issue is about designing sustainability into partnerships from the start, not adding it as a section at the end.
The Partnership Moment
The partnership had run for seven years.
It connected a research institution with regional employers, placing graduate students in industry settings for transitional experiences. The model worked. Students gained practical skills. Employers developed talent pipelines. The research institution could point to career outcomes beyond academia.
Then the program coordinator retired.
Within eighteen months, the partnership had effectively dissolved. Not dramatically, not with conflict, but slowly. Fewer placements happened each cycle. Employer contacts went stale. Institutional knowledge about how the program worked disappeared with the person who held it.
No one had done anything wrong. The coordinator had been dedicated and effective. But the partnership had been designed around a person, not around a structure. When the person left, the partnership left with them.
This is the sustainability problem in its most common form: partnerships that work because of specific individuals, and fail when those individuals move on.
Under the Surface
Sustainability isn't a section at the end of a proposal. It's a design principle embedded from the start.
When I look at partnerships that outlast their original circumstances, they share common features:
Redundancy at every layer. Not just one PI relationship, but multiple touchpoints between organizations. Not just one administrative champion, but distributed structural support. Not just one funding source, but diversified resources.
Embedded institutional processes. The partnership activities don't require special effort to maintain. They're built into normal organizational operations. The data collection happens through existing systems. The coordination happens through standing meetings. The reporting serves multiple purposes, not just partnership accountability.
Documented knowledge. What the partnership does, how it works, why decisions were made, all of this is written down somewhere that survives personnel transitions. Not in a filing cabinet, but in accessible, maintained documentation.
Renewal mechanisms. The partnership doesn't just persist. It adapts. There are regular check-ins, health assessments, opportunities to recalibrate. Stagnation is recognized and addressed before it becomes fatal.
When I look at partnerships that fail to sustain, they share different features:
Single points of failure. One person holds all the relationships. One funding source covers all the costs. One organization does all the coordination. When that single point fails, the partnership fails.
Bolt-on activities. The partnership activities are additions to normal operations, not integrated into them. They require sustained special effort that eventually can't be maintained.
Undocumented expertise. Key knowledge lives in people's heads. When those people leave, the knowledge leaves.
No adaptation mechanism. The partnership operates the same way it was originally designed, even as circumstances change. Eventually the original design no longer fits the current reality.
