2. 2
Products Disposition Target State Priority Value Case
TIME
Originate Accounts and Services (3.0) Decision Products (3.3) App 1 10,000$ 600,000$ Tolerate High $....
Originate Accounts and Services (3.0) Decision Products (3.3) App 2 3,000,000$ 1,200,000$ Tolerate Replace Low $....
Originate Accounts and Services (3.0) Decision Products (3.3) App 3 400,000$ 200,000$ Tolerate Replace High $....
6 R'sL0 Q1 2020Name
Commercial Loans
Technology Components
TCO% by Component (2017) TCO% by Component
Capabilities
L1
APP MODERNIZATION PRODUCT TAXONOMY
By making the nomenclature around products, capabilities, and apps more pervasive, we can get into a
mental model to facilitate intelligent decision-making…
1. For a Given
Product
2. We Need the
Capability to…
3. We Enable this
capability with these
Technology Components
[e.g. Applications]
4. If we [Disposition] & Get
to Target State
5. Priority
For Commercial
Loans
We need the
capability to
Decision Products
We currently use multiple
applications (e.g. our
Mainframe Customer Data,
Moody’s Analyst) to Decision
Products
If we Replace Our Mainframe with
nCino and supporting
enhancements and Replace
Moody’s Analyst with their latest
product Moody’s Credit Lens
High, Med, Low
We can target an OpEx reduction of $XXX while offering top line growth, a higher quality experience and
more resiliency
1 2 3 4
5
Model
Flow
Example
Use Case
Example
Business
Case
3. Classification: Internal Use
FROM INSIGHTS TO ACTIONS
considering multiple influences
Priority
Value
Disposition
Disposition: Applications are
dispositioned at each level of
assessment into one of the 7 R’s
iteratively ensuring minimal investment
in analysis
Priority: Applications are prioritized
based on several key factors including
business goals, technology goals, and
regulatory/compliance needs
Value/Cost: Technology spend is
compared internally and against external
bench marks to understand target cost.
Additionally, value through growth is
estimated
4. Classification: Internal Use
EACH 6R TREATMENT ADDRESSES
different elements of the client’s requirements
Lower degree of
achievement
Higher degree of
achievement
* Dependent on level of re-factoring
* *
BUSINESS
AGILITY
NEW IT
SKILLS
ALIGN TO
TARGET ARCH.
REDUCE
TCO
LEVERAGE CLOUD
CAPABILITIES
COST / TIME TO
ACHIEVE
RETAIN
REPLACE
RE-HOST
RE-PLATFORM
RE-FACTOR
RE-IMAGINE
Lower Cost Higher Cost
For far too long we have had IT and “THE BUSINESS”
We need to shift our focus away from our business partners focused on new features and truly make them product owners
This includes helping them understand what it takes to run a system every day
By shifting the focus of both the business and IT to focus on how do I deliver capabilities, you are able to build simple business cases for application modernize
What we have done at Accenture is steal from the Agile concept of As A, I want, so that to create a way for both business partners and IT engineers to simply understand and building a common language around application modernization
In this example, you can see how we create a simple story line that allows both groups a seat at the table..
While this framework only shows an L0 and L1, you can continue to allow for fine gained L2 and below to support your organizations view of products/capabilities.
At Accenture we see the disposition, priority, and value/cost drives all interacting and informing each other.
Often depending on your place in an organization, you may be concerned with one or two of these items for a single application, but rarely do we find a team that is thinking holistically about applications.
If you want to increase top line growth you might elect do go with a more aggressive disposition of re-image or re-arch, but that takes longer and cost more. If you want to do a data center exit, that might push you towards re-host/re-platform with a high priority…. Net Net, you can not decide on a single piece of this pie in a bubble. You will need to look across all three areas.
In the past we have looked at the disposition as a function of technical goals: Align to tech arch, reduce TCO, or leverage Cloud capabilities.
But we need to expand our thinking to include two key goals. First, business agility. This allows us to make commitments to our business partners and work at the speed of our business.
Second, is what Accenture calls New IT skills. We believe that 70% of training/learning is on the job learning. The best way to transform your workforce is to have people do Cloud work.
Aligning your organizational goals with the cost/time that your organization is willing to invest makes all parts of the organization acknowledge the goals and objectives of any migration/modernization
Another key area we see our clients fail at completing application modernization, is ANALYSIS PARALYSIS.
Again leveraging Agile, we created a process that allows us to disposition applications, just in time.
Ensure that as we begin to migrate application we are always learning and creating feedback loops that allow us to get better every day