Infrastructure Theater

We learned to say the word. We never learned to build the thing.

If you’ve been to a progressive funder convening in the last three years, you have heard some version of this sentence: “We’re building the infrastructure for long-term change.” It is in every deck, every docket, every theory of change. Somewhere along the way it became the password.

There is a name for what the word now covers. Infrastructure theater. It is what happens when an organization learns to say the word, perform the posture, and raise money against the promise of permanence without ever building the thing that lasts. The language of building laid over the operational reality of impermanence. Once you have the name, you start seeing it everywhere in the field.

I want to be honest about a gap, because it has a face and the abstractions hide it. We have no cultural home for the young man who watches every game, whose truck payment went up under the tariffs, who, when it is his turn to cook, puts three or four different meats on a smoker and not one vegetable in sight. Just smoke and fire and his boys around him. That man is not our enemy. He is economically ours to win, and we have nowhere to put him. No room he’d walk into, no role that would fit him, no one whose job it is to know his name. We talk about building infrastructure for a generation and we have not built the one thing that would actually reach him: a place to belong before anyone asks him for anything.

He is the sharpest case, not the whole of it. The same gap swallows the young woman who stayed with us and got handed a clipboard instead of a future. But he is the one who walked, and he shows the hole most clearly.

That is what this is really about. Not the org charts and the grant cycles, though we will get to those. The reason all of it matters is that somewhere there is a bridge we keep saying we’re building, and he is standing on the far side of a river we never spanned. The honest version is not that we lack the will to reach him. It is that we do not know how to build the bridge.

I have spent more than a decade inside this sector, building organizations, raising the money, signing the grant reports. So this is not a critique from the outside. But it is not a confession either. It is a diagnosis, and the subject is not any one organization. It is what the field as a whole has built under the banner of infrastructure, and why so little of it holds weight.

For a while the word meant something real. Infrastructure was a rebuke. It was the organizing sector saying: we’re done with short-burst mobilization, done shutting down after every election cycle, done being treated like a tactical vending machine. We want to build something that lasts. That argument was correct and it needed to be made loudly. But somewhere between the argument and the funding, the word stopped doing real work. Now “infrastructure” is what an organization calls itself when it does not want to be held accountable for outcomes. It is the sector’s most elegant escape hatch, and infrastructure theater is the show it pays for.

Anyone who has actually built one of these organizations knows what the absence underneath the word feels like. One person who is the strategist and the operations and the back office at once, learning the rules in real time, signing things there is no time to read, holding together something growing faster than anyone knows how to build it, because there is no one else and nothing in place that says there should be. That is what the absence of infrastructure feels like from the inside. It is not a missing line item. It is a house held together in a storm with tape and willpower, and called building because there is no other word for what is happening.

WHEN THE WORD DOES EVERYTHING, IT MEANS NOTHING.

Take the metaphor literally. Imagine someone comes to you and says they’re building a bridge. You get excited. A bridge is important. You invest. You check in a year later, and you find a field full of lumber, some concrete mix, and a 12-person team, six of whom are still in conversations about what kind of bridge this should be, three of whom are writing grant reports about the bridge they’re going to build, and two of whom are doing community listening sessions to understand the community’s relationship to bridges in general.

Nobody has drawn a blueprint. Nobody has assessed the load requirements. No one is certified to pour that concrete. There is no site inspector, no structural engineer, no project manager tracking what goes where and in what order.

Is that building infrastructure? Or is that infrastructure theater, performing the idea of building while the lumber rots in the field?

That is a lot of the sector right now. And the reason it keeps happening isn’t bad intentions. It is that the field has never gotten serious about what each person on that team is actually supposed to be doing.

WHAT INFRASTRUCTURE ACTUALLY REQUIRES

Real infrastructure is not a philosophy. It is a set of functions, performed by specific people with specific skills, in a specific sequence. The theater version has a cast. The real version has a crew with roles.

Construction needs architects. In organizing terms, these are the strategists who can look at a political landscape and design a structure that will hold weight over time. Not just “we want civic power,” but: here is the architecture, here is why the load goes here, here is what will fail first if we get this wrong. Architects are not generalists. They have a specific and technical skill. Most organizations have zero of them. What does that absence look like in practice? It looks like a network that has been “expanding” into new states for four years but has no coherent theory of which states, in what sequence, building toward what concentration of power. It looks like program decisions made by whoever is in the room, because there is no one whose job it is to hold the design. It looks like organizations that are responsive but never strategic, always reacting to the political moment, never building ahead of it.

Construction needs construction workers. People who are not thinking about the design anymore, they are executing it. In organizing, these are the experienced field directors and lead organizers who know how to move, how to build a base, how to convert a relationship into a vote or an action or a leader. The sector consistently underpays and undervalues these roles, hires people who are too green, and then wonders why the structure doesn’t hold.

Construction needs inspectors. People whose entire job is to check the work, catch the flaws before they become failures, and say “this doesn’t meet spec, fix it before we go further.” In organizing, this is evaluation, learning, and accountability infrastructure. Not annual reports for funders. Not vanity metrics. Actual quality control. Almost nobody funds it. Almost nobody builds it.

Construction needs a foreman. Someone coordinating all of these people, tracking dependencies, making decisions about sequencing. Not the visionary, not the funder relationship, not the public face, the person making sure the work actually flows. The sector calls this role “operations” and treats it like overhead. It is not overhead. It is the thing holding all the other things together.

There is a reason underneath all of this that is bigger than any single organization, and it is uncomfortable to say out loud. You cannot assign roles on a project when no one agrees on what is being built. And for about a decade now, the movement has not agreed on what it is building. It has agreed only on what it is against.

Ask a room of organizers and funders and operatives what it means to be a progressive right now, what the movement is for, what the country actually looks like when it wins, and you will get ten answers, most of them gauzy. Ask what it is against and the room answers in one voice. The movement has spent ten years defining itself by Trump. He has been its organizing principle, its fundraising engine, its turnout model, and its entire theory of who it is. Anti-Trump is not an identity. It is a reflex. And you cannot draw a blueprint out of a reflex.

This is why the architect role stays empty. An architect translates purpose into design. If the purpose is only “stop him,” there is nothing to design, there is only something to react to. A wrecking crew and a construction crew are not the same thing. You can assemble enormous energy to tear something down, and the field did, and then find that the crew it built does not know how to build, because building was never the point. The opposition gave the movement scale without direction. It told it where to point. It never told it what to make.

So the role confusion is not only a talent problem or a funding problem. It is a clarity problem that runs all the way to the top. When the highest level of a movement cannot say what it is for in plain language, every level beneath it inherits the same fog. The organizer does not know what they are organizing toward. The inspector has no spec to check against, because no one ever defined the standard. Everyone is busy. No one can tell you what finished looks like. And a project where no one can say what finished looks like is the perfect set for infrastructure theater, because there is no way to tell the performance from the real thing.

The metaphor breaks somewhere, and it has to be named, or the rest of it stops being trustworthy. A bridge has fixed physics and a known endpoint. The engineer knows the far shore before anyone surveys the ground. Organizing does not work like that. What is being built, and who it is for, is contested, and it often only becomes clear through the work itself. The listening sessions mocked earlier are sometimes exactly that, the work of figuring out what the structure is even supposed to do. So a fair critic could say that “blueprint first, then build” smuggles in a top-down knowability that organizing is supposed to resist. That critic would be partly right.

But here is what the metaphor still gets right. We do know the far shore. This bridge ends, eventually, in some measure of liberation: a community that can govern itself, exercise power, and not live at the mercy of whoever happens to hold office. We may not be able to draw every span before we start. We may be building part of it while standing on it, revising the route as the river moves underneath. That is the real condition of the work, and the organizing tradition already has a name for it. We make the road by walking.

What that does not excuse is formlessness. Not knowing the exact route is a different thing from not knowing how to build. You can hold the destination loosely and still be rigorous about the craft. You still need someone who can read the ground. You still need people who know how to pour concrete. You still need a sequence, even if it gets revised twenty times. “We are adaptive” is true, and it is also the most common cover story for “we never got serious.” The discipline lives in the how, not in pretending there is certainty about the where. The lumber rots in the field whether or not you know your endpoint.

THE FUNDING TRAP.

Here is the cruel irony. The people who convinced funders to invest in infrastructure made a compelling case by pointing to the long-term, diffuse, hard-to-measure nature of the work. And then the funding they won, because it is still philanthropic capital, still comes with one-to-three-year cycles, deliverable expectations, and a preference for organizations that can point to a finished product.

The pattern is familiar by now. Organizations spend almost ten years “building infrastructure” and come out the other end with no rooted base, no durable relationships with local institutions, and no staff who have been through multiple cycles of the work. What they have is a database, a logo, a board, and a story about what they’re going to build next.

So you get organizations that say “infrastructure” in every deck but build to the funding timeline. You get the lumber, but not the bridge. You get the org chart, but not the roles filled by people who actually know what they’re doing. You get the language of permanence and the operational reality of impermanence. The funding trap is what keeps the theater running, because it pays for the performance and never has to sit in the seats long enough to see whether anything got built.

And here is what makes this trap so durable: it protects everyone except the communities it is supposed to serve. The organization gets the grant. The program officer gets the portfolio win. The foundation board sees the language of long-term investment without having to wait long enough to see whether it worked. Nobody is formally accountable when the bridge doesn’t get built, because “infrastructure is long-term” and long-term is very hard to inspect. That is not a bug in the system. That is the system working exactly as designed, for everyone sitting at the table who isn’t from the community.

THE TALENT PROBLEM NOBODY WANTS TO SAY OUT LOUD.

Infrastructure requires skilled labor. Every year, progressive organizations collectively hire more than a thousand fellows, bright, motivated, politically aligned young people who spend a year learning the basics of the work. Some of them are exceptional. And at the end of that year, there is almost nowhere for the exceptional ones to go. No apprenticeship track. No journeyman pathway. No organization saying: we saw what you can do, here is a two-year commitment to turn you into a real organizer. Instead, the best of them scatter, into grad school, into advocacy jobs, into communications roles, into whatever is hiring, because the infrastructure to absorb them into a serious, long-term organizing career simply does not exist. The field runs an enormous top-of-funnel and a nearly empty pipeline. You cannot build a movement on a rotation of 22-year-olds at $48,000 a year who leave after 18 months because nobody ever told them there was a next step worth staying for.

The sector talks about pipeline and next-generation leadership constantly. What it does less often is sit with the fact that it has almost no mid-career infrastructure. There is entry-level and there is executive. There are people new to the work and people who have been doing it so long they have very little energy left. The skilled journeyman layer, the people who know enough to execute without constant oversight but aren’t yet burned out, is almost entirely absent in most organizations.

You cannot build infrastructure without skilled tradespeople. Full stop.

Here is the part that should sting, because the other side does not have this problem, and the reason they don’t is that they decided not to. The Leadership Institute has been training conservatives since 1979. One organization, one continuous program, more than four decades without interruption. It runs on roughly forty-five million dollars a year, offers dozens of types of training, and has put more than two hundred thousand people through its doors. And it does not train them and wave goodbye. It runs a standing job placement service for the entire movement, a pipeline that takes the people it trained and moves them into campaigns, congressional offices, statehouses, and newsrooms. More than five hundred sitting state legislators came through it. They built the apprenticeship, the journeyman track, and the placement office that our side keeps saying it wants and never funds.

Their model is not ours, and that is worth saying plainly. A pipeline that trains candidates and staff and places them in jobs is more legible and more fundable than the relational base-building this piece is about. It is the easier lift. Which is exactly why it is so damning that the field has not made it. If the other side can sustain a forty-year institution for the part that is straightforward to fund, the failure to build even that for organizing is not a resource problem. It is a choice the field keeps making.

And the difference is not money in the abstract. The progressive side moves real money too. The difference is that they treat leadership development as permanent infrastructure and the field treats it as a grant cycle. They are not nickel-and-diming the thing that makes everything else possible. They funded a forty-year institution whose entire job is to guarantee there is always a next generation that knows how to do the work, and a place for that generation to go. The field funds a fellowship, runs it for a year, congratulates itself on the size of the top of the funnel, and lets the bottom leak out into grad school. One side is building a pipeline. The other is running a turnstile.

There is a cost underneath the empty pipeline that the sector never books, and it lands hardest on the people most often asked to do the building. The journeyman layer is thin partly because the money runs out. It is also thin because the ecosystem has learned to extract from BIPOC leaders exactly what it will not invest in them. It wants their faces on the strategy and their credibility in the community, and it funds their organizations at a fraction of what it hands the white-led ones doing less, on shorter leashes, with more reporting and less trust. It asks them to build the thing and to take the punches at the same time. The funder who calls the work visionary and the leader difficult. The board that wants the proximity but not the authority. The raise that lands a year after a white hire got it for the same job. Most of it leaves no mark anyone else can see, which is the second job, proving the hit was real before you are allowed to be tired from it, then walking back in the next morning steady and grateful, as if the cost were not real because no one funded a line to measure it.

That is not a wellness footnote. It is a structural reason the building does not hold. A field that recruits BIPOC leaders for their credibility, underfunds them against their white peers, taxes them for the discomfort of leading, and then loses them to exhaustion every few years is not building a pipeline. It is mining one. It is running the turnstile by another name and calling the churn diversity. Retention is the whole game in infrastructure, the thing that lets an organization compound instead of restart, and a movement that treats the exhaustion of its builders as the cost of doing business has already decided, whether it will say so or not, that it is not building anything meant to last. If you want the journeyman layer to fill, fund the people who do the work at the level you fund everyone else, and stop spending them down faster than anyone could ever replace them.

WHAT THIS LOOKS LIKE IN PRACTICE.

It is easy to nod at this in the abstract and then go back to the lumber pile, so here is the concrete version.

Real infrastructure has an organizer-to-base ratio that makes sense for the kind of relationships the organization claims to build. It has documented processes that don’t live in one person’s head and don’t leave when that person does. It has a theory of how new staff become skilled, how skills transfer, how institutional knowledge accumulates.

Real infrastructure looks like sitting down in year one and building a training progression, not a one-time onboarding but an eighteen-to-twenty-four month arc that takes someone from canvasser to relational organizer to someone who can run a turf without supervision. It looks like writing that down, testing it, revising it when it doesn’t work, and having the next cohort benefit from what the last one learned. It looks like an organization that is measurably stronger in year four than in year one, not because it got more funding, but because it got smarter about how it develops people. Most organizations don’t do this because it takes time that isn’t billable to a deliverable. But it is exactly the difference between an organization that compounds across cycles and one that starts over every time a grant ends.

Real infrastructure can tell you, in plain language, what it has built. Not “we convened,” not “we trained,” not “we have a presence in X counties.” What has changed in the community’s capacity to exercise power? Where does the work go when the grant ends? What can this place do that it could not do three years ago? If the answer is unclear, the organization is not building infrastructure. It is funding the performance of it.

Here is what it looks like when someone gets it right, even briefly. Year one: a handful of organizers, a defined geography, and a clear theory of which relationships matter and why. Not everywhere. Somewhere, on purpose. Year three: those organizers have run a full cycle, made mistakes, been coached through them, and come back stronger. There is a base that knows the organization by name and has taken action more than once. Year five: an organizer who started as a fellow stayed, because the organization made a concrete commitment, a real title, a living wage, a defined role with a future, and is now training the next cohort. The community can do something it could not do before, turn people out, hold an official accountable, win something local and concrete. That is infrastructure. It does not announce itself. It just holds weight.

There is an argument underneath all of this that the sector hasn’t fully reckoned with. A lot of what gets called infrastructure is being built inside organizational structures, c3s especially, that are constitutionally limited in the kind of power-building work that makes infrastructure meaningful. An organization can have a perfectly operational c3 with excellent staff, strong training systems, and a real base, and still be legally prohibited from doing the most important electoral and political work that would actually convert that base into durable power. The funding follows the c3 because it is easier, cleaner, and more palatable to institutional philanthropy. But the work that changes who governs often can’t live there. So the field builds infrastructure in the wrong container and then wonders why it doesn’t hold political weight when the moment comes. This is the conversation the sector keeps almost having and then retreating from.

THE ASK IS HARDER THAN THE FRAMING.

The reason “infrastructure” became a dodge is because the real thing is genuinely hard to build and genuinely hard to fund. It requires long timelines, high trust, tolerance for slower early progress, and a willingness to fund the roles that don’t show up in a press release.

But the word has become an absolution. It lets organizations avoid the question of what they are actually building, because “infrastructure” is definitionally about what comes later. And “what comes later” is very hard to inspect.

The correction isn’t cynicism about infrastructure. The correction is rigor about what infrastructure actually requires, and clarity about whether an organization is building it or just naming itself after it. For funders, that means longer commitments, five years minimum, not two. It means funding the foreman role, the inspector role, the unglamorous operational backbone that never makes it into a press release. It means asking grantees not just what they plan to build, but who specifically is going to build it, what they know how to do, and how the organization will hold that knowledge when that person eventually leaves. And it means being willing to sit with the discomfort of not having a clean deliverable to show your board at the end of year two, because that discomfort is exactly what real infrastructure requires of everyone in the room.

WHAT HOLDS WHEN THE STATE IS THE LOAD

There is a harder version of this question, and it is the one the moment is forcing on the field. Everything argued for so far, the blueprint, the rooted base, the documented processes, the legal status that lets the money move, quietly assumes a state that will leave you alone to build. It assumes the only things trying to knock the bridge down are time, funding cycles, and the field’s own sloppiness.

That is not the assumption anyone gets to make anymore. Under a government willing to investigate, defund, and shutter the organizations it does not like, every property that makes an organization strong is also what makes it a target. A bridge is legible by design. It has an address, a registration, a board, a bank account, a list of everyone who works on it. The same scale and permanence that lets a movement outlast any single person is the exact surface area an authoritarian state attacks first. So the question underneath the whole infrastructure debate changes again. It is no longer about time, or funding, or discipline. It becomes: what holds weight when the load on the bridge is the state itself?

For a decade the field argued about leaders versus organizations as a question of which one builds power more efficiently. That debate assumed a moment that would leave the winner standing. Strip that assumption out and it stops being an efficiency question at all. It becomes a survival question: which form lasts through a government that has decided to come for you? The organization, with its roster and its registration and its bank account, is the easier thing to find and freeze. A leader, a relationship, a culture of trust is harder to fund and harder to scale, and also far harder to shut down. None of this is new. The movements that actually survived repression tended to run on distributed cells, portable leadership, and deliberately illegible forms, and the state still went hardest after whatever was most registered and most visible. The case the field spent a decade making for durable institutions was built for a different moment than the one it is walking into. That does not make it wrong. It makes it contingent, and the field has not been honest with itself about that.

The answer is not to stop building. Cynicism about institutions is just another escape hatch. But it changes what good engineering looks like. Real bridges are designed with redundancy, so one failed span does not bring down the whole structure. Infrastructure for this moment means the same thing: distributed enough that no single node is load-bearing for the entire network, firewalls between entities, leadership and relationships that survive the org that held them. The boundaries the field used to treat as bureaucratic caution become a security strategy. Resilience, not just durability, becomes part of the blueprint, and it is the part no one has drawn yet.

Which means the ask to funders is only half-stated until this is added to it. Five years instead of two is still right. But a five-year bet on a single legible institution is also the easiest thing in the world for a hostile state to find and close. So the commitment has to get longer and more distributed at the same time. Fund the depth, the rooted base, the journeyman track, the operational backbone, and fund it across enough nodes that no single raid, no single revoked status, no single defunding letter takes the whole network down with it. Which is also why betting on people, portable and relational and hard to seize, is no longer the soft alternative to institutions but part of how institutions survive. Permanence and redundancy stop being competing values. In this moment they are the same instruction. The durable thing was never the biggest, most legible institution anyone could build. It is the network that keeps standing when the largest node falls.

WHAT IT WOULD TAKE

The blueprint matters. The roles matter. The sequence matters. You may not be able to draw every span before you begin. You may be building part of it while you stand on it. But you have to know which shore you are building toward, and you have to know how to build. The honest thing to admit is that wanting to reach the other side is not the same as knowing how, and that no amount of calling an organization a bridge will carry one person across.

None of this is beyond us. The movement knows how to do this work. It has done it. The pipeline got built once, by people who decided it mattered enough to fund for forty years and never blinked. The bridge gets built, somewhere, every season, every time an organization chooses depth over flash and stays long enough to mean it. The field was never short on talent. It was never short on conviction. It was short on one thing only, the decision to build like it intends to still be here when the work pays off. And a decision is not a fate. A decision is a thing that can be made differently, starting now, starting with the next dollar and the next hire and the next person someone refuses to let scatter.

So let this not be a eulogy for infrastructure. Let it be the moment the field stops performing infrastructure and starts building it. If you fund this work, commit past the next cycle. Fund the foreman. Fund the inspector. Ask the hard question of who, specifically, is going to build the thing, and do not accept a deck for an answer. If you run an organization, find the one role you have been faking, and this year, fill it. And if you are the young man at the smoker, or the young woman who got the clipboard, the place that was supposed to hold you was real. It was always supposed to be real. It just never got built. Some of us are building it now, and we are building it for you, and this time it reaches the far shore.

We make the road by walking. We have always made the road by walking. The only question left, the only one that has ever mattered, is whether this time the field stops the theater, picks up the tools, and walks it on purpose, together, all the way across.