How to improve your ITIL processes?

Measuring is knowing, but without real understanding no use.

I just read a good article which sums it all up: “Before you can improve a process, you have to understand the current process. You have to get out from behind the desk and walk the process …”

So we are not talking about only knowing but also about understanding. “… how a process currently works is often very different from how you think it is (or should be) working.”

I want to deliver you the following takeaways as important steps you should take before you start improving processes:

1. About processes, control and truths – The very first thing you have to do is accept that no one really knows what is going on and how people perform their work, neither workers nor managers. Regardless of what you think you know, the work really getting done, and how it gets done, is different.
2. Workflow: what is real and what imaginary? – The only way to actually discover what is really getting done is to get up from behind the desk, walk out of the office, and literally walk around, observe, and take notes. You cannot practice ITIL from behind a desk. This sounds simple, but as in many things, the doing is not so straightforward. To practice ITIL you have to walk the process, literally. Keep in mind that your goal is to collect and model the existing process as it works today; not what you imagine it ought to be, but rather the actual tasks and workflow in place.
3. Walk the walk – It takes time to learn the workflow with the right accuracy and detail.  You need to capture the “who, what, when and where” of the process, and should skip the “how and why” to start with.
4. Than model the workflow – Based on the new info you will probably be surprised about the actual work and time involved. Now you are ready to map your processes with ITIL standards and to my opinion other best practices and your own experiences.

Be aware of:

• It takes work, time and attention to detail
• Get up and leave your office!
• Accept that you don’t really know what is going on, but that you are heading for an exciting journey
• It’s sometimes difficult to observe unbiased
• During your analysis your goal is documentation, not improvement
• Improvement in: the time it takes to do things. You should capture how long it takes to perform the work before you can answer the question “should this be changed”. That’s an important measure (consider our start-up reports on actual duration)
• The value of an accurate process model cannot be underestimated. You cannot improve anything without understanding it first.

Read on

http://www.itsmsolutions.com/newsletters/DITYvol6iss32.htm?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+DoITYourself+%28Do+IT+Yourself+%28DITY%29+Feed%29

Martijn