Why ITIL to the usual average administrator (10-500 PCs)

Hey. At once I will say that the topic is applicable not only to administrators, but also to freelancers, outsourcers.
I recently passed the training “HF421S, ITIL Foundation for IT Service Managment”, under the impression I bring Prometheus fire to the masses.
I hope most people know what ITIL is, for the rest, an excerpt from the wiki :

ITIL (pronounced “ITIL”, English - Information Technology Infrastructure Library) is a library that describes the best practices used in practice for organizing the work of departments or companies engaged in the provision of information technology services.

There is an opinion that ITIL is serious, difficult and confusing, it is necessary only for very large companies, and the majority copes with everything “on the knee”, keeps it in memory, and this is normal and convenient.
By no means.
Following ITIL principles helps, first of all, a company administrator of any size to work calmly, steadily, and planned. It's simple.

ITIL libraries are like they did in other IT companies the best. The reverse is also true: IT can be done in the best possible way using ITIL recommendations.
It is noteworthy that IT is the same everywhere, so everyone uses ITIL in different ways, often without knowing about its existence.
In fact, if an administrator does not work with his feet, but with his head, he will come, step by step, to what is described in ITIL on the issues that concern him.
I did just that.
The difference between following the recommendations and independent inventions is in the cost of the experience gained (the number of erroneous experiments, time and money spent).
In addition, you don’t think about many processes and solutions, because there is no need (incidents, requirements) for their modeling.
From my experience, I have highlighted a few basic examples of popular administrative problems in small companies:

1. Working with incidents and user requests usually takes most of the work time, is least effective (time / tasks), kills any planning and brings chaos.
   
2. Changes (update, installation) in the IT infrastructure entail the fall of everything, and the victorious solution of new problems by the invaluable night administrator shifts.
   
3. Changing the administrator (often the only one) leads to new expenses and downtime in IT, as the new admin does not know anything, is looking for everything, reworking other uncomfortable crutches into his favorite crutches, and also does not write documentation.
   
4. Risks are discussed in a rather abstract way, “what if”, “maybe”, “well, I told you,” “well, now it works,” “we don't need super, just to work” —the main tags of such reasoning.
   
5. Backup and restore procedures are subject to discussion for a maximum of a month after a serious failure, as long as the boss does not see the bill for the purchase of a SOHO collider.
   
6. etc. administrators act with a soul, conscientiously, better than anyone, but for some reason they still cannot build quality work and service services and hate people more and more .
   

To my great surprise, on the third day of the training, when the holistic picture gathered, I suddenly suddenly realized how easy it was to organize servicing the customer infrastructure, earn more, grow more, save time, effort, nerves, do not swear over trifles with customers and employees etc.
A great surprise was caused because I did not learn anything fundamentally new, and instead of the expected mountain of bureaucratic problems I saw opportunities for excellent process optimization.

So. Still, why ITIL ordinary average administrator (10-500 PCs)?
The ITIL briefly and clearly describes the principles, the adherence to which will help ease your work and establish the desired IT work in the company.
Options for the above examples:

1. A simple, working Service Desk will help solve problems with incidents and the timing of their resolution. An analysis of incidents will provide insights into bottlenecks, which are usually quite small within small companies.
   
2. Using Change Management will allow you to get rid of many problems due to trivial mistakes due to stupidity, due to carelessness or ignorance.
   
3. Documenting infrastructure is not as bad as it seems at first glance. Keeping documents up-to-date within Change Management requires little effort and saves a lot of time.
   And maintaining an internal knowledge base on the simplest wiki engine will save time in solving problems, or even provide an excellent self-service opportunity for users.
   
4. Understanding of risks and their correct assessment help identify critical services, optimize infrastructure, find and eliminate errors, etc., ultimately get rid of a headache through a reasoned fundraising, or complete transfer of responsibility to top management.
   
5. Backups can be a simple automated procedure, because you already have everything planned, planned out, risks identified, accidental breakdowns minimized, and management has allocated money because it has already estimated the profitability of this operation and allocated the necessary funds.
   
6. etc. administrators work quietly at scheduled hours, services in perpetual uptime, the customer / employer is satisfied and agrees to pay increases, resources are released, new customers are attracted, finally you can start your own business, not a routine and find time to go to the store for a new Bentley .