Enterprise architecture
Capability mapping, application landscape and a prioritised roadmap under TOGAF and MAE.
Nobody has the map.
An institution with twenty years of systems approved one at a time does not have a blueprint: it has sediment. Every new initiative starts with an excavation — what does this system do, who maintains it, what breaks if we switch it off — and that excavation is paid for in months of committee time.
The question that cannot be answered today is not a technical one. It is what we have, what it costs to keep running, and which part of the business it serves.
How it gets built.
Bottom-up, and in this order. Skipping the first step is what produces inventories nobody uses.
- 01Capabilities, not systems — We start from what the organisation does, not from what it has installed. An application map with no capabilities behind it is an inventory, and an inventory does not let you decide.
- 02The application map — What supports each capability, what is duplicated, which integration has been dead for years, and what stays switched on out of habit.
- 03Gaps and the cost of closing them — Where the business needs a capability with nothing underneath it, and what it takes to put it there. In numbers, not adjectives.
- 04A prioritised roadmap — Ordered by value and dependency, not by how long a request has been waiting. Under TOGAF and, in Colombian public institutions, aligned to MAE.
What you take away.
The map, the roadmap, and the judgement to keep deciding without us. An architecture only its author understands lasts exactly as long as the contract.