Subject Line: Why your partners don't recognize themselves in your reports (and how to fix it)
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
It's RPPR season. Or maybe you're writing a year-end narrative for a foundation grant. Either way, you're sitting in front of a partnership section that's supposed to capture what you accomplished together, and something feels hollow.
You know the work was good. You know the partnership moved forward. But the words on the page sound like... reporting. Generic. Distant. The kind of language that checks boxes but doesn't breathe.
Worse, you have this nagging suspicion that if your partner read it, they might not even recognize the collaboration you're describing.
This newsletter is for anyone who has written partnership content that technically satisfies requirements but fails to capture what actually happened. For PIs who want their partners to feel represented, not just mentioned. For project coordinators who know there's a better way but aren't sure how to find it.
Here's the uncomfortable truth: most partnership sections fail not because they lack information, but because they lack voice. Specifically, they lack your partner's voice. They describe what happened from a single perspective — yours — and that's exactly why partners read them and feel something is off.