Class Handout – Project Management / Organisation Why structure matters

1. Introduction: Why structure matters

Project work requires clarity of roles, but roles cannot function without a clear structure of the work itself.
Structure defines what needs to be done, how tasks connect, and how workstreams interact.
Without structure, even strong teams lose time, energy, and focus.

A project structure answers three foundational questions:

• What is the total scope of work?
• How is the work logically grouped?
• How do the groups connect and hand over?

This part of the course introduces the principles and logic behind effective structuring, supported by several examples:
the Lego metaphor, the Zoo organisation exercise, the Food grouping exercise, the Work Breakdown Structure, and the relay race example.

2. The Lego example: organising work vs. leaving it to chance

Scenario A: no structure

A team of twenty people stands in a room with a 100,000-piece Lego set and a single instruction manual.
The group receives the task to build the set together, without further preparation.

• The team gathers around the single manual.
• Some individuals begin without reading.
• Others try to interpret the manual simultaneously.
• Work begins, but progress is slow and chaotic.
• People block each other, duplicate steps, or assemble pieces incorrectly.

Scenario B: structured approach

Before the build starts, the manual is reviewed and the work is structured.

• The overall system is decomposed into several logical work packages.
• Each work package includes a subset of pieces and a dedicated section of the plan.
• The pieces are pre-separated accordingly.
• Small teams work in parallel, each completing its package.
• The final assembly connects all modules.

Key insight: organising work before starting increases speed, quality, and coordination. Structure is not a bureaucratic exercise. Structure enables productivity.

3. The MECE principle: the foundation of good structure

The slides introduce the Pyramid Principle and the MECE logic:

• Mutually
• Exclusive
• Collectively
• Exhaustive

MECE structures are the backbone of good project organisation.

3.1 Mutually exclusive

Each element belongs to one and only one group. There are no overlaps and no ambiguity about responsibilities.

3.2 Collectively exhaustive

All necessary elements appear in the structure. Nothing essential is forgotten and no blind spots remain.

3.3 Why MECE matters

Without MECE, teams fall into disputes about boundaries, responsibilities, and missing topics.
MECE removes friction points and establishes clarity.

4. The Zoo example: recognising good and bad structures

The Zoo exercise illustrates that multiple structures can be good, but mixed logic always produces problems.

4.1 Examples of good structures

A. Functional grouping

• Animal care
• Sales and service
• Facility and maintenance
• Administration

B. Regional grouping

• Africa area
• Europe area
• Asia area
• America area

C. Biological classification

• Mammals
• Birds
• Fish
• Amphibians and reptiles

4.2 Example of a bad structure

A problematic structure combines elements such as:

• Animal care
• Europe, Asia, America
• Birds

Immediate questions arise:

• Who is responsible for animal care of Asian birds?
• Who covers sales for African fish?

The logic mixes functions, geography, and species. This creates overlaps, gaps, and confusion.

Key insight: bad structure becomes visible even without deep context knowledge. When boundaries are unclear, the structure is not MECE.

5. The Food example: many structures can be valid

The food exercise shows that multiple structures can be logically correct as long as they are MECE.

Possible MECE structures include:

• By nutrients (protein, fat, carbohydrates)
• By origin (plant-based, animal-based)
• By temperature sensitivity (refrigerated, shelf-stable)
• By usage occasions (breakfast, lunch, dinner, snacks)
• By alphabet
• By item colours
• By rows or columns in the image

The core point: there is not one correct structure. There are many possible structures.
The requirement is simple: structures must be logical, distinct, and complete.

6. Work Breakdown Structure (WBS): definition and logic

A Work Breakdown Structure decomposes a project into manageable elements. It represents the entire scope of work in a structured and logical format.

The WBS logic:

• Top level: the project goal.
• Second level: major work packages.
• Third level: tasks and sub-tasks.

A WBS resembles an organisational chart, but it captures work, not people.

6.1 Purpose of a WBS

• Creates full scope visibility.
• Groups related tasks logically.
• Prevents overlaps.
• Forms a basis for planning, staffing, timing, and risk management.
• Reveals required competencies.

6.2 Identifying poor WBS design

A problematic WBS often mixes different types of elements on the same level, for example:

• Topics (Configuration, Deployment)
• Activities (Perform testing)
• Status concepts (Customisation upgrade)

The structure is neither MECE nor consistent:

• Levels overlap logically.
• One work package carries almost the entire workload.
• Other packages contain only fragments or nothing at all.

A non-MECE WBS causes planning challenges, unclear responsibilities, misalignment, and delays.

7. The House-Building WBS: a positive example

The house-building exercise decomposes a construction project into clear work packages.

1. Land acquisition
   • Search and selection
   • Financing approval
   • Notarial purchase
2. Planning
   • Select architect
   • Create official plans
   • Submit documents to authorities
3. Earthworks
   • Clear land
   • Remove debris
   • Prepare construction site
4. Shell construction
   • Excavate basement
   • Build foundation walls
   • Install windows
   • Build roof
5. Interior construction
   • Electrical installation
   • Heating system
   • Painting
   • Flooring
   • Kitchen and bathrooms
   • Remaining rooms
6. Garden and exterior
   • Level terrain
   • Plant trees
   • Prepare lawn

Each work package contains similar types of tasks. The packages do not overlap and together they cover the entire scope.
The structure also reveals required skills such as architects, construction specialists, and electricians.

A WBS is independent of time. Time planning comes later. The WBS expresses logical grouping, not sequence.

8. Cooperation at the boundaries: the relay race

Structure alone does not create success. High-performing teams add another capability: cooperation at the interfaces.

The relay analogy

In a 4x100m relay, a team with faster individual runners can still lose to a slower team.
The difference often lies in the baton handover.

• The baton handover cannot be fully pre-planned.
• Success depends on awareness, adaptation, and coordination.
• Both runners adjust dynamically within the exchange zone.

Even a perfectly structured project fails without efficient cross-team cooperation.

Insight for projects

Work packages and responsibilities define boundaries, but teams must still:

• Support each other at the edges.
• Anticipate upcoming tasks.
• Adjust to unexpected developments.
• Engage actively in interface management.

9. Integrated takeaways

• Structure the work.
  Use a MECE WBS to establish clarity, focus, and parallelisation.
  A project without structure becomes slow and chaotic.
• Organise teams around the structure.
  Match skills to work packages and ensure that boundaries are logical and complete.
• Enable cooperation across boundaries.
  Even with strong structure, success depends on how well interfaces work.
  Cooperation creates speed, quality, and resilience.