Why do so many IT transformations fail to deliver expected results or derail with extended spending and timeline ?
- Lack of appropriate program governance and safeguards.
- Lack of knowledge and advice in business transformation
- Insufficient planning for operating model and process redesign
- Deficient change management
- Uncontrolled master data
- Lack of independent oversight
…. are all often cited causes
Few will mention the lack of a clear identified technology strategy aligned with business capabilities and objectives driving and structuring an enterprise architecture target state.
What is this and why does that matter ? A technological transformation almost always requires:
- Changes in business processes
- Redesign of the operating model
- In addition, for complex ecosystems, rarely does a single solution cover all the required capabilities.
- A hybrid architecture that requires multiple solutions and interoperability with an intermediate state often needs to be planned.
Jumping headfirst into technology integration without strategic and architecture planning can result in:
- Changes to the scope
- MVP failures (minimum viable product)
- Deadlines exceeded
- Underestimates in Budget
- Business continuity challenges
- Minimal benefits other than mitigation of obsolescence risks
A capability-driven tech strategy & architecture is one of the missing links to a successful transformation
Some Foundations explained:
Business Capabilities:
- Different business functions (existing or future)
- Represented by grouping of functions or by end-to-end value streams.
- Used for:
- Evaluation of business performance and project aspirations
- Assessing how technology does or does not support each function
Conceptual Enterprise Architecture:
- Connects the IT field to the business world
- Relates technologies to business capabilities and defines their interaction a high level
- Used to describe:
- The current state
- Target state aspirations
- Types of technologies used and needed
- Facilitates highlighting of key gaps that may require third-party solutions or the need to schedule an interim state status.
- You don’t need to have technologies fully selected to establish an enterprise architecture
Proven methodology to put any transformation on a solid foundation
Business Vision and Objectives
- Sessions with Executives
- Definition of business objectives, gaps and areas of development
- Define the context and vision:
The what? and The Why?
Current state Analysis
- Artifact Reviews and Workshops
- Process and technology landscape analyses
- Recognized practices
- Describes in more details:
What to change?
Target State definition
- Technology scenario development
- Prerequisites for process change, master data readiness
- Operating model dependencies
- Alignment with conceptual enterprise architecture
- Describes:
How to change?
Action Plan & Business Case
- Actions to be taken
- Dependencies and risks to be mitigated
- Business case – costs and value generation (optional)
- Describes in more details:
How to change? & Why change?
This approach can typically be completed in 6-8 weeks depending on scope, complexity, and availability
Let me guide you in your first big decisions defining the itinerary of your transformation
We will adjust the approach, timeline and team to your company’s unique circumstances and work together for its success