Home/Agentic AI/Goal-Oriented/Goal Decomposition

Goal-Oriented Planning

Master how agents define objectives and create strategic plans to achieve them

Why Decompose Goals?

Complex goals are overwhelming. Goal decomposition breaks ambitious objectives into smaller, manageable sub-goals. This creates a clear roadmap, enables parallel execution, and makes progress measurable.

🎯 Without Decomposition

  • Overwhelming complexity
  • Unclear where to start
  • Hard to track progress
  • Sequential execution only
  • No early wins

With Decomposition

  • Manageable chunks
  • Clear action items
  • Measurable milestones
  • Parallel task execution
  • Visible progress

Interactive Decomposition Tree

Explore how complex goals break down into actionable sub-goals. Click scenario tabs to see different examples!

MAIN GOAL
Plan a week-long trip to Tokyo
SUB-GOAL 1
Transportation
Book round-trip flights
Research airport transfers
Plan city transportation (JR Pass vs Metro)
SUB-GOAL 2
Accommodation
SUB-GOAL 3
Activities

Decomposition Strategies

🔢 Sequential Decomposition

Break goal into ordered steps that must happen in sequence.

Main Goal → Step 1 → Step 2 → Step 3 → Complete
Example: Cooking recipe (prep → cook → plate → serve)

Parallel Decomposition

Break goal into independent sub-goals that can be pursued simultaneously.

Main Goal → [Task A + Task B + Task C] → Combine → Complete
Example: Event planning (venue + catering + invitations run in parallel)

🌳 Hierarchical Decomposition

Break goal into categories, then break each category into tasks (multi-level).

Main Goal → Categories → Sub-Tasks → Atomic Actions
Example: Building a house (foundation → framing → electrical → plumbing → finishing)

🎯 Milestone-Based Decomposition

Define intermediate milestones with concrete deliverables.

Start → Milestone 1 (25%) → Milestone 2 (50%) → Milestone 3 (75%) → Complete
Example: Software project (MVP → Beta → Release Candidate → Production)

Best Practices

  • Keep sub-goals atomic: Each should be completable in one session
  • Make them testable: Clear success criteria for each sub-goal
  • Limit hierarchy depth: 2-3 levels max to avoid over-complication
  • Identify dependencies: Know what must happen before what
  • Enable parallelization: Structure independent tasks to run concurrently