We’ve all heard that familiar phrase, “Don’t bite off more than you can chew.”\nThis idea is never more true than when you are starting a new project. It’s tempting to start with big, lofty plans for what you’re going to accomplish. However, without proper planning, you’re left with project delays, exceeded budgets and general chaos.\nBy using a work breakdown structure in project management (WBS), you can organize and create a system to roll out a new project.\nThis will make your life easier and keep your team steadily moving toward your (attainable) end goal.\nIn this article, we’ll look at: \n\nWhat is a work breakdown structure (WBS)?\nThe benefits of this project management approach\nHow it compares to other methods\nHow you can get started right now\nBest practices for implementation\nExamples to inspire your own team\n\nLet’s dive in.\nWhat exactly is a work breakdown structure?\nA work breakdown structure in project management is a hierarchical structure of project activity. In simple terms, it’s a list of what needs to be done within a project. It breaks down the tasks to be completed into clear steps, and displays them within a chart or other visible representation so the team can easily see each step of the project.\n\nVia ProjectManager.com\nWBS project management benefits\nYou may think creating a project plan is sufficient, and that a work breakdown structure is redundant.\nWhile proper project planning is vital, so is a work breakdown structure. Here are a few benefits.\nTasks are completed\nAlthough you have a plan in place, smaller tasks can get overlooked once the project is rolling along.\nWBS project management breaks out each of these tasks in a visual manner. The team can see what steps need to be completed and in what order.\nThis ensures nothing is skipped or forgotten in the process. And on the flipside, no unnecessary steps are added — everything is clearly outlined from the beginning.\nKeeps team members accountable\nJust like a breakdown structure keeps tasks organized, it also keeps team members organized.\nA WBS shows the entire team what tasks need to be completed and in what order.\nIf you’re using a project management tool like Hubstaff Tasks, you can easily assign these individual tasks to each person, or multiple people at once.\n\nThis way, nothing is missed. You can easily see what’s on everyone’s plate, and follow up with the team members responsible if the task missed its deadline.\nFosters communication\nSince all tasks are visible to the entire team, it’s easy for team members to communicate with one another.\nFor example, if work needs to be completed on one task before another team member can begin their part, it’s easy to find out what the holdup is.\nThis open communication brings unforeseen shifts in an established project management lifecycle to the forefront.\nThe more the team communicates throughout the process, the smoother the project will run.\n\nProvides structure\nWork breakdown structures take a project scope and put it to paper.\nSince all tasks are accounted for and organized, it provides a clear path for the team.\nAlthough there are always unexpected changes that come up during a project, a detailed and defined WBS can make surprises less destructive.\nHelps with budgeting\nBy breaking a project into small sections as a WBS does, it’s easier to estimate the costs involved. \nSince each task is assigned a team member, you’ll easily see how many team members you need. This helps estimate the staff and budget needed.\nBy looking at the number of tasks, it’s easier to estimate a project deadline based on what needs to be completed along the way.\nPlan projects for successGet more done with Hubstaff Tasks\nCarries out the project plan\nIf you think about it, a project plan is an outline of a project, but project success really stems from the work breakdown structure.\nYour structure is the lifeblood of a project. It helps with everything from resource planning to schedule planning to time estimations.\nWBS vs. project plan vs. project schedule\nYou now know why a WBS is important and a vital step in project management.\nHowever, you still might be wondering how it works with other project management components, such as a project schedule or plan.\nAs we discussed previously, a WBS takes the tasks needed to be completed from a project plan and breaks these out.\nIt focuses purely on the project management deliverables. It doesn’t include a time component, predecessors, or dependencies.\n\nVia ProjectManager.com\nA project schedule assigns time constraints to each task and shows dependencies. It also establishes a timeline for the project.\nAltogether, your process might look something like this:\n\nCreate your project plan\nCreate a work breakdown structure\nThen, you will use these two to create a project schedule.\n\nCreating a WBS before a project schedule will provide an uncluttered view of the tasks before dates and team members are assigned. This will help ensure you have everything accounted for.\nHow to create a work breakdown structure\nThere are a few components that every WBS has.\nAlthough, there are different formats you can use depending on what works best for your project and company.\nNo matter which format you choose, the overall structure should include the following parts.\n1. Establish project objective\nTake a look at your project plan and use the project objective you’ve established. This should go at the top of your work breakdown structure.\n2. Break out the tasks and subtasks\nNext, you want to break down the tasks into smaller and smaller tasks.\nThe point is to focus on the project deliverables. For example, you may have 10 large tasks, but underneath each of these you may have 20 subtasks that need to be completed in order to achieve the larger task.\nThe goal is to break out these tasks as a way to better meet the project objective.\nOne way to do this is with a Kanban board. This project management framework allows you to make each subtask its own card, with due dates, a description and team members assigned. These cards belong to a larger project, which you can view all at once as one board.\n\n3. Assign project phases\nDepending on how large or complex your project is, you’ll want to establish phases of the project.\nThis will make it easier to create a project timeline from your WBS.\nFor example, your phases might be: \n\nInitiation \nPlanning\nExecution\nResults\n\nCreate your Kanban boardVisualize tasks and progress with Hubstaff Tasks\nWBS best practices\nNow, some words of advice for making your WBS the best possible working document. Here are some WBS best practices to keep in mind.\nThink about tasks carefully\nYou’ll want to spend time thinking about what work needs to be completed.\nUse your WBS as a way to organize the most important tasks. Remove any tasks that seem unnecessary or unrelated.\nAlso, look at your main tasks. Can each subtask fully meet the needs of the main tasks?\nList tasks once\nIf you have a complex project, it’s easy to start listing a bunch of tasks without looking at it from a high level.\nStep back and make sure you are only listing each task once.\nYou don’t want to clutter your process or confuse your team members with two people doing the same or redundant work.\nFocus on deliverables\nThe point of a WBS is to focus on outcomes and not the actions needed to meet those deliverables.\nFor example, if you were building a car, you would list tire pressure control system and not create proper tire pressure in each tire.\nDon’t go too small\nThink attainable and realistic when creating subtasks.\n The rule of thumb is either 80\/20 or 10 hours.\nIn other words, subtasks should take no longer than 80 hours to complete, or 10 days.\nA work package should take no longer than a month to complete. When you go through your project tasks make sure they are doable in a reasonable timeframe and they are not broken out too much, either.\nTrying to take on too much or too little will lead to incomplete or subpar projects.\nCreate project phases\nProjects range in size and complexity.\nHowever, if you create at least three project phases, you will better organize the project and the team.\nFor example, these phases may be called the initiation phase, planning stage, and execution phase.\nAssign team members\nOnce you have a work breakdown structure created, assign each team member the tasks and subtasks.\nThere should be no overlap or missed tasks, and one team member should be accountable for the main tasks. That person takes ownership, and can check to see if all subtasks are completed on time.\nWork breakdown structure templates for project management\nThere are several work breakdown structure options to get you started. Choose the one that works best for keeping your team on task and organized.\nDownload your own WBS structure template\nWork breakdown structure templates for project management\nThere are several work breakdown structure options to get you started. Choose the one that works best for keeping your team on task and organized.\nDownload your own WBS structure templates\nFill out the form below to get your WBS structure templates.\n\n\n\nTree structure\nThe tree structure is a more visual option. Just like the name suggests, you start with a main objective and branch out to three or four sub-objectives to meet the overall project goal.\nThen, you create more and more subtasks to complete each sub-objective. This WBS can be created in Microsoft Word or a chart design program.\nOutline view\nThe outline view is just what it sounds like.\nYou start with the main objective, list sub-objectives and then list tasks to be completed in order under each project phase.\nThis is a good option if you need to make changes throughout the project. Items can easily be shifted around. The outline view can be created in Microsoft Word.\nHierarchical structure\nThe hierarchical structure is a lot like the outline view, but doesn’t include indentation.\nThis view may be harder to read, but it makes more sense if you have a complex project.\nIndentation in the outline view takes up space and requires a larger document when you have multiple project levels.\nThis hierarchical structure can be created in Microsoft Excel.\nTabular view\nThe tabular view is another work breakdown structure in project management that can be created in Microsoft Excel.\nIt lists project phases in levels with level one being the project objectives, level two being the main phases, and level three being the subtasks.\nPerfecting your work breakdown structure\nSpending time crafting the ideal project plan and assessing the risk management in project management are critical components of any project roll out.\nBut don’t forget to spend time creating the ideal work breakdown structure. Not only will it ensure all tasks are completed by the team on time, but you’ll uncover unforeseen issues before they derail your project.\nThe more you can plan and organize your project, the better the end result will be for your team and the company.