Einar & Partners | IT Benchmarks

Which teams are usually involved in a Service Mapping project?

Application or Service Owners

(75%)

Infrastructure / Platform teams (linux, windows, virtualization etc)

(66%)

Application Teams (Databases, Application Layer, Configurations)

(55%)

IT Architects

(51%)

Network Teams & Engineers

(42%)

Cloud Teams (AWS, Azure etc)

(42%)

Security Team

(34%)

Key Takeaways

Application or Service Owners were the most frequently involved stakeholders, highlighting the importance of business and service-level knowledge during service mapping implementations.
Infrastructure and platform teams also played a major role, reflecting the technical complexity of mapping environments across servers, operating systems, and virtualization layers.
Application teams and IT architects were commonly engaged to support dependency mapping, configuration validation, and architectural alignment.
Security, cloud, and network teams showed moderate involvement, indicating that service mapping projects increasingly require cross-functional collaboration across modern enterprise environments.

Take the survey to compare your results with benchmark data.