When $400 Million Buys Nothing
Why Program Management Isn't Optional
Nearly $400 million a year goes toward homeless services in Multnomah County, home to Portland, Oregon. Yet over the same period that spending has ramped up, unsheltered homelessness has quintupled. Hundreds of people still die on the streets every year. Mental illness and addiction also remain largely untreated.
This isn’t a story about compassion fatigue. And it isn’t a story about underfunding.
This is a story about systems failure.
Dr. Sharon Meieran, former county commissioner and emergency physician, recently published a turnaround plan for the county. This plan reads less like a dense political document and more like a critical diagnosis.
Not because she’s importing corporate jargon into government.
Because she’s putting a name to structural breakdowns that program management was invented to prevent.
Core Dysfunction
Here’s what she identifies:
Money is dispersed across departments with no clear line of sight
Authority fragmented, no real chain of command
Budgets based on history and inertia rather than strategy and results
No outcome data proving that anyone moves from crisis to stability
Overlapping programs quietly consume hundreds of millions
Sound familiar?
This isn’t unique to Multnomah County. It’s what happens anywhere programs multiply faster than the structure holding them together.
What Program Management Actually Does
Program management is the art of making complex efforts behave like a single system.
It defines who owns what.
It clarifies decision rights.
It ties money to outcomes.
It forces integration across silos.
Without it, programs multiply. Accountability diffuses. Results drift.
Look at what Meieran proposes. You’re not seeing political reform. You’re seeing structural correction…
Integration over Fragmentation
She proposes consolidating eleven departments into five integrated hubs.
Not for aesthetics. Not for optics.
Because when homelessness services sit in one department, mental health in another, addiction treatment in a third, and housing support in a fourth, each operating independently, you don’t have a system.
You have parallel efforts crashing into each other.
Real program management forces integration. It defines ownership. It clarifies decision rights. It establishes governance that crosses silos instead of pretending silos don’t exist.
Without that structure, you get what Multnomah County has now: duplication, contradiction, gaps and no one accountable for the whole.
Outcomes over Activity
The county tracks bed nights, meals served, case management hours. All activity metrics. None of them answer the only question that matters: are people actually moving from crisis to stability?
Program management forces that question.
It requires defining success in concrete terms, instrumenting for it, and tracking progress with discipline. Not just what was done, but what changed.
Meieran proposes zero-based budgeting, where every dollar must justify itself against a defined outcome. It’s not a budgeting tweak. That’s a full accountability shift. It exposes what’s working, exposes what isn’t, and makes visible what many organizations prefer to leave ambiguous.
Most institutions resist this not because it’s complicated, but because it’s clarifying.
Without it, you’re not managing. You’re just hoping it all works out.
Systems Thinking over Siloed Solutions
Homeless services don’t operate in isolation. They intersect with behavioral health, public safety, healthcare, housing policy, and economic development. When each function operates independently, incentives fracture, policies contradict, and resources collide.
Program management introduces system-level oversight. It creates decision-making authority that spans departments. It forces conflicts into the open before they metastasize.
Without that perspective, programs optimize for their own metrics, and the larger outcome degrades.
That’s how you end up with people cycling through services, helped in pieces, but never stabilized as a whole.
Structural Sustainability over Personality-Dependent Results
Meieran also points to chronic management turnover and authority concentrated in a single elected office with limited structural accountability.
This is the heroic leader trap.
An organization that functions only when the right individual happens to be in charge doesn’t have strength. It has a dependency.
Program management builds durability into the structure itself. Clear roles. Defined authority. Governance mechanisms. Performance systems that persist beyond personalities.
Leadership still matters, but it operates within guardrails with results that don’t collapse every time a seat changes.
Why Organizations Resist This
If program management prevents exactly the failures Multnomah County is experiencing, why isn’t it standard practice everywhere?
Because it forces clarity where ambiguity has been comfortable.
Program management makes constraints visible. It requires organizations to…
Admit they can't do everything
Acknowledge when things aren't working
Make painful choices about resource allocation
Accept accountability for outcomes instead of hiding behind effort and good intentions
It's psychologically easier to add another program, hire another manager, or fund another pilot than to ask whether the existing architecture is fundamentally broken.
Until the dysfunction becomes undeniable.
What This Actually Looks Like in Practice
Most organizations reading this are not managing a $400 million public services budget. But the same structural failures show up whether you’re running a mid-sized nonprofit, a city department, or a company trying to coordinate across business units.
Here's what to actually watch for and what to do about it.
If you have a growing program portfolio without integration mechanisms...
You know you're here when someone asks "who's responsible for X?" and the answer is either "everyone" or a list of three departments. Or when programs keep getting added but nobody can explain how they fit together.
Start by mapping what you actually have. Not the org chart—the real structure of who does what, where money flows, and where handoffs happen (or don't). Most organizations are shocked by what this reveals. You'll find programs that were supposed to sunset three years ago still running, initiatives that have completely drifted from their original purpose, and at least one critical function that everyone assumes someone else owns.
Then ask the uncomfortable question: if you were designing this from scratch today, knowing what you know now, would it look anything like this?
If not, you're managing technical debt. And like software technical debt, the longer you wait to address it, the more expensive and painful it becomes.
The fix isn't always consolidation. Sometimes it's clarifying boundaries and decision rights. Sometimes it's killing sacred cows that haven't delivered in years but consume resources and political capital. Sometimes it's admitting that Program A and Program B are fundamentally incompatible and you need to choose.
Whatever it is, it requires someone with enough authority to actually make changes and enough courage to piss people off. Because you will piss people off.
Every organizational structure creates winners and losers, and the current structure has incumbents who benefit from the confusion.
If you're measuring activity instead of outcomes...
This is the easiest trap to fall into because activity is so much easier to measure. You can count workshops delivered, clients served, grants awarded, meetings held. These numbers always go up, which makes everyone feel productive.
But here's the test: can you explain, with actual data, how your organization's work changes the state of the world? Not how busy you are, not how many people you touched—what actually changed for them?
If you can't answer that, you're probably tracking the wrong things. And worse, you're creating a culture where effort substitutes for impact.
The fix starts with outcomes mapping. For each major program or service line, complete this sentence: "A person is better off because of our work when _______________."
Then figure out how to measure that thing, even imperfectly.
Even if it means surveying people six months later, or tracking administrative data you don't control, or admitting you can't really measure the thing you claim to do.
You'll find that some programs can't articulate what success looks like beyond activity. That's useful information. Either clarify the outcomes or question why you're doing it.
And yes, some things are genuinely hard to measure. Advocacy work, prevention activities, systems change—these don't lend themselves to clean metrics. But "hard to measure" isn't the same as "impossible to assess." If you can't describe what evidence would convince you the program isn't working, then you've created an unfalsifiable proposition.
That's religion, not management.
If you have siloed departments with unclear handoffs...
This manifests as client ping-pong ("we referred them to Department B but they sent them back"), chronic coordination meetings that accomplish nothing, or programs that inadvertently undermine each other.
The underlying issue is usually that each unit is optimizing for its own metrics without regard for the overall system. Department A cares about throughput, Department B cares about compliance, Department C cares about cost containment. Nobody is accountable for the end-to-end outcome, so you get exactly what you'd expect: sub-optimization and finger-pointing.
The solution requires cross-functional governance—not another coordinating committee, but actual decision-making authority that spans silos. This might be a program director with budget authority across departments, a steering committee with real teeth, or a complete reorganization around outcomes instead of functions.
Whatever structure you choose, it needs three things: clear decision rights (who can actually say yes or no), consequences for non-cooperation (not just appeals to collegiality), and visibility into the whole system so problems surface before they become crises.
You'll know it's working when conflicts get resolved quickly instead of escalating into turf wars, when units start proactively sharing information that helps the overall effort even if it makes them look bad, and when people stop optimizing for their silo's metrics at the expense of the mission.
If success depends on specific Individuals…
This is the "hit by a bus" test, and most organizations fail it spectacularly.
If your star program director leaves, does the program collapse? If your integrator, who knows everyone and makes everything work, retires, does coordination fall apart?
Organizations love to celebrate heroic individuals who make things happen despite the system. The problem is that this reveals that your system doesn't actually work.
You're succeeding in spite of your structure, not because of it.
The fix is embedding what your high performers do into the overall system.
Document the relationships they maintain, the informal processes they use, the judgment calls they make. Then figure out how to ingrain that capability into roles, processes, and systems that persist when they leave.
This doesn’t eliminate the need for strong people. It removes fragility.
And if you can’t build that durability into the structure, you should question whether you’re running a program or relying on someone’s charisma.
The Deeper Point
Here's what's really going on with Multnomah County, and probably with your organization too: everyone is working hard, most people genuinely care, and the organization is still failing at its core mission.
That's not a people problem. That's a systems problem.
You can't hire your way out of systems problems. You can't inspire your way out. You can't add another initiative, form another task force, or write another strategic plan and expect different results.
At some point, the structure itself has to change.
That means changing how authority is defined, how decisions are made, how money flows, and what gets measured and rewarded. This is unglamorous work. It doesn’t photograph well for annual reports. But it's the only thing that actually moves the needle.
Meieran's plan works because it applies rigorous program management thinking to a systems failure. The principles—integrate, measure what matters, budget for results, account for every dollar—aren't novel. They're foundational. And their absence is predictably catastrophic.
The real question isn't whether your organization needs program management discipline. It's whether you're willing to accept what that discipline reveals about your current operations, and whether you're willing to do the hard work of fixing it.
Most organizations aren't. They'd rather add another program, adjust the strategy, or wait for better leadership. Which is why most organizations end up like Multnomah County: spending more every year and getting worse results.
Structural Correction Isn’t Strategy
Most organizations think they have a strategy problem.
They rewrite plans. Adjust priorities. Add initiatives. Hire stronger leaders. But execution still drifts because the issue wasn’t strategy.
It was always structure.
When ownership is unclear, work diffuses. When authority is fragmented, decisions stall. When outcomes aren’t defined, performance becomes interpretive. Complexity expands faster than control.
That does not resolve with another initiative.
It resolves with structural correction.
Big Left examines that structure. We assess where accountability breaks down, where authority conflicts, and whether disciplined project management would change the trajectory.
If you want a serious evaluation before adding anything else, start there.
Pick your flavor: submit a project inquiry or schedule a strategic working session
