Campaign Project Management
Definition
Campaign project management is the day-to-day operating system that sits between the strategic plan and the on-the-ground action: workstreams, named roles, milestones, dependencies, change control, decision logs, action registers, and a regular rhythm of stand-ups and reviews.
It sits below campaign-planning in the abstraction stack and is heavily borrowed from the agile and PRINCE2 traditions. Planning says we will run three phases over 18 months with these decision rules; project management says Alice owns the legal pipeline, Bob owns the press list, the Friday stand-up reviews the action register and the dependency map. The artefacts are visible to participants: kanban boards, weekly status notes, a shared decision log, a risk register, and a clear escalation path.
Why it matters: campaigns that skip this layer depend on a few heroic individuals and lose institutional memory when those individuals leave. Establishing a project-management cadence enables volunteer escalation because new joiners can be onboarded into an existing rhythm rather than into chaos.
It overlaps with kanban-for-campaigns and agile practices.
FAQ
What is campaign project management?
Campaign project management is the day-to-day operating system that sits between the strategic plan and on-the-ground action: workstreams, named roles, milestones, dependencies, change control, decision logs, action registers, and a regular rhythm of stand-ups and reviews. It sits below campaign-planning in the abstraction stack and is heavily borrowed from the agile and PRINCE2 traditions.
How does campaign project management differ from campaign planning?
Campaign project management differs from campaign-planning by sitting one layer lower in the abstraction stack. Planning says the team will run three phases over 18 months with these decision rules; project management says Alice owns the legal pipeline, Bob owns the press list, and the Friday stand-up reviews the action register and the dependency map. The two layers answer different questions.
Why does campaign project management matter?
Campaign project management matters because campaigns that skip the layer depend on a few heroic individuals and lose institutional memory when those individuals leave. Establishing a project-management cadence enables volunteer escalation: new joiners can be onboarded into an existing rhythm of stand-ups, kanban reviews, and decision logs rather than into chaos. The artefacts are visible and shareable.
What artefacts does campaign project management produce?
Campaign project management produces artefacts visible to participants across the team: kanban boards, weekly status notes, a shared decision log, a risk register, and a clear escalation path. Add to those the regular rhythm of stand-ups and reviews, action registers, dependency maps, and change control records. The point is that one person’s week is legible to the rest of the team.
What does campaign project management overlap with?
Campaign project management overlaps with kanban-for-campaigns and agile practices. Those traditions supply the cadences, the visible board, and the role definitions the PM layer borrows from. The campaign adaptation keeps the core artefact set — kanban boards, stand-ups, decision logs, risk registers — while mapping them onto named campaign workstreams rather than product sprints.
Full page: [[campaign-project-management]].