Skip to content

Campaigning Wiki

8 min read

lang: en

Summary

Organising is the patient, relational work of building committed leaders and a durable base of one-to-one relationships; mobilising, by contrast, moves people to act once, on a calendar. The distinction matters because tactics, no matter how well chosen, only carry weight when a credible base stands behind them [source: commons-library][source: moblab].

Body

Organising vs. mobilising

The Commons Social Change Library draws the line clearly: mobilising is the act of channelling existing supporters into a specific action — a rally, a petition deadline, a call-day — on a chosen date, while organising is the slower, upstream work of growing the base that any such action depends on [source: commons-library]. Mobilisation Lab frames the same split operationally: a mobilised crowd delivers a moment; an organised base delivers a series of moments, and the credibility to threaten the next one [source: moblab]. The two are not rivals — every campaign mobilises, and the question is only what it mobilises out of. An organisation that only mobilises is renting its audience from email lists and news cycles; an organisation that also organises owns the relationships that survive the news cycle. The Commons Library’s campaign-strategy manuals consistently place organising as the upstream layer of the campaign cycle, the work that has to be substantially done before public tactics become available options at all [source: commons-library]. Alliance Citoyenne’s published French case material confirms the same logic in a different national setting: their housing and anti-discrimination campaigns spend the majority of their months in listening, one-to-ones, and leader-development before any public action is named [source: alliance-citoyenne].

The relational ladder

The Commons Library describes a graduated ladder of relationships that supporters climb as a campaign deepens: contact (someone on a list or at a door), conversation (a two-way exchange, usually a one-to-one), commitment (a concrete ask accepted — a meeting to host, a shift to take, a call to make), and leadership (a person who now recruits and develops others) [source: commons-library]. Each rung is qualitatively different from the one below it, and the ladder is unidirectional in practice: a contact who skips straight to commitment without a real conversation tends to evaporate the first time the campaign costs them something. A contact who skips straight to leadership, recruited by flattery rather than by demonstrated commitment, burns out as soon as the work stops being fun. The Commons Library’s people-power manual is explicit that skipping rungs is the single most common reason otherwise promising campaigns lose their base between action peaks [source: commons-library]. Mobilisation Lab’s Campaign Accelerator toolkit operationalises the same ladder as a “supporter journey” with explicit role transitions at each stage, and ties each transition to a measurable behaviour change [source: moblab].

One-to-ones as the atomic unit

If the relational ladder is the structure, the one-to-one is the load-bearing unit. The Commons Library and MobLab both treat the one-to-one — a 30-to-60-minute structured conversation between an organiser and a prospective leader — as the smallest indivisible act of organising [source: commons-library][source: moblab]. The structure is conventional but specific: a one-to-one surfaces the other person’s story, self-interest, relationships, and capacity, and ends with a concrete ask calibrated to the rung they are currently on. Skipping the structure — treating a one-to-one as a chat, or worse, as a recruitment pitch — collapses the very relationship the conversation was meant to build. Alliance Citoyenne’s case write-ups make the same point from a French community-organising perspective: their four-step campaign method begins with listening and one-to-ones precisely because every later step (research, negotiation, escalation) rests on the trust those conversations create [source: alliance-citoyenne]. See one-to-ones for the full method.

Leadership development

Leadership development is the work of moving people from “does tasks” to “makes decisions”, and it is the layer at which campaigns most often collapse. The Commons Library distinguishes two activities that look similar from the outside but are structurally different: task delegation (handing someone a defined job with supervision) and leader development (handing someone a problem, a deadline, and the trust to solve it, then coaching the result) [source: commons-library]. Task delegation scales activity; leader development scales the organisation. A campaign that only delegates tasks grows linearly, limited by what its current leaders can supervise; a campaign that develops leaders grows multiplicatively, because each new leader soon develops leaders of their own. The Commons Library’s leadership-development materials warn that shallow pipelines — campaigns where the same two or three people make every decision and “delegate” everything else — are the most common failure mode in the second year of an organisation’s life [source: commons-library]. MobLab’s Campaign Accelerator toolkit maps the same insight onto distributed organising, where leadership development is the mechanism that prevents the centre from becoming a bottleneck as a campaign scales [source: moblab]. Alliance Citoyenne’s French community-organising practice explicitly builds local leader identification into its listening phase, before any issue is chosen, on the principle that leaders identified under pressure tend to be the loudest, not the most durable [source: alliance-citoyenne]. See leadership-development for the full method.

Distributed organising

Distributed organising is what happens when relational methods scale without concentrating decisions at a single centre. The Commons Library and Mobilisation Lab both describe the move from a hub-and-spoke model (the campaign office plans, the chapters execute) toward a mesh model (local teams plan, decide, and act on their own terrain while sharing brand, targets, and learning with peers) [source: commons-library][source: moblab]. MobLab’s Campaign Accelerator toolkit is the most-cited operationalisation of this shift: it defines team roles, a supporter journey, a distributed-action menu, and the metrics for each phase, so that local teams can act autonomously without drifting from the campaign’s overall theory of change [source: moblab]. The Commons Library frames the underlying principle: distributed organising does not mean decentralised decision-making about everything — it means pushing decision-making as close to the relationship as possible, and reserving the centre for the things only a centre can do (legal cover, brand coherence, shared research, escalatory decisions) [source: commons-library]. Alliance Citoyenne’s local-chapter model in French cities is a worked example: each chapter chooses its own local issue and runs its own campaign, while the national federation shares training, legal resources, and the occasional escalation across chapters [source: alliance-citoyenne]. The risk of distributed organising, consistently flagged in all three sources, is that without active leader development the centre quietly re-centralises as local teams burn out [source: commons-library][source: moblab]. See distributed-organizing for the full method.

Base size and bargaining power

The third-party sources converge on a causal claim at the heart of any organising strategy: the credibility of a demand is a function of the committed relationships that stand behind it. The Commons Library’s campaign-strategy materials frame this as the link between base-building and power: a target’s calculation of whether to concede, negotiate, or fight back tracks how many people they believe will follow through on the next escalation [source: commons-library]. Alliance Citoyenne’s published case accounts of French housing and anti-discrimination campaigns make the same point more concretely: the campaigns that won structural concessions were the ones whose target sat down because they could see, on paper and in the room, a base large and committed enough to escalate credibly [source: alliance-citoyenne]. MobLab’s distributed-organising metrics include base-size and commitment-depth indicators explicitly because the toolkit’s authors have seen campaigns lose negotiations not for lack of a good demand but for lack of a believable “and then what?” [source: moblab]. The corollary is uncomfortable but consistent across the sources: a brilliant tactic without a committed base is theatre; a committed base with an ordinary tactic is power [source: commons-library][source: alliance-citoyenne].

Use it for

  • Turning a warm email list into a committed local chapter before the campaign’s first public action.
  • Diagnosing why a campaign that had a strong start is losing its base between action peaks.
  • Designing a leader-development pipeline so the campaign survives the departure of its two or three founding leaders.
  • Deciding whether to scale a local win into a national campaign by replicating the relational model chapter-by-chapter.
  • Choosing between a hub-and-spoke structure and a distributed-organising mesh before the second year of an organisation.
  • Building the case, in a target meeting, that the base behind a demand is large and committed enough to make escalation credible.

Examples

  • Alliance Citoyenne housing campaigns, France, 2010s–present. A federation of local chapters, each anchored in one-to-ones and local leader identification, runs neighbourhood-level housing campaigns; the national structure exists mainly to share training, legal cover, and escalatory support. The model worked because base-building preceded any public demand, and because chapters retained decision authority on local issues [source: alliance-citoyenne].
  • Mobilisation Lab Campaign Accelerator campaigns, multinational, 2010s–present. Member organisations have used the Campaign Accelerator toolkit to move from staff-driven mobilisations to distributed-organising models in which local teams own their own supporter journey and action menu. The model worked because role transitions and metrics were defined upfront, so leader development kept pace with growth instead of lagging behind it [source: moblab].

Open Questions

None yet.

Graph View

Backlinks