CEB Architecture High Impact Capability
CEB Architecture High Impact Capability
CEB Architecture High Impact Capability
OVERVIEW
An approach to align technology solutions to strategic business objectives through capability roadmapping.
EXECUTIVE TEACHING
Leverage the process used to create capability roadmaps to obtain a deeper shared understanding of strategic business goals
and shift the dialogue with business partners away from short-term, project-based discussions. By broadening the conversation
to include people, process, and technology, capabilities can achieve a more holistic understanding of the underlying need.
COMPONENT TEACHINGS
Linking Business Strategy to CapabilitiesShift the dialogue between the IT liaison and business owner away from projects and
toward long-term plans.
Establishing Capability TargetsPut capability target choices into financial terms to help business partners make better investment
trade-off decisions.
Setting Capability Realization HorizonsHelp business partners understand the business and technology implications of different
paths to the target state.
Driving Application RationalizationExplicitly link programs to business capabilities to ensure application retirement goals are
being met.
Managing DemandUse the capability roadmap to manage demand by reconciling new project requests against established goals.
COMPONENT TEACHINGS
COMPANY SNAPSHOT
Merck & Co., Inc.
Industry:
Pharmaceuticals
2009 Revenue:
US$27.4 Billion
Through medicines, vaccines, biologic therapies, and consumer and animal products, Merck
works with customers and operates in more than 140 countries to deliver innovative health
solutions. Merck also demonstrates a commitment to increasing access to health care through
far-reaching programs that donate and deliver products to the people who need them.
Challenge
In a complex environment with more than 5,000 applications, more than 10,000 interfaces, and 35 different
technical environments, Merck was challenged to reduce IT maintenance and operations costs to increase
funds available for strategic projects the business required.
Approach
Merck develops a master-planning process that EA provides to business units. The process uses capability
roadmaps to identify consolidation opportunities and align new technology investments to strategic
priorities.
Results
Merck reduces the total number of applications by 20% and increases the portion of the IT budget devoted
to strategic investments by 50%.
Current Business
Capability
Outputs
Capability Model
Capability Prioritization
Strategy
Identification
Future Business
Capability
Outputs
To-Be Capability Map
Capability Gap
Assessment
To-Be Process
Framework
Output
Strategy on a Page
Outputs
Solution Evolution Plan
Capability Roadmap
Current
Solutions
Capability
Roadmap
Future
Solution
Output
Current State
Architecture
Outputs
Solution/Capability Map
Target Architecture
1. L
INKING BUSINESS STRATEGY
TO CAPABILITIES
Illustrative
FINANCE
2012 Experience
I have one source I can go to for my annual-planning
needs, and I know the data is correct.
Strategy on a Page
Business
Drivers and
Goals
Outcomes
Business
Imperatives
Business
Capability
Capability
Below Industry
Standard (IS-)
Industry Standard
(IS)
Industry Leader
(IL)
Strategic and
Tactical Financial
Planning
Accounting
to Reporting
Distinctive Leader
(DL)
$5 M
$1.5 M
Treasury and
Capital Management
$3 M
$2.5 M
$4 M
Business partners
always want more than
budgets allow. Its our
job to help them assess where
they need to be industry leaders
and where its okay to meet the
industry standard by illustrating
the business costs and technical
costs.
Paula Kowalczyk
Senior Director, Business and Solutions
Architecture
Merck & Co., Inc.
Create implementation
scenarios that enable certain
capabilities before the target
state is reached.
3. S
ETTING CAPABILITY REALIZATION
HORIZONS
Implementation Scenarios
Illustrative
Year 1
Year 2
Year 3
Current State
Interim State
Interim State
Target State
Current state
evaluation
Scenario A
Year 0
100% of capabilities
realized
New applications
rolled out
Legacy applications
decommissioned
Feasibility Assessment
Cost
Legacy
Life Span
Complexity
Business
Urgency
Scenario B
Time to
Delivery
Current state
evaluation
Capability 1
urgency: low
Capability 2
urgency: moderate
Capability 2
realized
100% of capabilities
realized
Legacy applications
decommissioned
Cost
Legacy
Life Span
Complexity
Business
Urgency
Scenario C
Time to
Delivery
Current state
evaluation
Capability 1
urgency: high
Capability 2
urgency: moderate
Capability 3
urgency: low
Capability 1 realized
Capability 2
realized
100% of capabilities
realized
Legacy applications
decommissioned
Cost
Legacy
Life Span
Complexity
Business
Urgency
Time to
Delivery
Programs
Program 1
2008
2009
Geo 1
Program 2
Geo 2
2010
2011
Geo 3
Apr.
Geo 4
July
Oct.
Geo 5
Program 3
Program 4
Program 5
Business Capabilities
Capability 1
(5)
(3)
(2)
Capability 2
App. A (6)
(5)
ERP (3)
Capability 3
App. C (3)
Capability 4
(4)
(1)
(2)
(3)
(1)
(0)
ERP (1)
Capability 5
(1)
Capability 6
App. H (9)
ERP (5)
Capability 7
App. M (15)
ERP (4)
(3)
Capability 8
App. Z (44)
ERP (20)
(19)
(43)
Program Key
(2)
(5)
Symbol Key
Concept/Preparation
Rollout
Design
Construction
Milestone
Capability Key
Current Solution (Primary/Total Number Applications Used to Support Capability)
Planned Solution
Solution Being Considered
5. MANAGING DEMAND
Demand Management Decision Tree
No.
Business
Request:
New
Imperative
Yes.
Review trade-offs (what comes off/
gets delayed?) and adjust roadmap.
Yes.
Adjust timing?
Yes.
Forward?
No.
Already on
roadmap?
No.
No.
Add capability?
No.
Aligned
to strategy?
Yes.
Aligned to
capability?
Yes.
Include capability in roadmap,
identify solutions, and make trade-offs.
Yes.
Yes.
Existing
solution?
No.
Review trade-offs (what comes off/
gets delayed?) and adjust roadmap.
Source: Merck; CEB analysis.
Capability roadmaps
enable Merck to simplify
the portfolio and shift
funds from maintenance to
strategic investments.
RESULTS
Net Reduction in Applications
IT Budget Allocation
Indexed
100
100
= 5%
95
100%
= 15%
23%
81
50
35%
50%
77%
65%
0
2008
2009
2010
(Projected)
0%
2003
2010
(Projected)
KEY TAKEAWAYS
1. Use capability roadmaps to achieve a deeper shared understanding of longer-term strategic
business goals. Too often, conversations with the business focus on short-term, technology solutions. By
broadening the conversation to include people, process, and technology, capabilities can achieve a more
holistic understanding of the underlying need.
2. Give business partners flexibility when developing a capability roadmap by presenting them with
multiple paths to the target state. To facilitate better trade-off decisions, make sure they understand the
financial implications of capability improvement choices.
3. Involve business partners in the roadmap creation process to increase their ownership of and
accountability for specific roadmap outcomes. By tying roadmap milestones to application retirement
and demand management objectives, getting business buy-in to more ITcentric goals becomes easier.
10
Master-Planning
Methodology, pg. 12
Master PlanningDefinition,
pg. 13
Master Planning
Deliverables and
Responsibilities, pg. 14
Business and Solutions
Architect/Strategist Job
Description, pg. 15
Linking Business
Strategy to Capabilities
Establishing
Capability Targets
Managing Demand
Business Capability
Roadmap (Executive View),
pg. 23
Business Capability
Roadmap (High-Level
Planning View), pg. 24
11
Member Login
Contact CEB