An exhaustive map has never been enough to make a decision. What is most often missing is the link between the target and the trade-off.
Many organisations have a map of their information system. Few use it to decide. The document exists, it is accurate, it is even up to date. But it does not say what to do.
A target is a decision hypothesis
A useful target architecture states choices: which capabilities to share, which applications to converge, which dependencies to remove, and in what order. It is deliberately incomplete where nothing needs to change, and precise where the organisation must make trade-offs.
Link the target to investment
- Every project tied to a target capability: you know whether it moves you closer to the target or further away.
- Enforceable architecture principles: few, written down, and used in committee to settle questions.
- A stepped roadmap: stable intermediate states, each delivering value, rather than a big-bang.
Enterprise architecture then becomes what it should be: a governance tool that makes decisions faster, more consistent and easier to explain.
Information published on this website is provided for information purposes and may change at any time. Publications on this site express general analysis and do not constitute advice tailored to a specific situation.