Work breakdown structure (WBS): what it is and how to use it

Afbeelding bijdrager Team AsanaTeam Asana30 juni 20217 min. leestijd
Work breakdown structure article banner image


A work breakdown structure (WBS) visually organizes project deliverables into different levels based on dependencies. It’s essentially your project plan in a visual form, with your project objective at the top, then dependencies and sub-dependencies below. In this article, we describe the different parts of a work breakdown structure and how to create one for your next project—along with a detailed example to get you started.

A work breakdown structure is a visual breakdown of a project that’s organized into multiple levels. In basic terms, it’s a way to visualize required deliverables in a more digestible way. 

Since a work breakdown structure is displayed visually, it can be created using a combination of workflow management software and specific methodologies. Some of these methods include timelines, Kanban boards, and calendars. 

We’ll take you through what to include in your work breakdown structure and provide examples using some of the most popular methods. 

What is the work breakdown structure in project management?

First things first, let’s break down a work breakdown structure (WBS). Project managers use work breakdown structures to help teams visualize projects and dependency-related deliverables

It’s a great tool when working on complex project scopes or working with team members that prefer to use visuals over lists. While most project managers prefer one type of visual over another, every work breakdown structure is made up of a few key parts. 

No matter which visual method you choose, your breakdown structure should incorporate:

From there, you’ll organize your structure based on the hierarchical levels of sub-deliverables. Your entire project will likely consist of multiple task levels which will depend on the work needed and the overall project timeline.  

Lees: Een projectplan maken dat u daadwerkelijk op het juiste spoor houdt

The levels of a work breakdown structure

Levels of a work breakdown structure help separate tasks by dependencies. Since projects can differ so significantly, the levels of your work breakdown structure will too. While most projects do have some form of dependencies, it’s possible you’ll come across projects that don’t require sub-dependencies. 

Levels of a work breakdown structure

There are three main levels of dependencies, though your structure could require more or fewer than that. Each level is connected to a parent task, with the work needed to complete the parent task organized into dependencies.  

Let’s take a look at the three highest level dependencies within a work breakdown structure. 

Level 1

The first level of a work breakdown structure is the most simplified form of the project since it contains the parent task. This is usually the same as the project objective

Let’s say, for instance, that your project team is working on revamping your website design. The first level of your WBS might look something like this:

  • Launch new website design

As you can see, it’s simple and straightforward. Level one is the basic objective and the first step of your many project management phases. The work needed to complete this objective will come later in levels two and three. 

Lees: Een doeltreffende projectdoelstelling schrijven, met voorbeelden

Level 2

From there, your breakdown structure will get a bit more complicated depending on the scope of the project. Level two of your WBS will include subtasks, otherwise known as dependencies, of the parent task. 

For example, let’s look at what tasks might be needed to launch a new website design. 

  • Revamp brand guidelines

  • Create messaging framework

  • Redesign your logo

  • Add new photography 

While slightly more granular than level one, level two is still a high-level overview of the dependencies needed to complete the project objective. 

Level 3

The next level of your WBS will break down these dependencies even further into sub-dependencies. This will include the work needed to complete the level two tasks.  

Here is an example of the above tasks broken down into the third level of your breakdown structure. 

  • Brand colors

  • Brand mood board

  • Design UX

  • Headline

  • Mission statement

  • Language guidelines

  • Sketch

  • Mockups

  • Final designs

  • Photoshoot

  • Photo edits

  • Final selections

Level three is where you break each task down into separate sub-dependencies. As you can see, the work needed to complete the project objective is becoming much more clear. You may even choose to add additional levels to your WBS, depending on how specific you want your visual to be. 

What’s included in a work breakdown structure?

A work breakdown structure is essentially a condensed project plan organized in a visual hierarchy. That means it contains everything that a successful project charter has, which includes WBS elements such as objectives, deliverables, timelines, and key stakeholders. 

What's included in a work breakdown structure

In order to create your own breakdown structure, you first need to know what to put in one. Thankfully, we’ve got you covered. Let’s take a look at some of the key pieces to include in your work breakdown structure. 

WBS dictionary

A work breakdown structure dictionary is a great place to start when beginning to build a new project structure. While not a traditional dictionary, the main purpose of the WBS dictionary is to explain each task in more detail. This is because the visual nature of a good WBS doesn’t allow room for detailed explanations. Creating a dictionary is an instrumental part of helping team members easily find the necessary details of various tasks.

While created by you, it may be beneficial to enlist the help of team members from various departments. This will ensure the dictionary is as useful as possible and all items are explained correctly.

Some fields you should include in your dictionary are:

  • Task names

  • Descriptions

  • Deliverables

  • Budget

  • Milestones

  • Approvals

While there are multiple fields you can include, the main thing to consider is creating a resource where team members can find information on the project work needed to complete various tasks.  

Task description

The task descriptions include both a task name and a brief description of the objectives. Since your WBS won’t have much space for a thorough description, you can include additional details in your WBS dictionary.

The objective of the task description is for team members to easily recognize what the task is in the shortest way possible. So don’t get too caught up in the level of detail needed just yet.  

Task owner

The task owner is an important piece to include both for accountability reasons and for communication. The easier it is to find answers, the quicker the tasks will be finished. While project managers are often task owners, department heads and managers may also be owners depending on the type of task. 

There’s nothing worse than wasting time looking for project information. Assigning task owners can improve team productivity as project stakeholders will be able to quickly direct questions to the appropriate person.   

Lees: Uw handleiding voor RACI-tabellen, met voorbeelden

Task budget

While not always needed, projects that require large budgets should be tracked carefully. It’s helpful to assign specific task budget caps in order to easily track how close you are to your allocated budget. 

Not tracking your budget could result in spending more than anticipated, which can dig into your profit margin. So be sure to not only track your total budget but individual task costs as well. 

Completion date 

It shouldn’t be a shock to hear that tracking your target completion date is a rather important detail. That said, it’s important to be prepared for changes to your completion date. 

While it can be difficult to manage multiple projects that go over their allotted timeline, sometimes it’s inevitable. In order to properly track progress, you should break down each task in a timeline or other project management tool. This way you can catch timeline delays in real time and work to prevent deadline issues from stacking up and causing you to miss your original completion date. 

Task status

Along with timeline tracking, documenting task status is important for quick progress checks. This can be logged in a few different ways, but many teams use terms such as open, in progress, and complete. 

This will not only help track progress but give a high-level overview of team productivity. For example, if there’s a pattern of select teams unable to complete tasks there may be an underlying issue. That way you can work to solve team workload or communication issues before they become huge problems.  

Lees: Een effectief projectstatusrapport schrijven

How to create a work breakdown structure

Now comes the fun part. Since a work breakdown structure is in the form of a visual hierarchy, there are a number of ways to create yours. The best part is that you get to pick which method is right for you and your team. 

How to create a work breakdown structure

Common visual methods that teams use include timelines, Kanban boards, and calendars. Depending on the software you use, some features may look slightly different in each. Let’s dive into these three methods in order to provide a deeper understanding of how you can create a work breakdown structure in each. 

Timelines (or Gantt charts)

Timelines are great tools to visualize work in a fun and colorful way. They’re also great at providing the necessary functionality for a WBS. Here are some of the functions you get using a timeline, also known as a flowchart or Gantt chart:

  • Import traditional spreadsheets

  • Track progress

  • Adjust tasks

  • Connect tasks by dependencies

  • Adjust deadline shifts

  • Assign task owners

  • Store unscheduled tasks

  • Adjust color tracking

  • Section by levels

  • Filter and sort tasks

You can start your WBS in a number of ways, including by importing an existing spreadsheet or building it directly in timeline software. Timelines are different from Kanban boards and calendars due to the visual layout and adjustable functionality. It’s really up to your preference to determine which visual is right for your team. 

Probeer tijdlijn met Asana gratis uit

Kanban boards 

Kanban boards are similar to timelines but differ in the way they’re visually organized. Instead of being organized in a horizontal line, they’re designed to look like boards as opposed to connecting tasks to timelines. Kanban software can help with the following to keep your projects on track:

A Kanban board is another great option for building out your WBS, and it’s one of the most frequently used tools for day-to-day resource management needs. One of the best things about this tool is that you can see task details up front. This makes it a great option if you’re unable to create a WBS dictionary.

The best way to get started with this method is to start building your hierarchy within your Kanban board. 

Probeer gratis borden met Asana


The third option for creating a WBS of your own is by using team calendar software. While not as commonly used for breakdown structures as the previous options, they’re a great tool to visualize projects. They’re also especially helpful for switching between day, week, and month views for large projects.

A calendar can help with the following to keep your projects on track:

  • Import traditional spreadsheets

  • Track progress

  • Adjust tasks

  • Connect tasks by dependencies

  • Adjust deadline shifts

  • Communicate in one place

  • Integrate with other calendars

Calendars are great tools for creating a WBS and they give you a different visual experience from the options above. To start your structure using a calendar, you can import an existing spreadsheet or start building a new project within your calendar software. 

Lees: 3 manieren om een projectplan te visualiseren: tijdlijnen, agenda's en borden

Work breakdown structure example

Now that you know what goes into a WBS and how to build one using a variety of software tools, let’s look at a tangible example. While your template will look slightly different depending on the method you use to create it, your WBS should include similar task hierarchies and levels. 

Work breakdown structure example

Here is an example work breakdown structure from the above details to get you started on your own.

WBS name: Website design

Description: Revamp our old website design based on the new branding. 

Completion date: 9/15/21

Budget: $50,000

Level 1: 

  1. Revamp website design 

Level 2:

  1. Revamp brand guidelines (Complete)

  2. Create messaging framework (Complete)

  3. Redesign logo (In progress)

  4. Add new photography (Open)

Level 3:

1. Revamp brand guidelines 

  • Brand colors—Kat Mooney

  • Brand mood board—Kat Mooney

  • Design UX—Ray Brooks

2. Create messaging framework

  • Headline—Daniela Vargas

  • Mission statement—Daniela Vargas

  • Language guidelines—Daniela Vargas

3. Redesign logo

  • Sketch—Kabir Madan

  • Mockups—Kat Mooney

  • Final designs—Kat Mooney

4. Add new photography

  • Photoshoot—Kabir Madan

  • Photo edits—Kat Mooney

  • Final selections—Kabir Madan

Remember that your WBS will look different based on the size of the project, its complexity, the timeline, and your chosen software. Each of these details will shape the dependencies and visual hierarchy of your project. 

Breaking down a work breakdown structure

When it comes down to it, a work breakdown structure isn’t so hard to create. In fact, once you get the hang of it, you and your team can only benefit from adding a visual hierarchy or project tasks. Whether you’re a visual or verbal learner, there’s a work management tool out there for everyone. 

With Asana, you can easily switch between lists, timelines, boards, and calendars without missing a beat. Less time spent on work about work? Yes, please. 

Probeer Asana gratis

Gerelateerde bronnen


30-60-90 day plan: How to onboard new hires with ease