The activation problem: how movements respond at speed

In the early weeks of December 2025, Operation Metro Surge descended on the Twin Cities. Federal agents — thousands of them — fanned out across Minneapolis and Saint Paul, detaining workers, breaking into homes, and circling schools. The Department of Homeland Security called it "the largest immigration enforcement operation ever."

What they didn't account for was what had been quietly built in the years before they arrived.

Within twelve minutes of an ICE operation being reported at a manufacturing facility in St. Paul, trained community observers were on site. Within days, a coalition of over ninety immigrant, labor, faith, and legal organizations was coordinating a unified response. Within weeks, labor unions, community groups, and faith institutions had organized the largest coordinated work stoppage in Minnesota since the 1930s — what they called a "Day of Truth and Freedom" — drawing tens of thousands into the streets in temperatures as low as twenty below zero.

This didn't happen because Minnesotans got lucky with the timing. It happened because they had built the infrastructure for it — patiently, deliberately, over years — before they needed it.

That gap — between having a network and being able to move that network within 48 hours — is the activation problem. And it is the most dangerous gap in the current movement landscape.

The difference between a network and a deployable network

Most organizing groups have a network. They have email lists, contact databases, group chats, and social media followings. They have people who care and have said so.

What most groups don't have is activation infrastructure: the systems, roles, and practiced workflows that allow a network to move together — quickly, clearly, and without improvising everything from scratch in the middle of a crisis.

The distinction matters because crises don't wait for you to build capacity. Federal enforcement actions happen at dawn. Legislation advances on short timelines. The window for effective response to a breaking situation is rarely longer than 48 to 72 hours. If your infrastructure doesn't exist and function before a crisis, it won't function during one.

Think of it as muscle memory. The workflows, communication channels, and role assignments that are practiced in ordinary times are the ones that hold together under pressure. The ones built in a hurry, in the middle of an emergency, are the ones that fail at exactly the wrong moment.

What Minnesota had built

The rapid response network that mobilized against Operation Metro Surge didn't emerge in December 2025. The foundation it rested on had been under construction since the early 2010s.

Years of coalition alignment. Beginning in the 1990s and early 2000s, during a period of conservative governance in Minnesota, unions and community organizations started asking a different question: not "how do we win our individual campaigns?" but "who are our long-term allies, and what are we trying to build together?" That alignment was formalized in 2011 as Minnesotans for a Fair Economy, a collaboration of labor, faith, and community organizations large enough to want to fight for significant change but honest enough to recognize they couldn't do it alone. The same relationships were activated in December 2025 — now operating under new names and with new urgency, but built on fifteen years of trust and shared practice.

Trained observer networks. MONARCA — an arm of Unidos Minnesota — had been training community members as legal observers long before Operation Metro Surge. By the time the surge began, MONARCA had trained over 20,000 Minnesotans to observe federal immigration enforcement activities: when to document, how to de-escalate, what constitutional protections apply, and how to get information to families and legal teams quickly. When the rapid response line received a report of ICE activity, trained observers could arrive on-site in minutes — not because they improvised it, but because they had rehearsed it.

A coordinating network, not a single organization. The Immigrant Defense Network (IDN) didn't try to run every response itself. It functioned as an umbrella and coordination layer for ninety-plus organizations, each with their own relationships, resources, and geographic reach. When the surge escalated, IDN didn't have to stand up new organizations from scratch — it activated existing ones. The signal moved through pre-existing channels to groups that already knew their role.

Practiced communication protocols. Observers were equipped with secure, toll-free phone and texting options. Multilingual capacity was built into the network, not bolted on after the fact. Information flowed through communication channels that had been established and tested before the emergency.

When the call for a Day of Truth and Freedom went out on January 13, 2026 — with ten days' notice, in the middle of winter — it was boosted by the same networks and channels that had been carrying information for months. Phone banking and canvassing immediately began in communities across the state. Ninety organizations had endorsed the call. The Minneapolis Regional Labor Federation, representing 175 unions and 80,000 members, formally endorsed the action two days later. The Minnesota AFL-CIO, with over a thousand affiliated locals, followed.

Tens of thousands came out in -20°F temperatures.

The anatomy of activation infrastructure

What Minnesota built — deliberately, over time — can be understood as a set of interlocking components. Each is achievable at smaller scales. Taken together, they are what separates a network that can move from one that can't.

Pre-assigned roles. Someone is always the first caller. Someone is always the coordinator who receives the report and initiates the chain. Someone is always responsible for the communication that goes out to the broader network. These roles don't need to be rigid, but they need to exist before the emergency, not be improvised during it. When the IDN rapid response team got to the Bro-Tex facility in twelve minutes, that speed was possible because the roles were already assigned and practiced.

Tiered cascade structure. Information and activation signals don't travel from a single center to every member simultaneously — at scale, that doesn't work. Instead, they move in tiers: from a coordinating body to regional hubs, from regional hubs to local chapters or neighborhood networks, from local nodes to individual members. Each tier has clear responsibility and clear communication channels. The Day of Truth and Freedom moved through exactly this kind of structure, with unions and organizations taking responsibility for mobilizing their own members while the coordinating coalition held the overall frame.

Redundant communication paths. What happens when your primary channel goes down, gets compromised, or is deliberately disrupted? Every activation system needs a backup — and the backup needs to be known and tested before it's needed. Minnesota's rapid response network used secure phone and texting options alongside email and organizational channels. When the situation escalated and communication became more fraught, the redundancy was already there.

Rehearsal as organizing. MONARCA's training sessions weren't just education — they were practice runs for the real thing. The moment a thousand people filled a church in Roseville to train as legal observers, they weren't just learning skills; they were rehearsing activation. They were practicing the experience of showing up quickly, in numbers, in response to a signal. That rehearsal was part of what made the Day of Truth and Freedom possible. The movement had already practiced moving together.

Clear signal protocols. How does an activation actually get triggered? Who has the authority to call it? What does a message look like that everyone recognizes as an activation call versus routine communication? Minnesota's organizers used a dedicated rapid response line. The call for January 23rd was issued by a named coalition with organizational authority. There was no ambiguity about what was being asked or who was asking. That clarity is itself infrastructure.

Building this at your scale

You don't need ninety organizations and fifteen years to begin building activation infrastructure. You need to start somewhere, and you need to start before you need it.

Map your existing network honestly. Not who's on your email list — who would actually show up within 24 hours if you called? Who has the relationships to bring five more people? Where are the nodes in your network that have genuine reach, and where are the gaps? This mapping exercise, done honestly, tells you where your real activation capacity is.

Assign roles explicitly. Who is your first responder — the person who gets notified first and initiates the chain? Who owns communication to different segments of your network? Who has relationships with coalition partners who could amplify an action? Write these down. Make sure the people in those roles know they're in them and have agreed to be.

Test your communication channels before you need them. Send a test message through your emergency channel and see who responds, in how long. Run a practice activation — "if we needed to notify everyone in our network right now, how would we do it?" — and measure where it breaks down. The failure modes you discover in a drill are much less costly than the ones you discover in a crisis.

Build relationships across organizational lines before the emergency. Minnesota's response worked because unions trusted community organizations and vice versa — and that trust came from years of working together on overlapping campaigns. The time to build those relationships is before you need them for something high-stakes. If you don't know the other organizations in your coalition well enough to call them at 6am, you don't have a coalition — you have a list of endorsers.

Make rehearsal part of your regular organizing. Every training, every turnout operation, every rapid-response drill is also a rehearsal for activation. The muscle memory you're building in ordinary times is the muscle memory that will function under pressure.

The Minnesota lesson

By February 2026, Operation Metro Surge had ended — federal agents began withdrawing from Minnesota, and the Trump administration cited a need to "turn down the temperature." The sustained, escalating resistance from below had forced a retreat.

That outcome wasn't guaranteed by the size of the state or the strength of its institutions. It was produced by the combination of community rage and organized infrastructure. The rage was the fuel. The infrastructure was what made it directional.

The lesson isn't that Minnesota is special. It's that Minnesota built something over time that most states and most movements haven't built yet. The tools were not sophisticated. The technology was not cutting-edge. What made the difference was the patient work of coalition building, the deliberate practice of showing up together, and the insistence on building activation capacity before the crisis arrived.

Every group working for change right now faces some version of the activation problem. The question isn't whether you'll need to move your network quickly — it's whether you'll have built the infrastructure to do it when the moment comes.

The answer to that question is being determined right now, in the organizing you're doing or not doing today.