The disruptive effect of digital business models is already visible, ranging from exponential growth to fast extinction. To succeed in digital business, organizations need much wider capabilities than conventional enterprise applications offerings. For example, a heavy manufacturer may need a solution consisting of embedded sensors within industrial equipment, software to aggregate and manage the data, storage and processing of large amounts of data, and data delivery to customers securely through a subscription service.
Technology providers, regardless of size, cannot accommodate technological complexity and rapid pace of innovation solely with the traditional make or buy options: they have to leverage the power of ecosystems.
In the enterprise applications space, ecosystems are not new. Software vendors (such as SAP, Oracle and Salesforce) have long created global networks of independent software vendors (ISVs) and consulting providers to complement their suite offerings. However, just offering a marketplace for partner applications and services is not sufficient to form an effective ecosystem. A technology provider can orchestrate an ecosystem by assuming the following responsibilities:
- Attract and recruit complementary partners.
- Define integration routes and provide relevant technologies and standards.
- Ensure customer-facing consistency without cannibalizing the core product roadmap and go-to-market model.
- Drive faster monetization.
In the just released note “Digital Business Redefines Application Software Ecosystems“, together with colleagues Stephen Crawford, Robert P. Anderson, Rajesh Kandaswamy, Alys Woodward and John Santoro, we look at how the advent of the digital business and cloud technologies has created more ways for technology providers to orchestrate and participate in enterprise applications ecosystems.
These ecosystems follow four archetypes:
- The Cloud Platform-led ecosystem: Orchestrated through use of common infrastructure.
- The Application Suite-led ecosystem: Orchestrated through a suite containing most of the solution features.
- The Experience-led ecosystem: Orchestrated through the definition of expected experiences across use cases and user personas.
- The Industry-led ecosystem: Orchestrated through jointly defined business requirements by industry members seeking standards-based interoperability.
The reference of each ecosystem to the four archetypes and its composition of participants will not be written in stone. Orchestrators may change priorities related to the ecosystem definition or capabilities they need from their participants.
Ecosystems adoption by enterprise applications buyers is still fairly limited, with the focus being still on custom applications and integration to fill in their digital platform gaps. We plan to do further research on this topic from a buyer perspective, related to the potential and challenges of the various technology provider ecosystems towards more effective and timely digital transformation. Meanwhile, I would love to hear your views as to the extent you are currently leveraging enterprise applications ecosystems in your own organizations and digital transformation roadmaps.
Read Complimentary Relevant Research
Leadership Vision for 2018: Infrastructure & Operations Leaders
I&O are key enablers for digital business. I&O leaders are accountable for delivering agility and innovation to their primary consumers...
View Relevant Webinars
Accelerating Deal Value Realization in Mergers & Acquisitions
With Tech M&A activities at unprecedented levels, Gartner continues to play an essential role with general managers and corporate development...
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.