Two Disciplines That Rarely Talk
Enterprise architecture and IT service management tend to operate as separate disciplines in most organisations. Architecture is concerned with the design of the technical landscape — the systems, the integrations, the standards. ITSM is concerned with how services are delivered and supported within that landscape. The two teams often occupy different reporting lines, use different frameworks and attend different conferences.
This separation is understandable historically. But it creates real problems in practice — and as IT environments become more complex, those problems are becoming more significant.
Where the Disconnection Causes Problems
The most visible point of disconnection is the service catalogue. A service catalogue that accurately reflects what IT delivers to the business needs to map to the underlying architectural components that support those services. Without that mapping, impact analysis is unreliable, change risk assessment is incomplete and the CMDB cannot be kept accurate.
Architecture decisions — new systems, decommissioned platforms, integration changes — directly affect the service landscape. When those decisions are made without ITSM input, services are disrupted, transition plans are inadequate and the operational teams dealing with the consequences are caught unprepared.
The Opportunity in Closer Alignment
Organisations that have built genuine alignment between architecture and ITSM — through shared governance, common data models and joint participation in design authority — consistently report better change outcomes, faster incident resolution and more accurate impact analysis than those that have not.
"Architecture decides what gets built. ITSM determines how it gets operated. Those conversations need to happen together, not sequentially."
The practical starting point is usually the CMDB — ensuring that architectural decisions are reflected in configuration management, and that the CMDB provides the foundation for both operational support and architectural analysis. From that shared data foundation, closer working practices tend to follow naturally.
Is your ITSM as good as it should be?
Our independent benchmarking assessment gives IT leaders a clear, evidence-based picture of where their service management stands — and exactly what to do about it.
Book a Free Strategy Session →