IT Service Management
How to Build a CMDB That Stays Accurate
A CMDB nobody trusts is worse than none. How to scope it around real use cases, automate population and keep data accurate over time.
Key takeaways
- ITIL 4 focuses on value co-creation, not just process compliance.
- Shift-left moves resolution closer to the user through self-service and knowledge.
- Measure experience (XLAs) alongside SLAs.
- AI assistants accelerate triage and knowledge reuse.
From processes to practices
ITIL 4 replaced rigid process descriptions with 34 management practices and a service value system. The emphasis is on outcomes, collaboration and continual improvement — useful principles for any service desk modernisation.
Shift-left
| Level | Who resolves | Example |
|---|---|---|
| Level 0 | User via self-service | Password reset, software request |
| Level 1 | Service desk | Known errors using knowledge articles |
| Level 2 | Specialist teams | Application or infrastructure faults |
| Level 3 | Engineering or vendor | Code defects, complex problems |
Each request that moves one level left reduces cost and improves user experience.
Building blocks
- Service catalogue with clear, user-friendly request items.
- Knowledge management using a knowledge-centred service approach — capture and improve knowledge during every interaction.
- Automation of fulfilment for common requests.
- Bilingual support in the languages your users speak.
- Integrated problem management to remove recurring incidents.
SLAs and XLAs
SLAs measure what IT does: response and resolution times. Experience-level agreements measure how users feel and how much productivity is lost. Combine both to avoid "watermelon" reporting — green on the outside, red inside.
Where AI helps
Virtual agents resolve routine requests, AI suggests categories and assignment groups, summarises long tickets and drafts knowledge articles from resolved incidents. Keep humans in control of changes to production.
Metrics
First-contact resolution, self-service adoption, mean time to resolve, reopened tickets, user satisfaction and recurring incident volume.
A 90-day plan
| Weeks | Focus |
|---|---|
| 1–3 | Baseline metrics, top request types, user feedback |
| 4–6 | Service catalogue redesign and top-20 knowledge articles |
| 7–9 | Self-service portal and automation of top requests |
| 10–12 | Virtual agent pilot, XLA measurement, continual improvement backlog |
How NAZZTEC helps
We provide ITIL 4 advisory, bilingual service desk operations and implementation of ITSM platforms including Freshservice and ServiceNow.
Next step: explore our IT Service Management services and ITSM Solutions.
Frequently asked questions
Do we need ITIL certification to adopt ITIL 4?
No. Training helps build a common language, but value comes from applying the practices pragmatically.
Which ITSM tool is best?
It depends on scale, complexity and budget. We implement platforms including Freshservice and ServiceNow and advise neutrally.
How quickly can a service desk be transformed?
Quick wins appear within weeks; a full transformation typically takes six to twelve months.
NAZZTEC Editorial TeamWritten and reviewed by NAZZTEC practitioners. This briefing is general guidance, not legal advice.
