WBS Workshop: How to Unlock Project Success

Workshop Setup: Preparing for Success (10-15 minutes)

Before you even begin the decomposition, a little preparation goes a long way. This ensures your team starts with a shared understanding and the right tools.

1. Gather Your Essentials:

• Large Whiteboard or Flip Charts: Absolutely crucial for visual collaboration.
• Sticky Notes (various colors if possible): Ideal for individual brainstorming and easy reorganization.
• Markers: Plenty of them!
• Project Charter/Scope Statement: The definitive source of your project’s high-level objectives and deliverables. Have it visible (projected, printed, or written on the whiteboard).
• WBS Template Examples (Optional but helpful): Show a couple of basic, non-related WBS structures (e.g., building a house, planning a wedding) to illustrate the hierarchical concept, but emphasize that your project’s WBS will be unique.
• “Parking Lot” for Out-of-Scope Items: A designated area on the whiteboard for ideas that come up but are clearly not part of this project’s scope. This acknowledges contributions without derailing the main effort.

2. Assemble the Right Team:

As discussed previously, this isn’t a solo activity. Ensure you have:

• The Project Manager (Facilitator): Your role is to guide the process, keep it on track, enforce the rules, and ensure everyone participates.
• Core Project Team Members: Those who will be doing the work or are critical subject matter experts. Their ground-level knowledge is invaluable.
• Key Stakeholders (as appropriate): Especially those whose input is crucial for defining deliverables and acceptance criteria.
• Subject Matter Experts (SMEs): For specific technical or functional areas.

3. Set the Stage & Review the “Why”:

• Reiterate the Purpose: Briefly recap the importance of the WBS (as discussed in the previous blog post). Emphasize that this exercise defines what the project will deliver, not how it will be done, and crucially, not when or how long it will take. Stress that this isn’t just “busy work” but a crucial step for clarity, estimation, and avoiding scope creep.
• Address the “Date Anxiety” Up Front: This is a key point for team buy-in. Acknowledge that committing to dates can feel daunting, especially with unknowns. Explicitly state that this WBS workshop is not about setting final deadlines or durations. Instead, it’s about breaking down the work into logical, manageable pieces so that later, in the scheduling and estimation phases, those dates can be set with much greater confidence and accuracy. Frame the WBS as the tool that enables realistic scheduling, rather than being the schedule itself. This helps alleviate early fears of commitment.
• Define “Deliverable”: Ensure everyone understands that a WBS element is a tangible outcome or component, not an activity. Provide a simple example: “House” (project), then “Foundation” (major deliverable), not “Digging trenches.”
• Introduce the “100% Rule”: Explain that the final WBS must encompass all work required for the project and nothing more.
• Explain the “Mutually Exclusive” concept: Each piece of work should only belong to one place in the WBS.

---

Step 1: Define the Project (Level 0) (5 minutes)

This is your starting point, the absolute top of your WBS.

• Action: Write the official Project Name clearly at the very top of your whiteboard or first flip chart. This represents 100% of the project scope.
• Example: If your project is “Develop New Customer Relationship Management (CRM) System,” that’s your Level 0.

---

Step 2: Identify Major Project Phases or Key Deliverables (Level 1) (20-30 minutes)

This is where you start to break down the big picture into its primary components. There are two common approaches here:

• Phase-Based: If your project naturally follows distinct sequential phases (e.g., initiation, planning, execution, closing), use these as Level 1.
• Major Deliverable-Based: If your project is more product-centric, identify the biggest, most critical deliverables that, when combined, make up the entire project.

Actions:

1. Brainstorm Individually (Silent Time – 5 mins): Give each team member a stack of sticky notes. Ask them to write down the major phases or top-level deliverables they envision for the project. One idea per sticky note. Encourage quantity over perfection.
2. Affinity Grouping (10-15 mins):
   • Have everyone put their sticky notes on the whiteboard under the Project Name.
   • As a team, group similar sticky notes together. Look for natural categories or logical groupings.
   • Discuss and label these groupings. These labels will become your Level 1 WBS elements.
3. Refine and Consolidate: Ensure these Level 1 elements genuinely represent distinct major parts of the project. Aim for 4-8 Level 1 elements for most projects; too many can indicate insufficient grouping.
   • Facilitator Tip: Challenge the team: “Does this Level 1 element, combined with the others, truly represent 100% of the project?” “Are there any overlaps between these Level 1 items?”

• Example (Phase-Based):
  • Project: Develop New CRM System
    • Initiation Phase
    • Planning Phase
    • Development Phase
    • Testing Phase
    • Deployment Phase
    • Project Closeout
• Example (Deliverable-Based):
  • Project: Develop New CRM System
    • Requirements Document
    • System Design
    • Core System Modules
    • Integration Components
    • User Training Materials
    • Deployment Plan

---

Step 3: Decompose Each Level 1 Element (Level 2, 3, etc.) (40-60 minutes)

This is the core of the WBS creation. You’ll take each Level 1 element and break it down further, then break down those elements, continuing until you reach the “work package” level.

Process for EACH Level 1 Element:

1. Focus on One Branch at a Time: Pick one Level 1 element.
2. Brainstorm Sub-Deliverables (Silent Time – 5 mins per branch): Ask team members (especially those with expertise in this area) to write down the major sub-deliverables or components required for that specific Level 1 item to be completed. Again, one idea per sticky note.
3. Place and Group (10-15 mins per branch):
   • Place these new sticky notes under the relevant Level 1 item.
   • Work as a team to group them logically. These are your Level 2 elements.
   • Iterate: For each Level 2 element, repeat the brainstorming, placing, and grouping process to create Level 3 elements, and so on.

When to Stop Decomposing? (The “Work Package” Level)

This is crucial and often where teams struggle. Stop when each element meets these criteria:

• Estimable: You can confidently estimate the cost, effort, and duration of the work required for this element. Crucially, this is where the WBS becomes granular enough for reliable estimates to be developed later. We are not estimating now, just breaking down to a level that permits estimation.
• Assignable: It’s a discrete piece of work that can be assigned to a single person or a small, clearly defined team.
• Manageable: You can monitor and control progress on this element.
• Small Enough: It’s typically no longer than 80 hours of effort, and no smaller than 8 hours (the “8/80 Rule” guideline). Adjust this based on your project’s granularity needs.
• Unique Output: It represents a clear, tangible deliverable, document, or component.

This lowest level is your “work package.” Mark them distinctly (e.g., with a different colored sticky note, or by drawing a box around them).

Addressing the “Unknowns” – Research and Discovery Work Packages (Crucial for Learning Teams):

What happens when you can’t definitively break down a deliverable because you lack information, documentation, or expertise? This is a common challenge, especially with new team members or legacy systems. The solution is to explicitly incorporate research and discovery as work packages within your WBS.

• Identify the Knowledge Gap: When a team member says, “We don’t know what changes are needed for system X because we can’t find the documentation,” this is your cue.
• Create a “Discovery” or “Analysis” Work Package: Instead of guessing or leaving it blank, create a specific work package (or a set of work packages) focused on resolving that unknown.
  • Example: If you have “System Integration Component” as a Level 2 item, and you don’t know the full scope of integration with an old “Legacy Billing System”:
    • System Integration Component (Level 2)
      • Legacy Billing System Integration (Level 3)
        • Legacy Billing System Documentation Review (Work Package)
        • Legacy Billing System Interface Analysis (Work Package)
        • Legacy Billing System Integration Requirements Document (Work Package)
        • Legacy Billing System Integration Design (Work Package)
• Estimate the Discovery Work: Even if you can’t estimate the final integration effort, you can estimate the effort required for the research, documentation review, interviews with SMEs, or prototyping needed to define the next level of work. This provides a tangible, measurable piece of work.
• Define its Deliverable: The deliverable for a discovery work package isn’t the final product, but rather the information needed to define the next steps. For example: “Integration Impact Assessment Report,” “Updated System Architecture Diagram,” or “Detailed Integration Requirements.”
• Acknowledge Uncertainty: In the WBS dictionary for these discovery work packages, explicitly state that subsequent work packages (e.g., “Implement Legacy Billing System Integration”) are dependent on the outcome of this discovery phase and their scope/estimates are currently unknown and will be refined later. This manages expectations transparently.

Facilitator Tips for Decomposition:

• Constantly Refer to the “100% Rule”: For each level, ask: “Do these sub-elements collectively represent 100% of the parent element’s scope?”
• Enforce “Deliverable-Oriented”: If someone suggests an activity (“Conduct meetings”), gently redirect: “What is the deliverable from those meetings? (e.g., ‘Meeting Minutes Document,’ ‘Requirements Sign-off’).”
• Avoid Over-Decomposition (Analysis Paralysis): If you’re going too deep too quickly, remind the team of the “8/80 rule” or similar guidelines. The goal is manageable chunks, not an exhaustive list of every single task.
• Ask Probing Questions:
  • “What are the major components of X?”
  • “What do we have to produce to say X is complete?”
  • “Is anything missing if we only produce these items?”
  • “Is this item truly a single, assignable piece of work?”
  • Crucially: “What information do we not have that we need to figure out this part of the work?” (This specifically prompts for discovery work packages).
• Example (Continuing from CRM System with an unknown):
  • Project: Develop New CRM System
    • Development Phase (Level 1)
      • Core System Modules (Level 2)
        • User Management Module (Level 3)
          • User Authentication Feature (Work Package)
          • User Profile Management Feature (Work Package)
        • Sales Lead Management Module (Level 3)
          • Lead Capture Functionality (Work Package)
          • Lead Qualification Workflow (Work Package)
      • Integration Components (Level 2)
        • Accounting System API Integration (Work Package)
        • Legacy System Integration (Level 3)
          • Legacy System Documentation & Interface Analysis (Work Package) [Deliverable: Analysis Report & Refined Requirements]
          • (Subsequent work packages for implementation will be defined after this discovery work)
        • Email Marketing Platform Integration (Work Package)

---

Step 4: Review and Refine the Entire WBS (15-20 minutes)

Once you have a full hierarchical breakdown, it’s crucial to step back and review it collectively.

Actions:

1. Visual Walk-Through: As a team, slowly walk through the entire WBS, starting from Level 0 down to the work packages. Read each element aloud.
2. Check for Completeness (100% Rule):
   • Are there any obvious omissions? Did anything end up in the “Parking Lot” that actually belongs?
   • Does the sum of the parts truly equal the whole project?
3. Check for Exclusivity: Are there any overlaps? Does one work package sound like it’s covering the same ground as another? If so, combine or clarify.
4. Check for Deliverable Focus: Is every element, especially at the lower levels, a tangible output? If not, rephrase.
5. Check for “Work Package” Clarity:
   • Are the lowest-level items truly estimable, assignable, and manageable?
   • Is the level of detail consistent across different branches of the WBS? (e.g., you don’t want one branch broken down to individual clicks while another is still at a very high level).
   • Specifically check discovery work packages: Are they clear? Does their deliverable define what information will be gained? Is it clear that further decomposition depends on this work?
6. Seek Consensus: Encourage questions and debate. Ensure everyone understands and agrees with the structure. This is critical for buy-in.
7. Assign WBS Identifiers (Optional but Recommended – Do this after the workshop): Once finalized, assign a numerical coding system (e.g., 1.0 for Level 1, 1.1 for Level 2, 1.1.1 for Level 3, etc.). This makes it easy to reference specific elements.

---

Step 5: Document and Communicate (After the workshop)

The whiteboard is temporary; your WBS needs to be a permanent, accessible document.

Actions:

1. Photograph or Transcribe: Take clear photos of your whiteboard or carefully transcribe the WBS into a digital format.
2. Choose a Format:
   • Outline View: A simple indented list (e.g., in a word processor or spreadsheet) is effective for clarity.
   • Graphical View (Hierarchical Tree): Specialized WBS software or even drawing tools can create a visual tree diagram.
   • Spreadsheet: Useful for adding columns for WBS ID, brief description, and later, assigning responsible parties.
3. Add a WBS Dictionary (Crucial for Clarity and Addressing Unknowns): For each work package (and potentially higher-level elements), create a brief description. This dictionary should define:
   • What the element is (its scope).
   • What constitutes completion (acceptance criteria).
   • Any key assumptions or constraints.
   • For “Discovery” or “Research” Work Packages: Clearly state that the purpose of this work package is to gather information to define subsequent work. Explicitly note that the scope, effort, and even existence of future related work packages are dependent on the outcome of this discovery work and will be refined upon its completion. This is your formal way of managing uncertainty and acknowledging the iterative nature of planning when faced with unknowns.
   • This helps prevent ambiguity and ensures everyone has the same understanding.
4. Circulate for Review and Formal Approval: Share the documented WBS with all stakeholders for a final review. Obtain formal sign-off from the project sponsor or relevant authority, making it part of your project’s baseline documentation.
5. Store Centrally: Keep the WBS in a project repository (e.g., SharePoint, Google Drive, project management software) where it’s easily accessible to the entire team and stakeholders.

---

Key Takeaways for Your Workshop Facilitation:

• Stay Deliverable-Focused: This is the most common mistake. Constantly redirect discussions back to outputs, not activities.
• Embrace Iteration: The WBS isn’t created in one perfect pass. It’s an iterative process of breaking down, discussing, and refining. This includes planning for iterative discovery when facing unknowns.
• Clarify the Purpose of the WBS vs. Scheduling: Reiterate that the WBS enables better scheduling and estimation down the line; it is not the schedule itself. This addresses the “date anxiety.”
• Encourage Participation: Every team member has valuable insights. Ensure all voices are heard.
• Manage Scope During Creation: Use your “Parking Lot” for out-of-scope ideas. If a significant new scope idea emerges, note it, but defer formal scope change discussions until after the WBS is baselined.
• The WBS is a Foundation, Not the End: Remind the team that this document will be the basis for scheduling, resource planning, and cost estimation, solidifying its value. It also explicitly plans for the work required to gain clarity on unknowns, which is a crucial step before detailed planning can proceed.

By following these steps, you can lead your project team through a practical, engaging, and highly effective workshop to build a robust Work Breakdown Structure. This foundational effort will pay dividends throughout your project’s lifecycle, providing clarity, control, and a shared understanding that is essential for achieving project success, even when faced with initial unknowns or concerns about future commitments. Now, go forth and decompose!