TL;DR: Marginal IT productivity drops sharply as teams scale, with mixed operating-system fleets able to push the Productivity Factor below zero, JumpCloud’s analysis of usage data from more than 5,000 organisations finds. Identity and device governance gets harder to run consistently as fragmentation rises, so each extra admin adds less value.
Editorial analysis by NHI Mgmt Group, based on content published by JumpCloud: “New Data: Fractured Tech Stack Slows Down IT”.
By the numbers:
- JumpCloud analyzed global product usage data from over 5,000 organisations.
- Each new IT admin brings an efficiency gain of up to 16.59% in early growth stages.
- At Commercial scale, that productivity gain falls to an average of just 7.27%.
Key questions
Q: Why do mixed fleets and dual identity providers reduce productivity as teams scale?
A: Because each additional platform introduces its own policy model, lifecycle path, and troubleshooting burden.
Q: What are the signs that identity and device governance is becoming fragmented?
A: Look for duplicated policies, repeated exception handling, inconsistent offboarding paths, and growing manual reconciliation between directories and endpoint tools.
Q: What breaks when IT environments rely on mixed device fleets and duplicated identity systems?
A: Control coverage becomes inconsistent across operating systems and directories, so teams spend more time reconciling exceptions than improving governance.
Practitioner guidance
- Standardise on fewer control planes Reduce the number of independent identity and device administration paths so that policy, lifecycle, and access decisions are enforced in one place as much as possible.
- Inventory duplicated identity rules Document every access, enrollment, and lifecycle rule that must be maintained in both Microsoft Entra and Google Workspace, then remove rules that cannot be governed consistently.
- Treat OS diversity as a governance metric Track Windows, macOS, and Linux coverage separately for enrollment, configuration, and remediation because mixed fleet support changes the real cost of control.
Bottom line: Tool sprawl and mixed fleets do not just slow operations, they change the economics of identity governance by making every additional admin less productive.
Glossary terms: Tool Sprawl, Mixed Device Fleet, Dual Identity-Provider Environment, Identity Blast Radius
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
Tool sprawl creates an identity governance ceiling, not just an operations burden. When every extra platform adds another policy surface, teams stop scaling control and start scaling exception handling. The result is a governance model that looks larger but becomes less consistent, especially when device, directory, and access decisions are split across multiple systems. Practitioners should treat sprawl as a structural identity risk, not a tooling preference.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to The 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption.
A question worth separating out:
Q: How should security teams respond when identity sprawl starts driving negative productivity?
A: They should stop treating sprawl as a staffing problem and start treating it as an architecture problem. First, identify which directories, device tools, and policy engines duplicate each other. Then collapse the highest-value overlaps, because negative productivity means the environment is consuming governance capacity faster than the team can replenish it.
👉 Read our full editorial: Tool sprawl and mixed fleets are flattening IT productivity
Tool sprawl creates an identity governance ceiling, not just an operations burden. When every extra platform adds another policy surface, teams stop scaling control and start scaling exception handling. The result is a governance model that looks larger but becomes less consistent, especially when device, directory, and access decisions are split across multiple systems. Practitioners should treat sprawl as a structural identity risk, not a tooling preference.
A few things that frame the scale:
- 69% of security leaders agree identity management must fundamentally shift to address agentic AI systems, according to The 2026 Infrastructure Identity Survey.
- Only 13% of organisations feel extremely prepared for the reality of agentic AI despite the majority racing toward autonomous adoption.
A question worth separating out:
Q: How should security teams respond when identity sprawl starts driving negative productivity?
A: They should stop treating sprawl as a staffing problem and start treating it as an architecture problem. First, identify which directories, device tools, and policy engines duplicate each other. Then collapse the highest-value overlaps, because negative productivity means the environment is consuming governance capacity faster than the team can replenish it.
👉 Read our full editorial: Tool sprawl and mixed fleets are flattening IT productivity
Tool sprawl is now an identity governance problem, not just an operations problem. Once identity stores, endpoint fleets, and admin consoles multiply, the real issue becomes control duplication. Every duplicated workflow increases drift risk, review burden, and policy inconsistency, which means the governance model itself has to be simplified before scale can be improved.
A question worth separating out:
Q: What should teams do when tool sprawl starts to absorb admin capacity?
A: Rationalise overlapping tools, remove duplicated administration paths, and automate repetitive lifecycle tasks before adding more headcount. If the environment cannot be governed consistently, extra staff will mostly absorb complexity instead of reducing it.
👉 Read our full editorial: Tool sprawl and mixed fleets are flattening IT productivity