The drive took about three hours each way.

A foundation on the eastern edge of a region had identified a priority: workforce development for youth, particularly summer programming that would connect young people with research careers. They had resources to deploy and a genuine desire to make an impact.

They also had a model that worked in their city, a mid-sized urban center with strong connections between industry, schools, and community organizations. Students built portfolios. They gained digital credentials. They developed relationships with mentors in STEM fields. The programs mapped to both credit opportunities and career pathways.

The question seemed reasonable: could this model be expanded? Could it be replicated at a larger research institution two hundred miles away?

Site visits were arranged. Documents were shared. Calls were scheduled. Everyone was polite and enthusiastic. The foundation leaders saw a major research institution with resources and reach. The institution's team saw a foundation with funding and connections.

What neither side fully grasped was how different their contexts actually were.

The foundation's home city had a population of roughly 200,000. The metropolitan area around the research institution had nearly seven times that. This wasn't just a difference in scale. It was a difference in kind.

In the smaller city, the foundation had spent years building relationships with specific high schools, specific employers, specific community organizations. They knew the curriculum coordinators by name. They understood the certification requirements. They had mapped the pathway from summer internship to college application to entry-level job.

The larger metro area had all of those elements too, but multiplied across dozens of school districts, hundreds of employers, thousands of community organizations. The research institution's existing programs were designed for different age groups. Their summer internships served undergraduate and graduate students, not high schoolers. Their workforce development partnerships pointed in different directions.

But in the site visits and the calls and the shared documents, these differences got smoothed over. Both groups talked about "STEM workforce development" and "building pathways" and "supporting underserved youth." The phrases matched. The realities didn't.

Eventually, a grant proposal had to be written.

This is where the dynamics shifted. A proposal requires specifics. It requires timelines, budgets, partner commitments, outcome measures. It requires someone to write down what will actually happen.

The team assigned to write the proposal found themselves documenting challenges more than opportunities. The geographic distances. The demographic differences. The mismatched program structures. The capacity gaps on both sides.

One section particularly stood out: the logistics. The proposal had to explain how staff from a research institution in one metropolitan area would regularly coordinate with school districts in a different metropolitan area two hundred miles away. It had to explain how a model designed for a mid-sized city would scale to a region seven times larger.

The explanations didn't hold together. And everyone involved knew it.

Someone finally said what everyone had been thinking: "We're writing about challenges more than opportunities. Maybe that's telling us something."