Decomposition: Breaking a Large Problem into Smaller Pieces

Decomposition is the process of taking a large goal and dividing it into smaller, understandable tasks and steps. It does not make the goal less important or change its purpose. Instead, it makes the work visible: people can see what needs to happen, in what order, who is responsible, and how each completed piece contributes to the whole.

A large problem often feels difficult because many decisions, dependencies, and uncertainties are mixed together. Breaking it into smaller pieces lets a person focus on one meaningful task at a time while still keeping sight of the overall outcome.

Large goal
    │
    ├── Task 1
    │      ├── Step 1
    │      └── Step 2
    │
    ├── Task 2
    │      ├── Step 1
    │      └── Step 2
    │
    └── Task 3
           ├── Step 1
           └── Step 2

Why Break Work Down?

The main purpose of decomposition is not simply to create a longer list of work. It is to create a plan that people can understand, use, inspect, and improve.

Clarity

A large goal can be vague: “organize an event,” “complete a study,” or “improve a service.” Smaller tasks turn that vague goal into concrete actions. Each task should have a recognizable purpose, and each step should move the work forward.

Clarity helps people distinguish what has already been completed from what remains uncertain. It also reveals dependencies. For example, a venue must usually be chosen before invitations can include a location.

Reuse

Many large efforts contain tasks that will be needed again. A clear set of steps for planning a meeting, reviewing information, approving a request, or preparing materials can be reused in future situations.

Reuse does not mean repeating work without thought. It means preserving a proven approach so that people can adapt it rather than start from nothing each time.

Checking

Smaller tasks make it possible to check progress and quality before the entire effort is complete. Instead of discovering a serious problem at the end, people can review each important result along the way.

Checking can answer questions such as: Is this step complete? Does it meet the expected standard? Is important information missing? Does the next task have what it needs to begin?

Collaboration

A large goal often requires more than one person. Breaking it into tasks allows people to share work without each person needing to manage the whole effort at once.

Collaboration works best when each task has a clear outcome, a responsible person or group, and a known connection to other tasks. This reduces duplicate effort, missed handoffs, and confusion about who should act next.

Shared goal
    │
    ├── Planning task ────────▶ Person or group A
    ├── Preparation task ─────▶ Person or group B
    ├── Review task ──────────▶ Person or group C
    └── Final delivery task ──▶ Person or group D

A Practical Process

Start with the outcome, not the list of activities. State what success should look like in plain language. Then identify the major tasks that must be completed to reach that outcome. For each task, identify the smaller steps required, the information or materials needed, the person responsible, and the point at which the task can be checked.

A useful process is:

1. Describe the final outcome clearly.
2. Identify the major tasks needed to produce that outcome.
3. Divide each major task into smaller steps only until the next action is clear.
4. Put tasks in a sensible order and identify which tasks depend on earlier work.
5. Assign responsibility and agree on how each important result will be checked.
6. Review the plan as work progresses, then adjust it when new information appears.

The right level of detail depends on the situation. A task is too broad when people do not know what to do next. It is too narrow when the plan becomes a distracting list of tiny actions that no longer help people understand the work.

Example 1: Simple — Hosting a Dinner

Large goal: Host a dinner for several friends on Saturday evening.

The goal sounds simple, but it includes several smaller tasks. Separating them prevents common problems such as buying ingredients too late, preparing more food than can be cooked at once, or discovering that a guest has a dietary restriction after the menu is chosen.

Host a dinner
    │
    ├── Plan the meal
    │      ├── Ask guests about dietary needs
    │      ├── Choose dishes
    │      └── Make a shopping list
    │
    ├── Prepare for guests
    │      ├── Confirm who is attending
    │      ├── Set the table
    │      └── Prepare drinks and seating
    │
    └── Prepare the food
           ├── Shop for ingredients
           ├── Prepare items that can be made early
           └── Cook and serve the meal

Clarity comes from knowing that “host a dinner” involves planning, preparation, and serving rather than one undefined activity.

Reuse comes from keeping a meal-planning checklist that can be adapted for future dinners.

Checking happens when the guest list, shopping list, and table arrangements are reviewed before the cooking begins.

Collaboration is possible when one person shops, another prepares a dish, and another sets the table. The tasks are distinct but contribute to the same meal.

Example 2: Medium Complexity — Organizing a Student Workshop

Large goal: Organize a one-day workshop for students on a selected topic.

This goal involves people, space, materials, communication, and timing. The tasks have dependencies: the date and location should be confirmed before participants receive final details, and materials should be prepared before the workshop begins.

Organize a student workshop
    │
    ├── Define the workshop
    │      ├── Choose the topic and intended audience
    │      ├── Set learning goals
    │      └── Decide the date and length
    │
    ├── Arrange logistics
    │      ├── Reserve a location or online meeting space
    │      ├── Confirm presenters and support people
    │      └── Prepare accessibility arrangements
    │
    ├── Communicate with participants
    │      ├── Create an announcement
    │      ├── Open registration
    │      └── Send reminders and practical details
    │
    ├── Prepare the session
    │      ├── Create activities and materials
    │      ├── Prepare equipment and handouts
    │      └── Review the schedule
    │
    └── Run and review the workshop
           ├── Welcome participants
           ├── Deliver activities and support questions
           ├── Collect feedback
           └── Record improvements for next time

The sequence can also be viewed as a flow of completed results:

Topic and goals
      │
      ▼
Date, location, and presenters
      │
      ▼
Participant communication
      │
      ▼
Materials and final schedule
      │
      ▼
Workshop day
      │
      ▼
Feedback and improvement

Clarity ensures that the workshop is not treated only as “an event to schedule.” It makes visible the separate work of defining the purpose, arranging logistics, communicating, preparing materials, and reviewing results.

Reuse occurs when the workshop plan becomes a template. Future workshops can reuse registration messages, accessibility checks, feedback questions, and a preparation timeline.

Checking occurs at several points: confirm the room reservation, review whether materials match the learning goals, verify that participants received essential details, and examine feedback after the event.

Collaboration becomes manageable because tasks can be shared. One group can prepare content, another can manage registration and communication, and another can prepare the room and equipment. Clear handoffs prevent gaps between those efforts.

Example 3: Complex — Improving a Community Flood-Preparedness Plan

Large goal: Improve a community’s ability to prepare for, respond to, and recover from flooding.

This is a complex problem because it affects many people and involves changing conditions. It includes physical infrastructure, public communication, emergency response, vulnerable residents, funding, maintenance, and long-term learning. No single person or group can complete the work alone.

The plan must therefore be divided into connected tasks that can be understood, checked, and coordinated.

Improve community flood preparedness
    │
    ├── Understand risks and needs
    │      ├── Identify flood-prone areas
    │      ├── Review past flood impacts
    │      └── Identify people and services needing extra support
    │
    ├── Set priorities and prepare the plan
    │      ├── Define desired outcomes
    │      ├── Choose actions based on urgency and impact
    │      └── Estimate resources and funding needs
    │
    ├── Improve physical readiness
    │      ├── Inspect drainage and protective structures
    │      ├── Identify maintenance and repair work
    │      └── Prepare emergency supplies and access routes
    │
    ├── Improve communication and response readiness
    │      ├── Define warning messages and communication channels
    │      ├── Prepare evacuation and shelter arrangements
    │      └── Practice response activities with relevant groups
    │
    └── Support recovery and long-term improvement
           ├── Document impacts after flood events
           ├── Coordinate recovery support
           ├── Review what worked and what failed
           └── Update the plan

A complex effort also has tasks that proceed at different times but must remain connected:

Risk information ───────────┐
                            │
Community needs ────────────┼──▶ Priorities and plan ──▶ Action schedule
                            │                                  │
Available resources ────────┘                                  ▼
                                                       Preparedness actions
                                                               │
                                                               ▼
Flood event or practice ──▶ Review results ──▶ Update future actions

Clarity is essential because “be better prepared for floods” is too broad to guide decisions. The smaller tasks distinguish understanding risk, choosing priorities, maintaining physical readiness, communicating with residents, responding during an emergency, and learning afterward.

Reuse matters because floods and other emergencies may occur repeatedly. Warning messages, contact lists, shelter procedures, assessment forms, and review methods should be maintained and adapted rather than recreated during each emergency.

Checking must occur throughout the effort. Risk information should be reviewed for accuracy, maintenance work should be inspected, warning messages should be tested, practice activities should be reviewed, and the plan should be updated after a real event or exercise.

Collaboration is central. Community leaders, emergency services, infrastructure teams, health and support organizations, schools, residents, and local businesses may all hold different parts of the work. A shared plan clarifies how their tasks connect and who is responsible for each handoff.

Keeping the Pieces Connected

Breaking work into smaller pieces should not cause people to lose sight of the whole goal. Each task should have a clear connection to the desired outcome, and each person should understand how their work enables the next step.

A helpful final review asks four questions:

Decomposition is successful when a large problem becomes understandable without becoming fragmented. The tasks and steps should be small enough to guide action, but connected enough to show how many separate efforts produce one meaningful result.