Campaign Project Management
Summary
Campaign project management is the day-to-day operating system: workstreams, roles, milestones, dependencies, change control, and a regular rhythm of stand-ups, decision logs and action registers that keep the campaign moving under shifting conditions.
Video
Embedded YouTube CC clips related to this page:
Body
Campaign project management is what the campaign uses during delivery to make sure the plan actually happens. It is distinct from campaign-planning (which produces the plan) and from volunteer-management (which develops the people doing the work): project management is the discipline of organising the work itself.
The ALA Frontline Advocacy Toolkit’s “deeper” planning roadmap — identify the lead team, find roles for all staff, define how leadership and frontline work together, set a goal, write the message, tell it to the right people, choose communication methods, put the plan on paper, evaluate — is a working example of a campaign-operating-system list applied in a different domain (library advocacy) [source: ala-frontline]. The same toolkit insists on writing the plan down: an oral plan that no one can re-read next week is a plan that will drift [source: ala-frontline].
The Commons Library’s organising modules and the People Power Manual pair the project-management layer with the strategy layer: each tactical timeline is paired with a “Creating a tactical timeline” process guide and a sequence of named process guides for action design, group process and decision-making [source: people-power-manual]. The Community Tool Box frames project management as the implementation discipline that turns the action plan into operational outputs — staff and volunteer assignments, milestones and review cadences [source: community-tool-box].
Lightweight tools dominate campaign project management in practice. Five recurring ones appear across the sources:
- Kanban board / action register — every active task as a card with owner, due date and status. The People Power Manual’s workshop handouts treat visible task tracking as essential for distributed organising [source: people-power-manual].
- Weekly stand-up — short, time-boxed meeting where each workstream reports what it did, what it will do and what is blocking it. The Commons Library runs its Campaign Accelerator around this cadence [source: commons-library].
- Decision log — one-line record of every significant decision, the date, who made it and why. ALA’s Frontline Advocacy Toolkit recommends this for advocacy projects specifically because decisions are otherwise lost between meetings [source: ala-frontline].
- Milestone tracker — a small number of named dates (launch, escalation, deadline, evaluation) on which the campaign turns. The Community Tool Box pairs milestones with indicators so each milestone triggers a measurable check [source: community-tool-box].
- Change-control note — a one-paragraph record of any change to strategy, message, target or budget and the reason. The Commons Library treats change control as inseparable from strategy revision: a campaign that quietly pivots without writing the pivot down will not be able to learn from itself [source: commons-library].
A common failure mode is to mistake activity for output. The Community Tool Box warns against the team that runs many tasks but cannot say which ones move which objectives [source: community-tool-box]. The ALA Frontline Advocacy Toolkit adds a discipline worth copying: every task card links to the specific goal it serves, and tasks that do not link to any goal are deleted [source: ala-frontline].
Use it for
Running a multi-workstream campaign week to week; onboarding new team members mid-campaign; surviving a leadership transition; making the campaign legible to a board or funder.
Examples
- African Americans boycott buses for integration in Montgomery, Alabama, US, — On January 30, 1956, opponents of the Montgomery bus boycott bombed the house · north-america
Learn more
- On Wikipedia: Customer relationship management — CC BY-SA 4.0
Related
- campaign-planning
- volunteer-management
- governance
- the-campaign-cycle
- risk-management
- kpis-and-dashboards
- commons-library
- community-tool-box
- people-power-manual
- ala-frontline
Open Questions
(none)
FAQ
What is campaign project management?
Campaign project management is the day-to-day operating system: workstreams, roles, milestones, dependencies, change control, and a regular rhythm of stand-ups, decision logs and action registers that keep the campaign moving under shifting conditions. It is what the campaign uses during delivery to make the plan actually happen — distinct from campaign planning (which produces the plan) and volunteer management (which develops the people). The ALA Frontline Advocacy Toolkit’s “deeper” planning roadmap is a working example in library advocacy [source: ala-frontline].
What are the five recurring lightweight tools?
Five recurring lightweight tools appear across the sources [source: people-power-manual] [source: commons-library] [source: ala-frontline] [source: community-tool-box]: (1) a kanban board, with cards for owner, due date and status; (2) a weekly stand-up, where each workstream reports what it did, will do, and what is blocking; (3) a decision log, recording every significant decision with date and rationale; (4) a milestone tracker, naming the launch, escalation, deadline, and evaluation dates; and (5) a change-control note, recording any pivot to strategy or budget and the reason.
Why write the plan down?
Writing the plan down is non-negotiable: an oral plan that no one can re-read next week is a plan that will drift [source: ala-frontline]. The Commons Library’s organising modules and the People Power Manual pair the project-management layer with the strategy layer, attaching named process guides to each tactical timeline [source: people-power-manual]. The Community Tool Box frames project management as the implementation discipline that turns the action plan into operational outputs — staff and volunteer assignments, milestones and review cadences [source: community-tool-box].
What is a common failure mode in campaign project management?
A common failure mode is to mistake activity for output: the Community Tool Box warns against teams that run many tasks but cannot say which ones move which objectives [source: community-tool-box]. The ALA Frontline Advocacy Toolkit counters with a discipline worth copying: every task card links to the goal it serves, and tasks without a goal are deleted [source: ala-frontline]. Change control is inseparable from strategy revision: a campaign that pivots without writing the pivot down will not learn from itself [source: commons-library].
Sources & verification
- sources/ala-frontline — grounding: secondary — RAW (13361 chars)
- sources/people-power-manual — grounding: secondary — RAW (7977 chars)
- sources/commons-library — grounding: secondary — RAW (5257 chars)
- sources/community-tool-box — grounding: secondary — RAW (833 chars)