Work Breakdown Structure
Summary
A work breakdown structure (WBS) decomposes the campaign into phases → workstreams → tasks, with milestones marking the end of each meaningful chunk — the discipline that turns a plan into a list with one owner per task.
Body
A WBS is the decomposition side of project management: take the campaign plan, break it into phases (preparation, launch, escalation, evaluation), each phase into workstreams (research, communications, field, fundraising, legal), each workstream into tasks. Each task should have:
- A clear definition of done — the press release has been sent to these N outlets and we have logged the responses.
- A single named owner.
- A due date that is realistic relative to the workstream’s other tasks.
The WBS is the input to both the timeline / Gantt (critical-path) and the RACI matrix (raci): it produces the row count those tools work with.
The ALA Frontline Advocacy Toolkit’s 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-WS 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].
A common failure mode is producing a WBS where tasks are too coarse — do communications — and no one can tell who has done what. The Community Tool Box and ALA Frontline both warn that a WBS that does not reach the level of one-task-one-owner-one-due-date is decoration [source: ala-frontline]. A second failure mode is under-breaking the WBS — tasks so small they obscure the workstream. The Community Tool Box’s action-planning chapters treat a useful WBS as one where the team can answer, for each task: who is responsible? when is it done? what does done look like? If any answer is missing, break the task further or roll it up [source: ala-frontline].
Use it for
Converting a campaign plan into a list with one owner per task; onboarding new team members mid-campaign; running a structured mid-campaign re-plan; producing the input to a Gantt or RACI.
Worked examples
case-studies/coalition-of-immokalee-workers-campaign-against-taco-bell— the CIW’s work breakdown structure for the Taco Bell campaign: research workstream, coalition workstream, fast-food-buyer workstream, communications workstream, fundraising workstream — each with named owners and quarterly milestones.case-studies/montgomery-bus-boycott— the campaign’s implicit WBS: car-pool workstream, mass-meeting workstream, legal-track workstream, communications workstream, fundraising workstream; each with named MIA committee chairs.
Related
- campaign-planning
- campaign-project-management
- critical-path
- raci
- kanban-for-campaigns
- risk-management
- governance
- ala-frontline
Open Questions
- 2026-06-23 — The locally fetched RAW for
[[ala-frontline|sources/ala-frontline]]is the toolkit’s planning roadmap but does not use the term “work breakdown structure” by name. Re-fetch a project-management chapter or a Seedstone / NDI source that covers WBS specifically before promoting this page.
Learn more
- On Wikipedia: Work breakdown structure — CC BY-SA 4.0
FAQ
What is a work breakdown structure?
A work breakdown structure is the decomposition (abbreviated WBS) that breaks the campaign into phases → workstreams → tasks, with milestones marking the end of each meaningful chunk — the discipline that turns a plan into a list with one owner per task. It is the decomposition side of project management.
What is the standard structure?
A WBS is built by taking the campaign plan, breaking it into phases (preparation, launch, escalation, evaluation), each phase into workstreams (research, communications, field, fundraising, legal), each workstream into tasks. Each task should have a clear definition of done, a single named owner, and a due date that is realistic relative to the workstream’s other tasks. The WBS is the input to both the timeline / Gantt (critical-path) and the RACI matrix (raci).
What does the ALA Frontline Advocacy Toolkit add?
The ALA Frontline Advocacy Toolkit’s planning roadmap — identify the lead team, find roles for all staff, set a goal, write the message, tell it to the right people, evaluate — is a working example of a campaign-WS 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].
What are the failure modes?
A common failure mode is producing a WBS where tasks are too coarse — do communications — and no one can tell who has done what. A second is under-breaking the WBS — tasks so small they obscure the workstream [source: ala-frontline]. The Community Tool Box treats a useful WBS as one where the team can answer, for each task: who is responsible? when is it done? what does done look like? If any answer is missing, the task needs re-breaking.
Sources & verification
- sources/ala-frontline — grounding: secondary — RAW (13361 chars)