Professional Documents
Culture Documents
Application Rationalization
6 steps to remove redundant business
services and capabilities
In its original form, an IT portfolio is at its most efficient. Over To address this, CIOs need an application rationalization (App
time, well-intentioned adoption of new and better applications Rat) initiative. This book provides guidance on how to rationalize
leads to improvements in the way IT delivers critical business apps and services in your IT portfolio and arms CIOs and IT
capabilities. However, too often, these expansions are not finance leaders with practical ways to identify and eliminate
accompanied by an evaluation of other applications supporting duplication so they can use the cost savings to fund additional
the same business capabilities, yielding duplicate or overly- investment.
embellished apps delivering the same capability.
. Replace guesswork with facts.
No one means for this to happen, but eventually, the IT budget
groans under the weight of supporting this excess capability that
. Stop counting licenses and start defining business value.
hogs funding and starves the CIO’s innovation agenda. . Reject one-and-done initiatives that aren’t repeatable.
Despite company’s best efforts to control spending and secure the network, IT organizations are fighting
an uphill battle.
. Shadow IT and siloed purchasing habits lead to rogue and . Pain from past attempts to rationalize apps and cut costs could
redundant applications that exist outside the scrutiny and leave people hesitant to embrace further optimization programs.
control of the IT organization. . Complicated total cost of ownership (TCO) calculations can
. M&A activity introduces the applications and services of a make it tough to get buy-in and lead to uncertainty about the
newly acquired business, many of which may overlap or parallel cost implications of retiring an app or retaining it.
those already in place. . Zombie apps mean there could be applications running simply
. Sheer complexity and sprawl can also limit visibility, making because retirement plans were never fully executed or completed
it difficult to see where duplication is happening across a vast successfully.
application portfolio.
Is it dead or is it alive?
All too often, applications are cursed to live on in the ether of a company’s network. At one point, IT was dutifully focused on
retiring an app, but the process was never completed. Now said app is cursed to a lonely existence as a Zombie app that’s neglected
by users, should have been retired, but lives on in the IT portfolio. It’s only lot in life is to haunt the IT organization, and the budget,
with excessive infrastructure, application and vendor costs, while supporting the enterprise with little or no value. The only way to
eliminate the costs and inconvenience is to finish the retirement process. Running an App Rat initiative can help to hunt down the
Zombie apps and vanquish them for good.
Application rationalization initiatives are notorious for not being completed or for falling short of their potential to optimize costs. If you’re
aware of what stops teams from seeing success, you can ensure you avoid these pitfalls in your own approach.
1 2 3 4 5 6
Frame Catalog Cost Score Execute Sustain
By taking a phased approach, organizations can increase their chances of securing business partner buy-in and successfully executing.
Once an App Rat initiative is framed, it’s time to catalog the targeted applications based on the following questions:
How is an application used in our environment and how does usage compare across the business?
This question helps quantify metrics around the application’s usage, operation, and maintenance.
Source: TBM Taxonomy, part of the Apptio TBM Unified Model® (ATUM )
2000
services
The next step is describing each app based on these
six attributes: Size & complexity
Functionality & backlog
Business partners are most familiar with the nature of User experience & satisfaction
these apps, so getting their input is critical – but not at App
the risk of overthinking it. Business & criticality Security & compliance
Revenue & efficiency impact Value Risk Business continuity
The goal is to get directional input about an application’s Competitive differentiation Architecture & skills
organizational fit, so in most cases a simple survey should Fit
suffice. For example, ask stakeholders to rank each of the
Dev & support labor Consistency
dimensions with a high, medium, and low.
Infrastructure Cost Data Integrity
Vendor Geography
However, when it comes to assessing an application’s
total cost, most stakeholders won’t know how to respond. Vendor
Financial health
Therefore, this data point must be calculated in a more
Competition
granular fashion. Roadmap
Transaction Volumes
. Indicates relative value to the business
. Automation platforms may have low user activity but high business
transaction value
. Check with app owners to understand volumes and transaction
criticality
Up to this point, an application might seem like a critical element in the portfolio, but data around run, usage, and operational metrics could contain insights that tell a different story.
For example:
To allocate these expenses the general ledger might include an entry for wages, broken down
by employee. Aligning wages to the consuming application and business unit might first require
appropriating them to the internal labor cost pool, using a simple chart of accounts.
These costs could then be allocated from the internal labor pool up to the delivery tower using
active directory. By consulting a list of people on the delivery team, the appropriate percentage
of labor costs could be attributed directly to that team.
If the delivery team supports multiple applications (like SAP, Adobe, and Salesforce), then
determining which portion of the team should be attributed to Salesforce might require data such
as ticket count or the change request volume. User logins or activity level could also help identify
which business units are consuming Salesforce.
You can get started with the data you have – in its current The benefits of a standards-based cost allocation model
form – and evolve over time using a good, better, best
As the quality of data improves, organizations can generate App Rat initiatives with
approach:
more detailed assessment of application costs and trade-offs, but it’s not always clear
. Good: Use existing data to get a directionally correct how they should allocate those costs. Depending on the quality of their data, they
view of your app total cost of ownership (TCO) with could allocate costs based on:
costs routed based on assumptions. . Assumptions (e.g., the percentage of labor costs for a particular OS)
. Better: Get more accurate views of your app TCO . Attributes (e.g., how many makes and models of desktops and laptops are on the
taking into account infrastructure costs with costs network)
weighted by an attribute of an item. . Consumption (e.g., the actual number of business transactions or the usage level per
. Best: Use more nuanced data to do strategic month by users within an application)
portfolio alignment with costs allocated by measured
consumption.
The Apptio TBM Unified Model® (ATUM®) provides out-of-the-box guidance for
gathering the right data, pre-defined cost allocation methods, and a standardized
Get the poster at apptio.com/ATUM taxonomy of IT functions based on TBM (technology business management), a best
https://www.apptio.com/resources/posters/atum-poster/
practice discipline for managing the business of IT and communicating the cost, quality,
and value of IT investments to business partners.
Business Fit
Dev & support labor Consistency The value an app delivers balanced
Infrastructure Cost Data Integrity against the cost. The greater the
Vendor Geography
cost, the lower the score.
Vendor
Business Fit
Financial health
Competition
Roadmap
Business Fit
120
applications and targeted
170 more apps for
Application rationalization is one part of application portfolio management (APM). Done correctly, APM is a continuous
migration, resulting in
process for maintaining, governing and curating an application portfolio year-over-year. Because APM is ongoing,
millions of dollars in avoided
organizations should take a slightly different approach:
costs from unused app
. Don’t boil the ocean, but iteratively expand the scope. After each round of assessing and optimizing the portfolio,
licenses.
take a broader approach with the next round.
. Improve the detail of the assessment, especially TCO calculations. After the low-hanging fruit has been picked,
take a more thorough and nuanced approach to identifying waste.
. Get better at planning for the future. Take care in setting budgets, prioritizing and justifying apps, determining how
and when to onboard new apps, and establishing governance.
Finally, a successful APM program – and App Rat Initiative – requires continued investment; clear objectives that the
organization can drive toward; regular checkpoints to maintain a quarterly or semi-annual cadence; and automation
to generate consistent, fast, and scalable TCO calculations.
Don’t struggle to articulate the true cost and associated business value of your application and service portfolio
in manual spreadsheets. You need a purpose-built, automated IT cost analytics solution in order to continuously
optimize.
Apptio fuels digital business transformation. Technology leaders use Apptio’s machine learning to
analyze and plan their technology spend so they can invest in products that increase the speed of
business and deliver innovation. By translating raw costs, utilization, and billing data into business-
centric views, IT leaders shift spending from maintenance to growth.
Apptio.com © 2021 Apptio, Inc. All rights reserved. Trademarks and logos are the property of their respective owners. A1200 V2105-1 The Definitive Framework for Application Rationalization | 19