A bigger plan. A clear next task.
Organize outcomes into delivery areas and work packages, then connect the tasks that move them forward.

Organize outcomes into delivery areas and work packages, then connect the tasks that move them forward.

A work breakdown structure, or WBS, describes what a project needs to deliver. It helps you move from a broad goal to work packages with a clear purpose and completion criteria. Tasks describe the actions that contribute to those packages.

Describe the change or deliverable the whole project should produce.
Group related outcomes so the broad scope remains understandable.
Define a smaller deliverable and what must be true when it is complete.
Connect the practical actions that create and verify the deliverable.
An illustrative WBSA website launch, made concrete.Project: launch the website. Delivery area: public product experience. Work package: publish a useful product page. Completion criteria: approved content, working navigation and readable mobile layout. Tasks: write the copy, prepare imagery, build the page and review the published result.
Link work to the projects it supports without maintaining separate copies.
A WBS explains the deliverables. Task states explain what is happening now.
Write criteria that someone can check, rather than a vague intention.
A package without tasks is a planning gap, not evidence that its outcome is complete.
No. Personal tasks and simple lists remain a valid starting point.
No. WBS groups deliverables; a board groups execution tasks by their actual state.
No. The launch example is explanatory. Build a structure that reflects your own project and acceptance criteria.