Multi-Cloud as a Product: JP Morgan's Strategic Shift

The Productization of Multi-Cloud

The core argument presented by Albinati and Mahajan at QCon London 2026 – that multi-cloud strategy should be treated as a product rather than a project – is a profound and necessary reframing for many enterprises. The article effectively highlights the pitfalls of the ad-hoc, technically-driven approach, which often results in increased costs, operational complexity, and fragmented engineering efforts. By advocating for a product-centric mindset, organized around capabilities (observability, cost management, identity, etc.) rather than siloed cloud providers, JP Morgan Chase is demonstrating a mature understanding of how to manage distributed cloud environments sustainably. The emphasis on structured demand governance and the concrete example of 'Frankenstein logging' being solved through a product lens provides tangible evidence of this approach's benefits, such as reduced log volume and faster incident resolution. This perspective is particularly relevant in the current landscape where AI workloads are increasingly driving the need for specialized cloud resources, potentially exacerbating existing multi-cloud fragmentation if not managed strategically.

However, while the product management analogy is powerful, its implementation within large, complex organizations like JP Morgan Chase presents its own set of challenges. The transition from a project-based to a product-based team structure requires significant organizational change management, including potential shifts in roles, responsibilities, and team dynamics. Defining clear ownership and accountability for these 'capability products' across different business units and cloud environments can be intricate. Furthermore, the article touches upon 'golden paths over bespoke one-offs,' which implies a need for robust platform engineering teams capable of building and maintaining these standardized solutions. The success of this strategy hinges on the maturity of the organization's platform engineering capabilities and its willingness to invest in them. While the 'console test' for logging offers a practical benchmark, developing similar tangible metrics and governance frameworks for other capabilities will be crucial for widespread adoption and consistent outcomes. The article implicitly suggests that portability isn't always the answer, favoring optimized contracts and SLAs, which is a pragmatic stance but requires deep vendor management expertise. The long-term implications for vendor lock-in and negotiation power need careful consideration as organizations lean into differentiated cloud services rather than aiming for abstract portability.

Key Points

• Enterprises are often approaching multi-cloud adoption incorrectly by treating it as a technical project rather than an organizational product.
• The accidental nature of multi-cloud adoption (acquisitions, shadow IT, AI workload demands) leads to fragmentation and complexity.
• Shifting from cloud-provider-centric organization to capability-centric organization (observability, cost management, identity) is key.
• Treating multi-cloud as a product involves structured demand governance, clear intake processes, and planning cadences.
• Practical examples, like improving logging platforms by understanding user needs and filtering data at the edge, demonstrate product-like improvements.
• Key principles include: capabilities over silos, shared discovery over isolated priorities, golden paths over bespoke solutions, governance by design, and resilience over mere portability.

---

📖 Source: QCon London 2026: Your Multi-Cloud Strategy Is a Product Problem — Treat It Like One