The gap between mandate and machinery has a shape. After enough reps, you can see it coming.
These aren't the failures the trade press writes about. Nobody writes about initiatives that never quite launched, programs that technically exist but don't really run, or pilots that finished on paper and left nothing behind. Those are the ones I get called in on. After enough reps (startup, agency, foundation, vendor) four of them show up more than the rest.
“The plan assumed someone would build it.”
The most common one. A board approves a strategy. A council passes a program. A foundation commits a grant. Everyone celebrates. Then the strategy goes into a folder and the work of turning it into a functioning operation never actually starts.
I've seen it at startups that closed enterprise deals before they had the onboarding capacity to serve them. I've seen it in agencies that got budget for a new program without the hiring authority or procurement runway to stand it up. I've seen it at foundations where the grant cleared and the grantee assumed the foundation had an implementation plan, and the foundation assumed the grantee did.
If no one can answer that, the program doesn't exist yet, no matter what the vote count was.
“The old process got copied into the new system.”
Particular to modernization work, and the most expensive kind of failure because everyone thinks it's a success until they realize it isn't. A legacy system gets replaced. The new platform goes live. The KPIs look clean. But six months in, nothing has actually gotten better, because the broken processes the old technology had calcified got faithfully reproduced in the new one. The tech changed, but the work didn't.
The tell is usually in the RFP. If the requirements document was written by the people whose job is to protect the existing process, the modernization will deliver exactly what it asked for, which is the problem. The real work of modernization isn't the migration. It's refusing to rebuild the bad processes the old technology was hiding. That refusal is political, not technical, which is why most modernization vendors avoid it.
“The coalition held until the first handoff.”
Urban work requires coalitions (agencies, vendors, funders, community groups, operators) and coalitions are usually strongest the day they launch and weakest the day the first handoff happens. Someone leaves. A commissioner turns over. A grant cycle ends. An election shifts. The coalition was held together by three specific people and two of them are gone.
This hits foundations especially hard, because philanthropic initiatives often depend on a single program officer who personally convened everyone in the room. When that program officer moves on, the coalition discovers it was a relationship, not an institution. The fix isn't "hire better people." It's building durability into the initiative from the start: explicit governance, documented commitments, institutional anchors that outlast the individuals.
“Everything runs through one person and that person is exhausted.”
The last pattern is the most human. A founder, an executive director, a commissioner, a program lead: someone has become the single point of coordination for a program that's outgrown them. Every question routes to them. Every decision waits for them. The organization is technically bigger than one person but operationally isn't. They know it. They'll tell you over coffee.
I've been that person. I've worked with that person. The fix is almost never what the person thinks it is. It's rarely a hire. It's usually a redesign of how decisions get made and information flows, so the person at the top isn't the only place context lives. They don't need another direct report. They need the system around them to work without them in every room.
They only get more expensive the longer you wait to fix them.