Loading content
Shared services centralize reusable functions and platforms within an organization to increase efficiency, consistency, and scalability. They separate product/domain ownership from cross-cutting services and define governance, interfaces, and operating models. Suitable for reducing duplication and standardizing technical and administrative processes.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Shared services are centrally provided technical or organizational capabilities used jointly by multiple applications or teams.
The model grew from the effort to provide recurring capabilities such as networking, identity, logging, or security controls once and reuse them through standardized interfaces.
A shared service has an accountable operator, defined scope, and an interface or service level. Consumers save local effort but share availability, capacity, cost, and change risks. This differs from shared-nothing: shared services deliberately use a common capability, while shared-nothing isolates resources.
A team or platform owns operation, interface, and quality of the shared service.
Multiple applications or teams use the same capability through agreed access paths.
Reuse lowers effort but creates shared capacity, availability, and change risks.
Shared services help assess platform and organizational architectures. Explicit ownership, consumption limits, cost allocation, and failure behavior prevent a central service from becoming a hidden bottleneck.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.