Plexii glossary
Work breakdown structure (WBS)
A hierarchy that divides a project’s complete deliverables into smaller, manageable work packages.
What it means
A hierarchy that breaks deliverables into work packages, the 100% rule , WBS vs task list vs Gantt chart, and a worked example on a clearly fictional event.
The term is most useful as a shared description. It does not remove the need to look at the actual task, evidence or constraint in front of you.
A practical example
An event divides into venue, programme, speakers and guests; each branch breaks into deliverables that can be owned.
Put it into practice
- Name the concrete situation before applying the label. Work breakdown structure (WBS) is useful only when it changes a choice, boundary or next action.
- Make the state visible: write the owner, time, source or stopping condition down instead of relying on memory.
- Review what happened. Keep the part that reduced ambiguity and change the part that added ceremony without helping the work.
How it relates to Plexii
grow the breakdown as a Mind map and turn branches into tasks (widget mind map), then schedule them in a Table’s Gantt view (table views).