Enterprise Architecture Management Road mapping
Summary
I use an application called LeanIX to document and map out items such as Capabilities, Process, Technologies and Components. This tool lets me plan out a 3-month run-ahead architecture runway that has architecturally significant changes.
Commercial organisations differ very much to Not-for Profits. I wanted to document a recent and difficult journey going through a re-platforming work. Here is my initial sample roadmap that I started documenting in LeanIX (the enterprise applications management tool).
Removing waste and maintaining architecture purity
Below is a sample task list structured in a table format, detailing the tasks needed to be completed. It can be quite lengthy and wasteful, especially when you need to make decisions fast.
Task No. | Task Description | Inputs | Outputs | Responsible |
---|---|---|---|---|
1 | Assess current IT infrastructure | Existing IT infrastructure data | Assessment report | IT Architect |
2 | Perform gap analysis | Assessment report | Gap analysis report | Enterprise Architect |
3 | Review compliance and standards | Current compliance documents | Compliance review report | Compliance Officer |
4 | Define strategic objectives | Business strategy, Gap analysis | Strategic objectives document | Strategy Manager |
5 | Develop transition architectures | Strategic objectives | Transition architecture models | IT Architect |
6 | Implement ITIL service improvements | Current ITIL processes | Improved ITIL processes | Service Manager |
7 | Engage stakeholders | Transition plans | Engagement and feedback report | Change Manager |
8 | Train staff on new processes and tools | Updated processes and tools | Training materials and records | HR Manager |
9 | Outline future state architecture | Transition architecture models | Future state architecture model | IT Architect |
10 | Integrate advanced ITIL processes | Improved ITIL processes | Fully integrated ITIL framework | Service Manager |
11 | Align architecture with TOGAF standards | TOGAF standards, Current model | TOGAF-aligned architecture model | Enterprise Architect |
12 | Establish continuous improvement mechanisms | Feedback, performance metrics | Continuous improvement plan | Quality Manager |
13 | Develop technology adoption plan | Emerging technology trends | Technology roadmap | CTO |
14 | Schedule periodic architecture reviews | Architecture models, KPIs | Review and update reports | Review Board |
Baseline Operating Model (Current State)
- Assessment of Current Architecture:
- Document the current IT infrastructure, software, and services.
- Identify stakeholders, current IT capabilities, and service management processes.
- Evaluate current adherence to ITIL service management and TOGAF architecture principles.
- Gap Analysis:
- Identify gaps in current architecture and service management against industry best practices.
- Outline risks, inefficiencies, and areas lacking scalability or performance.
- Compliance and Standards Review:
- Review current compliance with relevant standards and regulations.
- Determine the alignment with TOGAF and ITIL frameworks in the existing setup.
Transition Operating Model (Intermediate State)
- Strategic Planning:
- Define the roadmap to transition from the baseline to the target operating model.
- Set clear, measurable milestones and intermediate goals.
- Architecture Development:
- Develop a series of transitional architectures that reflect incremental improvements.
- Utilize TOGAF’s Architecture Development Method (ADM) for structured development.
- Service Improvement:
- Implement ITIL processes for better IT service management.
- Focus on improving service design, transition, and operation phases.
- Stakeholder Engagement and Change Management:
- Communicate changes and expectations to all stakeholders.
- Implement training and support to adapt to new processes and tools.
Target Operating Model (Future State)
- Future State Architecture:
- Outline the desired state of IT infrastructure, platforms, and services.
- Emphasize scalability, efficiency, and compliance.
- Advanced ITIL Integration:
- Fully integrate ITIL service management lifecycle into daily operations.
- Enhance capabilities in service strategy, design, transition, operation, and continual service improvement.
- TOGAF Alignment:
- Ensure that the architecture fully conforms to TOGAF standards, particularly focusing on strategic alignment, value realization, resource management, and risk management.
- Innovation and Continuous Improvement:
- Establish mechanisms for ongoing evaluation and adaptation of the architecture.
- Foster a culture of innovation and continuous improvement.
- Technology Roadmap:
- Develop a technology adoption plan that includes emerging technologies.
- Plan for regular updates and upgrades to maintain technological relevance and superiority.
The output of the roadmap planning looks something like this:

High-Level ASR (Significant Requirements) and Architecture Quality Attributes
Roadmap are pointless without having some principles, here are the top principles that I would consider, that align with the organisations Mission, Strategic Vision and Objectives for the current 2-5 year.
Tools and Metrics
- Architecture Tools: Use software tools that support TOGAF ADM and ITIL processes.
- Performance Metrics: Define KPIs aligned with business goals to measure IT performance and service management effectiveness.
- Regular Reviews: Schedule periodic reviews of the architecture and its alignment with the strategic objectives.
Total Cost of Ownership (TCO)
- Principle: Minimise the lifetime cost of IT assets while maximising value to the business.
- Application: Consider both direct costs (e.g., acquisition, deployment) and indirect costs (e.g., maintenance, training, and support). Factor in the costs of future upgrades, scalability, and potential exit costs.
2. Costing
- Principle: Achieve transparency and predictability in IT expenditures.
- Application: Implement a detailed costing model that includes initial capital expenditures, ongoing operational expenses, and incidentals. This model should be used to forecast budget needs and assess financial performance against investments.
3. Composite SLAs
- Principle: Ensure high reliability and performance standards across all IT services.
- Application: Develop composite SLAs that cover multiple services or components, ensuring that they align with business needs. These SLAs should detail performance metrics, downtime allowances, and remediation strategies.
4. Technical Debt
- Principle: Proactively manage and reduce technical debt to ensure long-term system health and agility.
- Application: Establish processes to regularly assess and address technical debt, such as outdated technologies, inefficient code, and legacy systems that could hinder future development or scalability.
5. Lead and Cycle Times
- Principle: Optimise processes to reduce time from development to deployment.
- Application: Focus on streamlining operations to shorten lead and cycle times. Implement agile methodologies to accelerate project cycles and improve responsiveness to change.