Content
- Overview
- Step I: Assess Current Situation
- Step II: Develop Plan
- Step III: Target IT Design Outline
Overview
The technology integration work stream will be responsible for analyzing the current situation and determining what is needed successfully to migrate Acquired Company over to Acquirer's systems.
Step I: Assess
Understand both companies approaches and processes
Step II: Develop Plan
Develop recommended approach
Benefits of Structured Approach
- Sense of structure and a common language help the two companies work together
- Ensures no major issues are missed
- Discipline to maintain intensity despite day-to-day issues
- Speeds decision-making by creating a direct route to the top
- Helps capture learnings from each deal to refine the process
Step I: Assess Current Situation
Planning and design work begins with joint discovery and fact finding as part of developing the high-level plan and recommendations.
Key Activities
- Collect (or acquire from Due Diligence team) current information for both organizations including technology:
- Objectives
- Organizational charts and staffing levels
- Systems and operating models
- Conduct work-mapping of current technology capabilities/processes. Develop:
- Understanding of high-level operations, processes, and technology
- High-level “need-state” operations, processes, and technology models and identify gaps
Step II: Develop Plan
This step involves developing the technology integration high-level plans for the work stream and determining the implications on resource requirements, employee training, and communications to stakeholders.
Key Activities
- Prioritize and determine which gaps should be addressed
- Determine additional functionality Acquirer’s systems will need
- Identify potential issues/risks/interdependencies
- Develop plans with timing, milestones, and costs to migrate Acquired Co over to Acquirer’s systems
- Determine post-integration organizational structure
- Impact on staffing (projected cost and savings)
- Identify key open issues, cut-across issues, risks, “quick hit” opportunities
Target IT Design Template
Function |
Pre-Merger Operating Model |
Post-Merger Target Operating Model |
Portfolio Management |
||
|
||
|
||
|
||
|
||
|
||
Client Management |
||
|
||
|
||
|
||
|
||
Business Management |
||
|
||
|
||
|
||
|
||
|