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
You're six months into a funded project, and something is off. Not catastrophically wrong - nobody's walking away - but the careful plans you outlined in your proposal aren't mapping to reality the way you thought they would.
Maybe your industry partner restructured and the champion you worked with is now in a different role. Maybe the student participants you expected to recruit aren't materializing at the numbers you projected. Maybe the timeline that seemed reasonable when you were writing at your desk feels impossible now that you're actually doing the work.
And somewhere in the back of your mind, there's a voice saying: We're supposed to report on this. What do we say?
This newsletter is for anyone navigating the gap between what you proposed and what's actually happening. It's for PIs, project managers, partnership coordinators - anyone who has opened their proposal document, looked at what they promised, and felt that particular tightening in their chest.
Here's the thing: this gap is normal. It's so normal that the best funders build expectations for it into their frameworks. The NSF calls it "adaptive management." Program officers expect it. The question isn't whether your project will need to adapt - it will. The question is whether you'll navigate that adaptation in a way that strengthens your partnership and your credibility, or whether you'll pretend everything is fine until report time.
The Partnership Moment
Picture this: You're on a call with your community partner. You were supposed to launch a professional development series together last month, but it hasn't happened. Their staff person who was coordinating got pulled onto another priority. Your faculty co-PI had a family emergency. The dates you planned around a district calendar shifted when the district changed their training schedule.
None of this is anyone's fault. All of it means you're behind.
Your partner says something like: "So what should we tell the funder?"
And you pause. Because you don't know.
You could minimize it. "We're still on track overall." That's technically true - the overall goals are still achievable - but it ignores the fact that the timeline you proposed is now impossible.
You could explain it away. List all the reasons why things changed. But that sounds like excuses, and you've read enough reviewer comments to know how that lands.
You could say nothing yet and hope things get better. But report time is coming, and the gap is only going to be harder to explain the longer you wait.
Here's what I've learned from watching partnerships navigate this moment well: the ones that survive don't have fewer challenges. They have better language for framing challenges as learning.
Under the Surface
Here's what most people miss about adaptive management: it's not about putting a positive spin on problems. It's about genuine metacognition - being explicit about your design assumptions and how reality is teaching you something different.
When you wrote your proposal, you made assumptions. You assumed your partner organization had certain capacity. You assumed timelines would hold. You assumed people would stay in their roles and priorities would remain stable. You assumed your model of how the work would unfold was accurate.
Some of those assumptions were wrong. That's not failure - that's implementation teaching you something.
The shift is from framing setbacks as failure to framing them as expected iterations. When you wrote the proposal, you knew it was an initial design. You knew reality would require adjustment. You just didn't know which adjustments would be needed.
The best proposals actually build this expectation in explicitly. They use language like: "We anticipate our plan will move through iterations of forcing functions." They describe structural redundancy - multiple partners, multiple pathways, multiple people in each role - so when any one element shifts, there's continuity. They name the duality of roles for continuity, the cohort and mentorship structures, the buffer built into timelines.
If your proposal didn't include that language, you can still adopt the mindset. The key is being explicit about what you anticipated, what you learned, and how you're adapting. Not as apology. As methodology.
