This article discusses the importance of determining which parts of a product, user experience, and technology each team owns while organizing technology teams to build digital products and services. It explains the model for describing the architecture of a business which includes products, product bundles, business value types, portfolio, product variants, user journeys and experiences, and product features. It also provides a clear understanding of domain information and services that product features leverage while exposing domain information and capabilities. This article can help technology companies and organizations to discuss the trade-offs of organizational design patterns while creating common ground on the language used to define responsibilities a team may own.
