10. Setting Outcomes

In the previous chapter, we used practices to help extract lots of detail to confirm what problems we're going to solve, who we're solving them for, and our approach to solving them in an experimental and incremental way.

By using practices such as Impact Mapping and human-centered design, we should now have a good understanding of the customer and business pain points. Before we dive into developing software solutions, we need to translate those problems into potential business and customer outcomes. And we need to use all the information captured from those artifacts and the information radiated from those practices to ensure we deliver outcomes that will really matter.

In this chapter, we're going to explore all the learning done in the Discovery section of the Mobius Loop so far to clearly define and articulate the goals and outcomes the team is striving to deliver to happy stakeholders and end users. This includes:

• Explaining...