Why Policies Fail

Before You Launch the Campaign What to ask yourself, your community, and your team before you announce anything

Most issue campaigns do not fail because the cause was wrong.

They fail because the strategy was unclear, the infrastructure was never built, or the team never got past the launch. The Arc Framework exists to close that gap. This post is for the campaign director who just picked up the framework and is asking: this is great, but where do I start? It is also for the seasoned organizer who has run campaigns before but has never had a complete process to work from.

You start by answering these questions. Honestly. In writing. With the people who will be doing this work alongside you.

01 / DEFINE: Name the Condition

Advocacy without clarity is just noise.

The Define phase asks you to name the condition you are trying to change, understand who is most affected and what they actually say about it, and get clear on what winning looks like before you build anything else. Issue campaigns that skip Define spend years working hard on the wrong thing.

Ask yourself: What is the specific condition you are trying to change? Can you name it as a policy, a budget line, or a practice, not just as a feeling? What does winning look like as a concrete outcome?

Ask the community: Who is most affected and have you actually talked to them about what they want changed? Not what you think they want. What they say. And what does the community define as victory? This is not the same as what the campaign defines as victory.

Ask your team: Are we building our analysis from the community's lived experience or from our assumptions about it? Is the community a partner in this campaign or an audience for it? Be honest about which one it actually is right now.

In issue campaigns, the people most affected by the condition are not your audience. They are your authority. That relationship has to be designed before anything else moves.

02 / PLAN: Strategy Before Action

A theory of change is not a hope. It is a map.

Issue campaigns live and die by coalition. Your plan has to map who is in, who is persuadable, and who you need to move. Before any of that, you need to answer one question: if you do everything right, how does the condition actually change?

Ask yourself: Who has the power to make this change? Name the actual decision-makers. What is your theory of change, walked out step by step? Does the logic actually hold?

Ask the community: Who in the community has standing with decision-makers that you do not? What is non-negotiable in how this campaign is run?

Ask your team: Who is persuadable among the decision-makers and what will it actually take to move them? Who is immovable and are we spending time trying to convince people who will not move? Does your strategy name the structural forces you are up against, or just the opponent?

03 / DESIGN: Build the Capacity to Execute

Most issue campaigns skip Design and call it agility. It is not agility. It is chaos wearing a good cause.

Roles filled. Systems built. Coalition partners aligned. People trained before you launch. The Design phase is not glamorous but campaigns that skip it pay for it at the worst possible time.

Ask yourself: What roles does this campaign require and which ones are currently empty seats? Do I have a Community Lead, someone whose explicit job is to keep this campaign rooted in the affected community?

Ask your team: Does every person know their role, their lane, and who they report to? Is our coalition infrastructure built to hold through a long fight or did we assume people would stay engaged without any management?

A role without an owner is a gap waiting to become a crisis. Fill the seats before you start the work.

04 / IMPLEMENT: Move from Ideas to Reality

Issue campaigns require a different implementation muscle.

The timeline is longer. The opposition is often more entrenched. The wins are rarely clean. Implementation is where the plan meets the conditions, and your job is to stay adaptive without losing the strategy.

Ask yourself: Are we running the campaign we planned or the one that is easiest right now? What is the campaign asking of the community and is that ask proportional to the trust we have built?

Ask the community: What is the community experiencing right now that we are not seeing from inside the campaign?

Ask your team: What is not working right now that we have been afraid to name out loud? Are we doing activity that feels like progress or are we actually moving the decision-makers we need to move?

05 / EVALUATE: Learn Without Flinching

Issue campaigns have no Election Night. That means you have to build your own accountability structures or drift.

The Evaluate phase embeds honest assessment into the work itself. What are your milestones? Who is moving? What is the community telling you that you have not been hearing?

Ask yourself: What are our campaign milestones and are we hitting them? Are we measuring what the community says matters or only what our funders want to see?

Ask the community: Is this campaign still aligned with what the community wants, or has their understanding of the problem evolved while we kept running the same play?

Ask your team: Are we willing to surface what is not working before it is too late to change it? What has the campaign learned in the last 60 days and where has that learning actually changed what we are doing?

If it has not changed anything, you are not evaluating. You are just logging.

06 / SCALE: Expand What Works

Unlike electoral campaigns, issue campaigns do not end on a fixed date. Use that.

The infrastructure you build compounds. The relationships you develop transfer. The power you accumulate carries forward. Scale in issue work means replicating what worked, transferring knowledge, and building toward the next condition you are trying to change.

Ask yourself: What has this campaign built that should outlast it, win or lose? What is replicable and what was specific to this issue, this moment, this coalition?

Ask the community: What did the community learn about its own power through this campaign that belongs to the community and not to us?

Ask your team: How do we transfer institutional knowledge so it does not walk out the door with the people who are leaving?