A business problem is the organizational difficulty or unmet need that motivates a system. Clarifying it means understanding why the system exists, whom it serves, and which outcomes matter before prioritizing delivery or automation. section 14.1.1 section 3.2.1
Use the problem to keep team decisions connected to business value:
- Contrast a vague feature goal with a measurable outcome that explains who benefits and why. section 3.2.1
- Prioritize critical workflows over attractive but nonessential functionality. section 14.1.1
- When implementation becomes difficult or expensive, seek another solution that achieves the same business outcome. section 3.2.1
From system purpose to critical workflow
For an online store, the business purpose is selling products without requiring physical visits. Finding products, purchasing them, and requesting refunds or replacements are more important than ratings, reviews, or recommendations because failure in the core workflows undermines the system's purpose. section 14.1.1
Figure 14.2 Actors and their goals on a Journey Map. You can add additional actors and goals as your understanding of the system under test expands.
Map actors and their goals to make the business context visible, then expand the map as understanding grows. section 14.1.1
