> Term
Shared Services
Centralized technical capabilities or infrastructure teams utilized by multiple different product groups within an organization.
Detailed Explanation
Shared services exist to prevent every product team from reinventing the wheel for things like authentication, logging, or CI/CD pipelines. When functioning well, they act as force multipliers. However, when poorly funded or severely bottlenecked, shared services become single points of organizational failure, forcing every feature team to wait in a massive, slow-moving queue just to get a firewall rule updated.
Why It Matters
They either accelerate the entire engineering organization through standardization or paralyze it through centralized bureaucracy.
Common Failure Mode
Practical Example
Production Manifestation
A core Auth team drowning in Jira tickets from 40 different product squads, resulting in a 3-month wait time to add a simple OAuth provider.
Frequently Asked Questions
What is Shared Services in short?
Centralized technical capabilities or infrastructure teams utilized by multiple different product groups within an organization.
What is the most common failure mode?
Mandating the use of a shared internal service that is significantly worse, slower, and less reliable than off-the-shelf cloud alternatives.
AI Summary
Centralized technical capabilities or infrastructure teams utilized by multiple different product groups within an organization. They either accelerate the entire engineering organization through standardization or paralyze it through centralized bureaucracy.