Topic starter
09/07/2026 3:29 pm
TL;DR: Public-sector IT is constrained by budget pressure, procurement cycles averaging 18 months, legacy systems, and a 360,000-person skills gap in Germany, according to Efecte and cited studies. The real issue is not tool availability but governance that cannot move faster than the administrative processes it is meant to improve.
Editorial analysis by NHI Mgmt Group, based on content published by Efecte: “IT im öffentlichen Sektor: Herausforderungen meistern mit Matrix42”.
By the numbers:
- Many public-sector projects in Europe take about 18 months to obtain approval, according to the International Public Procurement Conference 2023 cited by Efecte.
- 71% of public institutions in Germany say lengthy tender processes slow them down, according to Bitkom Research cited by Efecte.
- Only 32% of European authorities use digital end-to-end workflows, according to a 2023 McKinsey study cited by Efecte.
Key questions
Q: How should public-sector teams modernise IAM when procurement takes too long?
A: They should design for delayed implementation by separating control intent from deployment timing.
Q: Why do legacy systems make compliance harder in public administration?
A: Legacy systems fragment records and force manual handoffs, so policy cannot be executed consistently across identities, services and endpoints.
A: The clearest signs are repeated delays between approval and implementation, manual workarounds that persist after go-live, and controls that are documented but not consistently enforced.
Practitioner guidance
- Audit procurement-to-deployment latency Measure how long approved identity, service management, and compliance changes take to reach production, then break the delay into budget, tendering, integration and change-control stages.
- Prioritise automation where manual governance fails most often Focus on onboarding, license administration, ticket routing and reporting workflows that repeatedly stall because staff capacity is limited or approvals are too slow.
- Map legacy integration choke points Identify where isolated data structures force manual handoffs between systems, because those points are where access records, service requests and audit evidence usually diverge.
Bottom line: The article shows that public-sector IT stalls because budget pressure, procurement delay, legacy systems and staffing shortages all slow execution.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
09/07/2026 3:50 pm
Public-sector IT modernisation is constrained by governance throughput, not by technology availability. The article shows that budgets, procurement, and legacy systems form a control environment that cannot absorb change quickly enough. When service delivery, licensing, and workflow governance all depend on long approval chains, the organisation is effectively rate-limited by administration. Practitioners should treat throughput as a governance variable, not an operational afterthought.
A question worth separating out:
Q: Should public institutions prioritise automation or platform replacement first?
A: They should prioritise the area where manual effort most directly causes policy failure. If the immediate problem is repetitive governance work, automation can stabilise execution quickly. If the deeper problem is fragmented systems and broken handoffs, platform replacement may be necessary first so automation does not simply accelerate a flawed process.
👉 Read our full editorial: Public sector IT stalls on budget, procurement, and legacy systems