Also known as: WBS, work decomposition
A Work Breakdown Structure (WBS) decomposes a project into smaller, manageable deliverables organized hierarchically. Top level is the whole project; next levels are major phases or deliverables; leaf level is individual tasks. A WBS makes scope estimable, assignable, and trackable, and exposes gaps where undefined work was smuggled into "and then we finish."
Where you'll see work breakdown structure (wbs) in day-to-day work inside Helm.
Helm Projects support hierarchical task structure: milestones contain tasks, tasks contain subtasks. This mirrors the WBS pattern. When estimating a project, building the WBS as Helm tasks (with hours per task) produces both a defensible estimate and the execution plan in one step. The Project Manager agent uses the WBS to detect scope expansion. New top-level tasks added after kickoff are a signal the original WBS missed something or scope has grown.
Concepts that show up in the same workflows and reports.
Common questions and honest answers.
Leaf tasks should be estimable in a specific number of hours (typically 4-40 hours per leaf). If a task is "20-80 hours", it needs to be broken down further. If every task is 1-2 hours, you've over-decomposed.
Related but distinct. WBS defines the work; a project plan adds timeline, assignments, and dependencies on top. In Helm, the WBS is the task structure; the plan is the same tasks scheduled and assigned.
Because projects that go over budget didn't miss the estimate on individual tasks. They missed whole tasks that weren't in the plan. A thorough WBS exposes those before estimation. A rushed WBS hides them until delivery.
Helm is the AI work platform where these concepts stop being theory and start being your Monday morning.