The Partnerships Everyone Sees

Subject Line: The MOU that looked great on paper but meant nothing in practice

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 stared at a partnership section of a proposal and wondered whether what they were describing was actually real.

You might be a researcher trying to demonstrate broader impacts. You might be a program director building workforce pathways. You might be an evaluator trying to assess collaboration quality. Either way, you've seen partnerships that looked impressive on paper and delivered nothing in practice.

This guide is about building partnerships that have depth, not just surface. And the first step is recognizing what surface actually looks like.

A bit about where this comes from: I've spent fifteen years designing STEM partnerships and evaluating what makes them work. I've watched partnerships launch with fanfare and fade into vague quarterly updates. I've also watched partnerships that seemed modest at first transform institutions over time. The difference isn't resources or enthusiasm. It's design. And design starts with seeing the layers.

The Partnership Moment

The boardroom smelled of fresh coffee and possibility.

Twelve people sat around a polished table at a research institution. Board members had flown in from across the country: foundation leaders, industry executives, people who wrote checks and opened doors.

One board member leaned forward with the enthusiasm of someone who had just connected two dots that seemed obviously meant to be joined.

"We have all these researchers here," she said. "And we know high school teachers need better professional development. What if we brought them together?"

The concept was elegant. Her own foundation on the East Coast had been running teacher workshops in partnership with a museum and a local research university. Teachers would spend a week immersed in current science, then return to their classrooms inspired.

Heads nodded around the table. This was a problem worth solving. And here was an institution with world-class researchers, a public engagement mission, and a foundation leader offering to help fund the solution.

What could go wrong?

Under the Surface

Three floors below that boardroom, a team of engagement specialists had spent years building something careful: science festivals, researcher training programs, community partnerships. They had relationships with school district coordinators, state science teacher associations, the Department of Public Instruction. They knew the ecosystem.

They were not in the room.

When the directive came down, filtered through two layers of leadership, it arrived as a fait accompli. The two organizations should work together. A grant proposal would be written. The model could be replicated.

But the people who would actually do the work hadn't been asked the questions that mattered:

Does this align with anything we're already doing?
Do we have the relationships with local school districts to make this work?
What would we have to stop doing to start this?

Instead, they were handed a vision shaped by someone else's experience in someone else's context. An East Coast collaboration between a museum and a university, now being transplanted to a Midwest research hub with different infrastructure, relationships, and constraints.

The team began what would become months of spinning.

The Partnership Shift

This is a story about surface partnerships.

Surface partnerships are the visible layer: the MOUs, the letters of support, the advisory board memberships, the co-PI arrangements. They're the partnerships you can describe in a proposal, announce in a press release, photograph at a signing ceremony.

Surface partnerships aren't bad. They're necessary. You can't build depth without surface. But surface alone produces what I saw in that boardroom: enthusiasm without infrastructure, vision without implementation, partnerships that exist on paper but not in practice.

The team in that story ended up reorganizing, pulling people away from existing programs that had taken years to build. They had conference calls, shared documents, emails that multiplied like cells dividing. They reached out to experts who might contribute, dreamed of impacts that might be possible.

But "aware" and "intrigued" are not the same as "committed." And "consulted" is not the same as "designing together."

The grant opportunity had a deadline. As it approached, a quiet conversation happened. The East Coast partners decided to submit the proposal themselves. They would test the model in their own context first, with their own resources.

This was presented not as a failure, but as a strategic pivot. The idea wasn't wrong. It was just ahead of its infrastructure.

The Partnership Pattern: Garbage Phrases and the Booking Agent Trap

When partnerships lack depth, you hear specific language. I call them garbage phrases.

You've heard them:

"This partnership is amazing because our organizations share such a strong commitment to STEM education."
"We couldn't imagine not working with them because their values align so perfectly with ours."
"The collaboration has been incredibly valuable for both sides."

These phrases sound positive. They fill space in reports and presentations. They give the impression that something meaningful is happening.

But listen to what they don't say:

They don't describe specific outcomes.
They don't identify what each partner uniquely contributes.
They don't explain how the partnership is different from what either organization could do alone.
They don't articulate how success would be measured.

Garbage phrases are a symptom. They emerge when the actual "why" was never developed, or when it was developed once and then forgotten as the partnership became routine.

When you hear someone describe a partnership using only adjectives, ask yourself: what's the verb? What does this partnership actually do?

The other pattern I see repeatedly is what I call the booking agent trap. This happens when partnership activities become routinized to the point where logistics dominate and purpose fades.

Picture a science center buzzing with activity. A visiting researcher sets up a demonstration. Middle schoolers cluster around tables. A staff member rushes between two programs simultaneously, clipboard in hand.

The staff member has a master's degree in museum education. She understands scaffolding, age-appropriate content, formative assessment. But today, she's functioning as a booking agent. She booked the scientist the way you might book a comedian for a comedy club: find an available slot, confirm the date, send a reminder email, make sure the microphone works.

The researcher prepared his demonstration without any input from the education team. He doesn't know what the students have already learned, what curriculum standards matter to their teachers, or what follow-up opportunities might exist.

This is partnership logistics without partnership purpose. The event happens. The photos get taken. The reports get filed. But the design intelligence that could make the experience transformative gets left on the sideline.

Try This: The Layer Audit

Before you write your next partnership description, do a quick audit. For each partnership in your portfolio, ask:

Surface Layer:

Do we have a formal agreement (MOU, letter of support, advisory role)?
Can we describe this partnership in a proposal or press release?
Would someone outside our organizations recognize this as a partnership?

Structural Layer:

Do we have institutional infrastructure supporting this partnership (research office support, compliance processes, space allocation, administrative coordination)?
If key personnel left, would the partnership survive?
Are there multiple touchpoints between our organizations, or just one relationship?

Systems Layer:

Does this partnership connect to broader networks or initiatives?
Are there feedback loops that allow the partnership to evolve?
Does this partnership create opportunities that neither organization could access alone?

If you can only answer "yes" to the surface layer questions, you have a surface partnership. That's not necessarily bad. But it's incomplete.

The Partnership Layer Mapper tool that accompanies this issue helps you visualize your entire partnership portfolio across these three layers. Most people discover they have more surface partnerships than they realized, and more depth potential than they knew.

Your Team's Turn

If you're working through this with a cohort or team:

Which of your current partnerships are primarily surface? Which have structural depth? Which connect to systems?
Where do you see garbage phrases in your own partnership descriptions?
Can you identify a partnership that started as surface and developed depth over time? What enabled that development?

Your Local Action

Find someone at your institution who manages partnership infrastructure, not just individual partnerships. They might be in the research office, community engagement, or economic development. Ask them:

What partnerships have you seen that looked great on paper but didn't deliver?
What partnerships surprised you by producing more than expected?
What's the difference between the two?

The answers will reveal local patterns about what enables depth versus what produces only surface.

Continue the Journey

This is Issue 1 of Layered Partnership Design, a Team Guide about building partnerships that have depth, not just visibility.

Here's what I've learned: recognizing surface partnerships isn't criticism. It's diagnosis. Surface partnerships become problematic only when we mistake them for depth, when we write proposals as if they have infrastructure that doesn't exist, when we make commitments we can't keep because we haven't built the structural support to keep them.

Issue 2 goes underneath the surface to the structural layer: the institutional infrastructure that enables partnerships to actually work. Research office support, compliance processes, IRB agreements, data sharing protocols, space allocation. When the structure is strong, surface partnerships thrive. When it's weak, even great partnerships crumble.

The full Team Guide is eight issues, each building on the last: from surface to structure to systems, from institutional landscape to network activation, from cross-institutional design to partnership sustainability. It includes interactive tools, downloadable templates, and slide decks for team meetings.

But the next step is seeing the structure. That's where partnerships either find ground to stand on or discover they've been floating.

The One Thing

If you remember nothing else from this issue:

Surface partnerships aren't bad. They're just incomplete. The question isn't whether you have surface partnerships. It's whether you're building depth underneath them.

Some partnerships exist only at the surface layer and produce real value there. Board memberships, advisory relationships, letters of support. These matter. But proposals that describe surface partnerships as if they had structural depth, that promise implementation without infrastructure to support it, those proposals are telling stories that won't hold up.

The Layered Partnership Design framework doesn't ask you to eliminate surface partnerships. It asks you to see clearly which layer each partnership actually occupies, so you can build depth where it matters, acknowledge surface where that's appropriate, and stop pretending one is the other.

Layered Partnership Design is part of the STEMsaic Team Guide Collection.

Your institution's research development office and partnership professionals are your best local resources. The frameworks here come alive when you apply them with people who know your context.