When Strategies Miss the Street: Lessons from the Frontlines of Public Development

I’ve sat in boardrooms with carefully crafted strategic plans. I’ve facilitated roundtables with ambitious frameworks. I’ve led capacity-building workshops where whiteboards filled with arrows and visions and buzzwords. I’ve also stood—often in the same week—in under-resourced municipal offices, crowded refugee classrooms, and behind-the-scenes moments that never make it into a log frame.

After more than a decade of working across governance, public development, and international programs in Jordan and Palestine—with trips and trainings across the U.S., Europe, and the UK—I’ve learned this: strategy is necessary, but it’s never enough.

The realities on the ground always speak back.

Sometimes they whisper; sometimes they scream.

The Misalignment Between Planning and People

In one city, we had a brilliant civic engagement strategy. Pages of activities, timelines, KPIs. But in a key meeting, a woman from a local neighborhood committee quietly said, “We don’t need another awareness campaign. We need streetlights.” That sentence still echoes in my head.

Our data didn’t show that. Our frameworks didn’t ask about that. But she was right.

That moment taught me: development isn’t always about doing more. It’s about listening better.

When Everything Looks Right on Paper

I’ve worked with municipalities, ministries, and NGOs across Palestine and Jordan. Each time, the funding cycles bring their own logic: design the intervention, tick the boxes, and show the outcomes. But behind every “success story” is a public employee working overtime with no pay increase, a young community activist whose energy is spent navigating bureaucracy, or a program that makes numbers but doesn’t move hearts.

One example? We once celebrated meeting every indicator in a youth empowerment project. But in the closing workshop, a participant stood up and said: “You taught us about leadership, but didn’t trust us to lead anything.”

Ouch. She was right, too.

What I’ve learned from Moving between Worlds

I’ve traveled across continents and sectors—from Amman to London, Bonn to Colorado. The policies shift, the jargon changes, but the core truths stay the same: if you don’t include the people closest to the problem in the solution, you’re planning for them, not with them.

Higher education can learn a lot from this.

We teach planning. We grade strategy. But how often do we ask students or young professionals to reflect on what planning misses? Do we talk about ego in leadership? About the power dynamics in donor meetings? About what happens when your “stakeholder map” doesn’t include the gatekeeper at the front desk who actually controls access?

These aren’t just implementation details. They’re where strategy lives—or dies.

A Call for Slower, Smarter, More Human Planning

I’m not anti-strategy. Quite the opposite. I’ve spent years writing them, training teams to execute them, and aligning them with national plans. But I believe we need to widen the lens.

Can we teach adaptive strategy—not just linear plans?

Can we make room for pause in fast-moving programs?

Can we normalize feedback that doesn’t come in surveys, but in hallway conversations and honest exits?

Can we see “success” as more than reports and more like relationships?

If I Could Rewrite One Thing

If I had the chance to go back to the beginning of my career, I wouldn’t rewrite a single strategy document. I’d rewrite the conversations we had before writing them.

I’d start by asking:

What are people already doing, quietly and effectively?

Who hasn’t spoken in this room yet?

What does success feel like—not just look like?

I’m now in a new role in higher education. I coordinate an international digital learning program between Jordan and German partner universities. It's early, and I’m learning every day. But I carry these lessons with me. Every call, every plan, I ask: Are we building something that fits the system, or something that can serve the people?

There’s a big difference.

We need both, yes. But if we forget the second, the first becomes just a PDF.