I recently spent a few days in Chicago (well, in Rosemont, to be precise) with the Gartner/AMR Research SAP and Oracle Peer Forums at their semi-annual summit. It’s always great to participate in these events and network with some of the top SAP and Oracle customers. We used the opportunity to discuss key initiatives and identify best practices for how to extract the most value out of their application portfolios.
During the sessions, we talked about improving total cost of ownership and how to elevate the role of IT in the business. A lot of the informal conversation was centered on the best ways to extend and evolve application portfolios to meet the changing requirements of the business. Many of the Forum members continually struggle to keep up with these demands because of the inflexibility of the application architecture and the challenges of maintaining one complex application portfolio. A big part of the problem is that many of the systems have been architected to focus on improving internal processes and operations, while much of the business strategy has shifted to a network-based orientation.
Last week I spent two full days with Gartner colleagues Yvonne Genovese, Jim Shepherd and Val Sribar to talk about application research, and we kept coming back to the same question: Do companies need to rethink their application strategies to better reflect today’s collaborative business models? The answer sure seemed like yes, so we thought about the best way to accomplish this.
All Apps Should Not Be Created Equal
The fundamental idea from our discussions is that too many organizations have built their application strategies on a flawed premise: having a single, integrated application portfolio that’s managed against a common set of criteria and evolves on a common timeline. But this has led to the mess many companies are in. Any changes to systems require a tremendous amount of effort because even simple modifications have far-reaching implications to foundational systems.
We identified an approach to reclassify the applications based on the role they play in the organization to help develop a level of abstraction that can accelerate the pace of change for IT:
- Systems of record — These are the systems that form the foundation for your enterprise and manage the information necessary to run your business. They’re transaction oriented and are core to financial reporting and regulatory compliance. Their pace of change is slow, with their life span measured in decades. They’re most likely delivered on premises.
- Systems of differentiation — These are the systems that help drive differentiation for your company. They connect to customers and trading partners, as well as help speed time to market and overall agility. They’re more collaborative in nature, and while they leverage data from systems of record, they capture and maintain additional information. They’re relatively stable and have a life span of anywhere from three to 10 years. Many of these systems will be deployed on premises, but some may be delivered as a cloud application.
- Systems of transformation — These systems create innovation for your organization. They’re often developed out of ad hoc processes and tied to specific initiatives, so they can have very short life cycles. They’re driven, developed and funded out of business budgets. They’re also highly collaborative and involve both structured and unstructured data. The dynamic nature of these applications is well suited for cloud-based deployments.
Applications in the differentiation and transformation tiers will often be funded, created, implemented and managed outside the IT organization (whose role might be to create a platform for that class of application). These application categories should be treated differently because they have different life spans, regulatory implications and change requirements. Unfortunately, many companies have lumped all of them together into one monolithic architecture, which is costly to maintain and hard to change.
The Seeds Have Been Planted
When companies introduce portfolio management discipline, they often start categorizing IT spending across three similar dimensions: run the business, grow the business and transform the business. This categorization gives companies the ability to measure and adjust their IT spending to reflect business priorities. They can also use these metrics as a lever to reduce IT spending on “keeping the lights on” and increase spending for initiatives that will drive revenue growth or margin improvement.
However, it’s not enough to simply track your spending after the fact. Reorienting your application portfolio on these three categories will force a number of changes:
- Business cases are different because the goals and criteria are different.
- Ownership and funding models differ at each level.
- Vendor selection criteria varies significantly.
- Integration, data and security strategy must reflect different goals.
- Overall governance strategy changes to support a more distributed model.
- Application life cycle management differs by category.
More to Come
I believe we’ve hit on an exciting new thread of research that will help customers adjust their application portfolios to better reflect how the business operates and give organizations the power to make IT a truly integrated and differentiated capability. We’re planning a series of research that will help our clients not only understand what these changes mean, but how to make the changes necessary.
Has your organization already made this transformation, or are you in the middle of reassessing your application portfolio? I would love to hear your story at firstname.lastname@example.org.
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.