Differentiating between Primary Outcomes and Enabling Outcomes
In the previous two chapters, we used several different practices to discover the Target Outcomes. Some of them are more functional-, application product-, and business-focused (the Why and Who), and some are more non-functional-focused (the How).
As we discover these different types of outcomes, we can explore relationships between them and see whether a hierarchy exists or not.
Gabrielle Benefield and Ryan Shriver explain7 that Enabling Outcomes, such as decreasing time to onboard new developers, improving test automation and reducing the time to build and deploy code, will hopefully improve primary outcomes such as improve customer experience.
This may just be a hypothesis that needs validation through experimentation and delivery.
Let's look at some common examples of outcomes that are a mix of primary and enabling outcomes.
- Increasing Speed...
