What is ITIL?
ITIL is a widely used framework of proven practices for IT service management. It describes how IT services are planned, delivered and continually improved so that they create measurable value for the business. The current version is called ITIL 4.

ITIL: definition and origin
ITIL stands for “IT Infrastructure Library.” The collection of proven practices originated in the 1980s at a British government agency and over the years became the world’s most widely used framework for IT service management. ITIL is neither a law nor a standard but a point of orientation: it supplies terms, practices and principles that any company can tailor to its size.
The current version, ITIL 4, no longer centers on rigid processes but on value creation: a service value system links guiding principles, governance, a value chain, 34 practices and continual improvement. Individuals can be certified in ITIL; organizations can be audited against the related ISO/IEC 20000 standard.
The most important practices in daily operations
For mid-sized companies, only a few practices are truly decisive. They form the backbone of every service desk and can be applied without certification. A clean separation matters: a fault is fixed quickly, while its cause is eliminated permanently through problem management.
- Incident management: fix faults quickly so operations keep running
- Problem management: find and eliminate the causes of recurring faults
- Service request management: handle standard requests such as access or new devices
- Change enablement: introduce changes to IT systems in a controlled way, weighing the risk
- Service level management: agree and measure services and response times in binding terms
- Knowledge management: document knowledge and make it findable for everyone
Real-world example: the recurring printer failure
In a tax consultancy, the network printer keeps failing after updates. Each time someone opens a ticket, a technician restarts the service, and an hour later everything is back to normal. In ITIL terms, that is incident management: operations continue, but the cause remains.
Only when the fault is logged as a problem does the service provider examine the driver and switch it to a stable version. The change is documented through change enablement and tested beforehand. The result is fewer tickets, fewer interruptions and a solution that remains traceable even after staff changes.
Benefits, limits and common mistakes
ITIL creates a common language between IT, business departments and service providers, makes services measurable and reduces dependence on individuals. The biggest danger is over-organization: a company with 40 workstations that implements every practice in full creates more administration than benefit.
The proven principle is to start where the pain is greatest—usually with clean ticket handling, clear priorities and a knowledge base. Another mistake is to treat ITIL as a purely IT matter: without involving the business departments, service levels remain theoretical.
Applying ITIL in a mid-sized company
An ITIL certification is not required for this. It is enough to adopt the basic ideas: a central entry point through the service desk, separate handling of faults, requests and changes, defined response times and regular reporting. Nano Concepts sets up these workflows in IT support and advises on how much structure suits the size of your business.
Frequently asked questions about ITIL (IT service management framework)
Neither. ITIL is a framework of recommendations that nobody is legally bound to follow. Individuals can be certified. For organizations there is the ISO/IEC 20000 standard, which makes an IT service management system auditable and is closely based on ITIL.
An incident is a single fault that should be fixed quickly so operations can continue. A problem is the underlying cause, often behind several incidents. Problem management looks for that cause and eliminates it permanently.
As a model, yes; as a complete rulebook, usually not. Small companies benefit from individual building blocks such as ticket handling, priorities, change planning and a knowledge base. ITIL 4 explicitly recommends keeping things simple and practical and adopting only what brings benefit.
DevOps and ITIL complement each other. ITIL describes how IT services are run and governed reliably; DevOps describes how software is developed and delivered quickly and in an automated way. ITIL 4 explicitly takes up ideas from agile and DevOps.
Matching services

Technology Consulting
Software selection, architecture, code review and a digitalization roadmap – independent and implementation-oriented.
Learn more
IT Support
Helpdesk, level 1 to level 3 support and workplace services – remote and on site from a single source.
Learn more
Maintenance & Support
Updates, monitoring, backups and further development – so websites, apps and software run reliably.
Learn more
Digital Transformation Consulting
Analyze processes, set priorities, create a roadmap – digital transformation consulting for SMEs with implementation in mind.
Learn moreRelated terms
Relevant for these industries
Related magazine articles

Prioritizing Technical Debt: Pay the Interest or Pay It Down?
Technical debt is not a synonym for bad code – it becomes dangerous when it stays invisible. Here is how to assess legacy burdens by impact and effort and reduce them in a plannable way.
Read more
Cloud Scaling for Platforms: Find Bottlenecks, Control Costs
More servers rarely solve the real problem. How to scale web platforms deliberately: measure bottlenecks, fix the database and cache first, and keep costs and resilience under control from the start.
Read more
Software Requirements Specification (Lastenheft): Structure, Example and Checklist
A good requirements specification makes quotes comparable and fixed prices possible. How it is structured, how to word requirements so they can be tested and how to tell that yours is complete.
Read more