Campaigning Wiki

3 min read

Summary

Kanban — visible To do · Doing · Done columns on a board, with a limit on work-in-progress — is the lightweight flow-control discipline for fast-moving, reactive campaign work where rigid quarterly plans break.

Body

Kanban is the visual-flow discipline borrowed from lean and agile practice and adapted to campaign work. The mechanics are simple:

  • A board with three (or more) columns — To do · Doing · Done is the workhorse; some teams add Blocked and Review.
  • Cards for each task — with named owner, due date and a link back to the campaign goal it serves.
  • A limit on work-in-progress (WIP). The team commits to no more than N tasks in Doing at once; new work does not enter Doing until something leaves it. The WIP limit is the discipline that makes Kanban different from a generic task list.

The People Power Manual’s workshop handouts treat visible task tracking as essential for distributed organising, and the manual’s organising themes pair Tactics with Organisational considerations so each tactic has a named owner and a visible status [source: people-power-manual]. The Commons Library’s Campaign Accelerator trains campaigners to maintain a kanban-style action register and to read it at a fixed weekly slot [source: commons-library]. The ALA Frontline Advocacy Toolkit’s planning roadmap recommends the same visible-board discipline for advocacy projects specifically because decisions and tasks are otherwise lost between meetings [source: ala-frontline].

A useful campaign kanban has five properties:

  • Cards link to a goal. Every card links to the SMART goal or OKR it serves. Cards that do not link to any goal are deleted.
  • Owner per card. No card without a name.
  • WIP limit. The team’s hardest discipline — and the one that prevents over-commitment.
  • Fixed-cadence review. A standing 30-minute weekly review at which the board is read and re-prioritised.
  • Visible to the team. Not a personal to-do list — a shared artefact the team can scan in 60 seconds.

A common failure mode is to use Kanban as a glorified to-do list without the WIP limit — at which point the board tracks activity but does not control flow. The Commons Library treats the WIP limit as the discipline that distinguishes Kanban from a simple task list [source: commons-library]. A second failure mode is to over-tool the board — dozens of columns, dozens of card types — at which point the board becomes a project-management tool the team no longer reads. The ALA Frontline Advocacy Toolkit recommends a board the team can update in two minutes per card, not in fifteen [source: ala-frontline].

Kanban pairs particularly well with OKRs: OKRs set direction (what the quarter is trying to achieve); Kanban manages flow (how the work actually moves). It also pairs with RACI at the per-card level: each card’s owner is the Responsible; the campaign manager is the Accountable; whoever else is consulted or informed is named on the card.

Use it for

Running a fast-moving digital or rapid-response campaign; managing a coalition’s shared work; onboarding new team members mid-campaign; surviving a leadership transition; pairing with OKRs for direction + Kanban for flow.

Open Questions

None yet.

Sources & verification

  • sources/commons-library — grounding: secondary — RAW (5257 chars)
  • sources/people-power-manual — grounding: secondary — RAW (7977 chars)
  • sources/ala-frontline — grounding: secondary — RAW (13361 chars)

Verified 2026-06-23 by llm-qc.

Graph View

Backlinks