A customer outcome is a measurable improvement a customer experiences from using a product or service. In architecture modernization, outcomes also give teams a reason to change systems: the aim is better customer experience or business performance, not simply a new architecture or a completed list of features. section 3.0 section 1.2
Make the desired result clear before choosing an architecture. Product north stars—key metrics such as engagement or revenue—help distinguish progress toward a goal from delivery of predefined requirements. An independent value stream gives one team responsibility for a business subdomain and the freedom to discover product and technology solutions that contribute to those metrics. section 1.2 section 6.1.1
An airline’s modernization goals
A large airline sought differentiated customer experiences, faster innovation, new revenue opportunities, and better operational performance at lower cost. Its difficult-to-change monolith made those goals hard to pursue. EventStorming helped stakeholders explore domain boundaries and decide where largely independent teams could work. section 9.3.4
To connect a proposed change to a result, ask:
- Which customer or business improvement matters, and which product metric could show progress? section 1.2 section 3.0
- Which capabilities or heavily changing parts of the system need attention to support that improvement? section 3.0
- Can business and technology experts test the connection together rather than assuming an architecture pattern will deliver it? section 2.2.3
Use the result to prioritize a roadmap, then check whether decisions produced the expected value. Start small, learn from delivery, and adapt the plan; an outcome is a direction to validate, not a promise that every proposed change will work. section 16.0
