5.3IT asset management & ITSM (ITIL)
You can only manage well what you actually know you have. IT asset management is the discipline of keeping a current inventory of the estate: workstations, servers, printers, network gear, software and licences. An up-to-date inventory underpins nearly everything else — security (you cannot protect an unknown device), licensing (you cannot stay compliant without knowing what is installed), support (faster diagnosis when you know the machine), and planning (renewals, replacements, budgets). Tools exist to automate this, discovering devices and tracking licences, but even a simple, maintained list beats a perfect one that is out of date.
Above the inventory sits the idea of running IT as structured services. ITSM (IT Service Management) is the practice of managing IT as services delivered to the organization, and ITIL is the best-known framework of good practices for doing so — covering things like incident management, problem management and change management. The crucial caveat: ITIL is a set of practices to adapt, not rules to apply to the letter. A small organization takes the useful ideas — log incidents, distinguish incidents from underlying problems, control changes — without the heavy bureaucracy meant for large enterprises. The goal is pragmatic: deliver reliable IT service efficiently. Know what you have, treat IT as a service, and borrow from frameworks what genuinely helps at your scale.
Section vocabulary
- IT asset management
- Keeping a current inventory of hardware, software and licences across the estate.
- Inventory
- The maintained list of assets — the foundation for security, licensing, support and planning.
- ITSM
- IT Service Management: running IT as structured services delivered to the organization.
- ITIL
- A widely used framework of IT service best practices — to adapt, not apply to the letter.
- Change management
- A controlled way of making changes to reduce the risk of disruption.
Why is an IT inventory so important?
In practice — Start an inventory and adapt a practice
- Begin a simple inventory: list machines, key software and licences with owners.
- Note how that inventory would help with security, licensing and support.
- Pick one ITIL idea (e.g. distinguishing incidents from problems, or controlling changes).
- Describe a lightweight version of it that fits a small organization without heavy process.
Key takeaways
- You manage well only what you know you have — keep a current inventory.
- The inventory underpins security, licensing, support and planning.
- ITSM runs IT as structured services; ITIL is the best-known framework of practices.
- Adapt ITIL — take the useful ideas, skip the enterprise bureaucracy at small scale.
Frequently asked questions
Why does an inventory matter so much — can't I just deal with devices as they come up?
Because you cannot protect, license, support or plan around things you do not know exist. An unknown laptop is an unpatched, unmonitored way into your network; unknown installed software is a compliance and security gap; without a list you rediscover the estate reactively, every incident starting with « what is this machine? » A current inventory turns all of that proactive: you can push updates to everything, prove licence compliance, diagnose faster because you know the hardware and history, and budget for renewals and replacements before they become emergencies. It does not need to be sophisticated — a simple, genuinely maintained list is enormously valuable, and the classic failure is not the lack of a tool but letting the list go stale.
Is ITIL overkill for a small IT team?
The full framework, applied literally, absolutely can be — ITIL was shaped for large enterprises with many staff and formal processes. But its core ideas are valuable at any size if you take them pragmatically. Logging incidents, separating a one-off incident from the recurring problem behind it, and controlling changes so they do not cause outages are all useful to a team of one. The mistake is treating ITIL as a rulebook to implement wholesale; the right approach is to borrow the concepts that reduce your real pain and skip the ceremony you do not need. Adapt, don't adopt: a lightweight version of good service practice makes small IT more reliable without drowning it in process.