How to create a WBS: a practical Work Breakdown Structure guide

In Project Management, one of the most common mistakes is starting work without having a clear picture of everything that needs to be done.

The result? Delays, unexpected costs and the dreaded scope creep — the uncontrolled expansion of project objectives.

The solution is one of the foundations of solid planning: the WBS, or Work Breakdown Structure.

In this article, we will look at what a WBS is, why it is essential and, above all, how to create one step by step. Mokapen

What exactly is a WBS?

Imagine you need to build a house.

You cannot simply say “build the house”. You need to think about foundations, walls, roof, systems and finishes.

A WBS works in the same way: it is a hierarchical breakdown of the entire project scope into smaller, more manageable components.

It is not a simple To-Do List.

It is a structured map of the deliverables the project must produce. Mokapen

The golden rule: the 100% Rule

The most important principle behind a WBS is the 100% Rule.

The WBS must include 100% of the work defined by the project scope.

• If a piece of work is not in the WBS, it is outside the project.
• If something appears in the WBS but does not contribute to the final objective, it should be removed. Mokapen

The 4 levels of a WBS

To create order, the project is broken down into hierarchical levels:

1. Level 0 – The project
   The final objective, for example “New e-commerce website”.

2. Level 1 – Main phases or deliverables
   The major areas, such as Design, Development, Content and Testing.

3. Level 2 – Sub-deliverables
   The specific components of each area. For example, under Design: Wireframes, UI Kit and Mockups.

4. Level 3+ – Work Packages
   The lowest level of the structure. These are work packages that can be assigned to one person or team and estimated in terms of time and cost. Mokapen

How to create a WBS in 5 steps

Here is a practical process to move from a project idea to a structured Work Breakdown Structure.

1. Define the final objective

Write the project name clearly at the top.

This is your Level 0.

Make sure the project Scope Statement is clear before you begin breaking the work down.

2. Identify the main deliverables

Ask yourself:

“What are the major components that, together, make up the finished project?”

Do not think in terms of actions such as “write code”.

Think in terms of tangible outcomes such as “Shopping Cart Module” or “User Database”. Mokapen

3. Break down the deliverables

Take each main deliverable and divide it into smaller components.

Keep asking:

“What is this element made of?”

For example:

• Project: Gala Dinner
  • Macro-area: Catering
    • Menu
    • Drinks
    • Service staff
    • Table setup

The goal is to progressively reduce complexity until the work becomes easy to understand and manage. Mokapen

4. Stop at the Work Package level

When should you stop decomposing the work?

When a component is small enough to be:

• assigned to one clear owner;
• estimated accurately in terms of time and cost;
• completed within a reasonable period.

A commonly used guideline is the 8/80 rule: a Work Package should generally require no less than 8 hours and no more than 80 hours of work. Mokapen

5. Review and code the structure

Assign a unique code to each element, for example:

• 1.0
• 1.1
• 1.1.2

This makes communication, tracking and project accounting easier.

Finally, apply the 100% Rule once again to make sure nothing has been forgotten. Mokapen

Practical example: creating a mobile app

Here is what a simplified WBS might look like:

• 1.0 Mobile App XYZ
  • 1.1 Project Management
    • 1.1.1 Planning
    • 1.1.2 Progress meetings
  • 1.2 Design
    • 1.2.1 User research
    • 1.2.2 Wireframes
    • 1.2.3 Clickable prototype
  • 1.3 Frontend Development
    • 1.3.1 Login screen
    • 1.3.2 Home page
    • 1.3.3 User profile
  • 1.4 Backend Development
    • 1.4.1 Server setup
    • 1.4.2 Database API
  • 1.5 Release
    • 1.5.1 Beta testing
    • 1.5.2 Store publication Mokapen

Creating a WBS requires some extra effort at the beginning, but it can save much more time during execution.

It becomes the map that keeps the team from losing direction.

Once the Work Breakdown Structure is complete, you have a solid foundation for building the project schedule, creating a Gantt chart, estimating the budget and assigning resources.

The next step is to transform Work Packages into activities scheduled over time.