Enterprise Architecture
Step beyond one solution and connect an organisation's capabilities, portfolio and technology direction.
This program is planned and not scheduled yet. No date, price or cohort has been announced. If you register interest, we contact you when it is scheduled or to discuss an individual format.
Objective
The program takes an architect from a single project to the organisation level: capability and value stream maps, application portfolio management, target and transition architectures, and governance without bureaucracy. TOGAF concepts are named as a reference; the program does not promise a certification.
Who it's for
- Solution architects whose decisions affect several teams and systems
- Technical leaders responsible for technology strategy and standards
- Senior specialists who want to view the technology portfolio at organisation level
- People who want to align IT plans with business strategy
Who it's not for
- Those without solution-level design experience; the solution architecture program fits better first
- Those looking for TOGAF or other framework certification preparation
- Those who want detailed code or product-specific training
Prerequisites
- Experience with solution architecture spanning several systems
- A habit of documenting with C4 and ADRs
- Grounding in integration and data architecture
- Ability to connect business processes with technical systems
What you will be able to do
What you will be able to do
- Prepare a capability map and a value stream model for an organisation
- Assess an application portfolio by value, risk and lifecycle criteria
- Distinguish current, target and transition architectures and derive a phased plan
- Write technology principles and standards and define an exception process
- Propose a lightweight governance model (architecture forum, decision rights)
- Draft a technology radar and an integration and data strategy
No education program can guarantee employment or a promotion.
Curriculum
Curriculum
- 01
Purpose and frameworks of enterprise architecture
What enterprise architecture is for, and what to take from frameworks such as TOGAF as a reference.
- Business, data, application and technology domains
- Frameworks as reference: TOGAF concepts (ADM, repository)
- Adapting a framework rather than applying it literally
- The architect's role and sphere of influence
- Typical failures: documentation for its own sake
Hands-on lab: A document of EA goals and success criteria for a given organisation description.
- 02
Capabilities and value streams
Model what the organisation does and how value flows, independent of IT.
- Business capability map
- Value streams and their stages
- Capability-to-application mapping
- Assessing capabilities by maturity and importance
- Heat maps to focus investment
Hands-on lab: A capability map and two value streams for a fictional distribution company.
- 03
Application portfolio management
Turn a list of existing systems into a portfolio that supports decisions.
- Application inventory and ownership
- Value, risk and technical health criteria
- Keep, change, merge, retire (TIME-style) decisions
- Detecting duplicated capabilities
- Keeping portfolio data current
Hands-on lab: An assessment table and recommended decisions for a fictional 20-application portfolio.
- 04
Target and transition architectures
Move from the current state to the target through achievable intermediate stages.
- Baseline, target and transition architectures
- Gap analysis
- Dependencies between transition stages
- Intermediate states that deliver value
- Planning risk and rollback
Hands-on lab: A three-stage transition roadmap from a legacy ERP to a modular landscape.
- 05
Principles, standards and governance without bureaucracy
Build rules that keep consistency without getting in the teams' way.
- Architecture principles: statement, rationale, implications
- Standards, recommendations and the exception process
- Architecture forum and decision rights
- Guardrail approach: pre-agreed paths
- Assessing governance impact (as quality signals, without promising numbers)
Hands-on lab: A governance model draft with five principles, two standards and an exception process.
- 06
Technology radar
Classify technology choices in a transparent, updatable way.
- Radar rings: adopt, trial, assess, hold
- Selection criteria and rationale
- Technology lifecycle and exit plans
- Updating the radar together with teams
- How the radar relates to ADRs
Hands-on lab: A draft 15-item technology radar for a fictional organisation, with rationales.
- 07
Integration and data strategy
Define how systems and data connect at organisation level.
- Integration platform and API strategy
- Data ownership, master data and catalogue
- Data quality and accountability
- Privacy and regulatory constraints
- Trade-offs between centralised and distributed data models
Hands-on lab: A one-page summary of an integration and data strategy for a fictional organisation, with first steps.
- 08
Aligning roadmaps with business strategy
Link technical plans to business goals and present them to leadership.
- From strategy to capability investments
- Prioritising the roadmap
- Presenting investment decisions
- Balancing short and long term
- Adapting to change and refreshing the plan
Hands-on lab: An 18-month architecture roadmap for a scenario with stated business goals, and a short leadership presentation.
Practice assignments
- A capability map for an organisation
- An application portfolio assessment
- A draft of principles and standards
- A target and transition architecture document
- A technology radar draft
Portfolio deliverables
- A capability map and value stream model for a case study
- A portfolio assessment with recommendations
- A target and transition architecture roadmap
- A draft of principles, standards and a governance model
How learning is assessed
- Defense of the target architecture and roadmap in front of a panel playing leadership (simulation)
- A written review of the portfolio assessment
- Feedback on the governance model (recommendations, not a certificate)
Tools and technologies
- Capability map
- ArchiMate (as a notation)
- C4 model
- ADR (Markdown)
- Technology radar
- Miro / FigJam
- Spreadsheet tools (for portfolio assessment)
- TOGAF concepts (as a reference)
Level progression
- Before
- Solution architecture experience: designing solutions that span several systems.
- After
- Building an architecture function in an organisation, or practice in a strategic technology role.
- Length and format
- Length and format are not set yet; the program is planned and not scheduled.
Frequently asked questions
Frequently asked questions
Is this program available now?
No. It is planned and not scheduled. No dates or prices are announced. You can request a consultation.
Is it TOGAF certification preparation?
No. TOGAF concepts are named as a reference, but the program does not promise a certification and is not exam preparation.
Will this create bureaucracy?
The opposite. The governance module focuses on lightweight rules, guardrails and an exception process that do not block teams.
Does it promise a role or outcome?
No. No program can guarantee a title, salary or outcome. It builds analysis and communication skills.
Articles related to this program
- ADRsWriting Architecture Decision Records that survive the team
- Enterprise architectureEnterprise architecture: capabilities, portfolios and governance without bureaucracy
- Solution architectureWhen and how to modernize a legacy monolith
- Solution architectureThe solution architect role: from requirements to a working solution