Work breakdown structure (WBS) is a project management technique that segments larger projects into more manageable deliverables. WBS organizes your project by tree-like hierarchy, with your overall project objective at the top. From there, dependencies of the parent objective are identified, and at the bottom, these dependencies are broken down into specific tasks.

For example, let’s say you’re developing a new mobile app. The level one project or parent objective could be to “launch new mobile app.” The primary level two dependencies would be to create the database, develop the back-end logic and design the user interface. From there, some level three tasks for the user-interface dependency would be hosting a creative brainstorming session, creating a mood board, building the wireframes and more.

WBS is a visual project management technique that typically uses workflow management software or Kanban boards to manage the dependencies and tasks of a project. WBS is great for defining a project’s scope, identifying dependencies, estimating timelines and costs, assigning tasks to team members and tracking the project’s overall progress.

The WBS project management technique is therefore best for larger, more complex projects that need to be broken down into smaller parts. This is because complex projects typically have many dependencies and subtasks, and WBS is great at identifying and planning for them.