Who's This For
You've had good first conversations. You've mapped assets. The partnership feels promising. Now comes the part most researchers skip: having explicit conversations about what you each expect.
This issue is for faculty, PIs, and research administrators who've experienced partnerships that seemed solid until they weren't. Maybe you've watched misaligned expectations turn enthusiasm into frustration. Maybe you've been the partner who felt surprised by demands you never agreed to. Either way, you know that unspoken assumptions create problems down the road.
The Partnership Moment
You're three months into planning a major proposal. The partnership has felt easy. Every meeting ends with agreement. Both sides express enthusiasm. You're thinking: this is how partnerships should work.
Then you ask about timeline.
You need a commitment by next month for the proposal. They mention they'll need to run it by their board, which doesn't meet until the month after. You assumed the person you've been meeting with could make decisions. They assumed you understood their governance structure.
Or you discuss implementation plans. You describe the evaluation framework you've designed. They ask when they'll get to review it. You thought you were sharing a finished product. They thought they'd be involved in designing it.
Or you bring up intellectual property. They mention they'd want to use the curriculum you're developing in their other programs. You hadn't considered that the grant products might flow in directions beyond the original project.
None of these are conflicts. Not yet. They're misalignments. Places where you each assumed the other understood something that was never discussed.
Caught early, they're easy to resolve. Caught during implementation, they become the kind of tensions that end partnerships.
Under the Surface
Here's what creates these misalignments: the same optimism that makes partnerships feel good in early stages.
When conversations are going well, nobody wants to introduce friction. You're building rapport, finding common ground, getting excited about possibilities. Asking hard questions feels like it might break the spell.
So everyone assumes. You assume they have decision-making authority because they showed up to negotiate. They assume you'll involve them in design because you emphasized collaboration. You assume the timeline is obvious because it's driven by the proposal deadline. They assume they'll have more runway because their organizational calendar works differently.
Everyone's acting in good faith. Everyone's making reasonable assumptions. And the assumptions don't match.
The fix isn't to become suspicious of partners. It's to build expectation conversations into your partnership development process. Not because you distrust each other, but because explicit alignment prevents problems that implicit assumptions create.
