Skip to main content

Posts

What is a Service?

This is perhaps one of the most important yet challenging questions in all of IT Service Management. In fact it makes ITSM possible (given the realization that it is IT Service Management). I pondered this question while having lunch and catching up on some industry reading about value and customers. The ITIL© V3 definition of a service is as follows: A service is a means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. So given this definition, how do we know what exactly is a service? As a result of my pondering (and some sauce spilled on my blazer from my lunch) I came to a conclusion. Simply, a service is anything you do to help other people accomplish a goal. In other words it is “work done for other people”. If a person could accomplish the work themselves, would they need service provided to them? Maybe, but often, they can’t do it as well, as cheaply, etc. As an example, let’s go back to the s

Evaluating and Selecting ITSM Tools

I am often asked, what is the best ITSM tool? Which tools are ITIL compliant? The answer is, of course, “it depends!” Every organization has different needs, budgets and resources. For now, there is no officially recognized “ITIL Compliant” designation. The OGC and APM Group have recently introduced a Software Assessment Scheme that will audit ITSM toolsets against specifically defined ITIL criteria. Going forward, you will be able to easily identify the tool suites that have met those requirements. The starting point is a list of generic requirements. An integrated suite is preferable and should include as much of the following as possible: Service Portfoilio Service Catalog Service Design Tools Discovery/Deployment/Licensing Technology Workflow or process engines CMDB’S Configuration Management Systems (CMS) Self Help for Users Remote Control Diagnostic Utilities Reporting Tools/Dashboards Service Knowledge Management System (SKMS) Depending on your requirements, goals, budget, ITSM

Who was Bloom and why should I care?

Benjamin Bloom (1913 – 1999) was an American educational psychologist who developed a taxonomy, or structure, through which educational objectives could be organized according to their cognitive complexity. The cognitive domain deals with a person's ability to process information and use it in a meaningful way. Bloom identified six levels within the cognitive domain, from the simple recall of facts, through increasingly more complex and abstract levels of thinking. Simply put, Bloom’s Taxonomy helps teachers categorize learning objectives and, from there, assess learning achievements. Why should you care? Many popular certification exams – such as the ITIL V3 exams – are based on Bloom’s Taxonomy. Understanding the Bloom level at which you will be tested and using appropriate study techniques greatly increases your ability to Engage effectively in class Prepare properly for the exam Achieve success on the exam It is also useful to understand your learning style, or approach to lear

Change Management People

“Those Change Management people make my life so difficult sometimes!” I heard this from one of my students the other day. In this person’s organization they have made a common error. They have confused the process of Change Management with the Service Desk, Technical, Operations and Application Management functions. In other words the people who use the Change Management (and other processes) have become the same as the process itself. This is an often misconstrued and misinterpreted idea. We must remember that ITIL makes a distinction between Functions (groups of people who use processes to complete similar types of work) and Processes (sets of activities used to complete various types of work). I like to remind my learners that Functions use Processes (or people do activities). Functions are not Processes and Processes are not Functions. There may be groups of people or work teams who use a process as their main tool. As an example, the Release Implementation Team could use Re

Celebrating National Customer Service Week (Part 2)

It’s National Customer Service Week (NCSW). Held every year during the first week in October, NCSW provides an excellent opportunity to explore ways to better serve your customers. A great starting point is ensuring your policies, processes and procedures are customer friendly. What does that mean? Be a customer for a moment. What are the things that drive you crazy? Here is my list of pet peeves, along with a few suggestions. Limited options – Every process begins with a trigger. For IT organizations, a common trigger is a call to the Service Desk to report an incident or submit a service request. Times have changed. Increasingly customers want the ability to use other channels such as email, self-help via the internet, chat, and in many cases, all of the above. There are currently four generations in the work place, all who have very different expectations and desires in terms of how they obtain support. Are your processes keeping up with the times? Surveys, focus groups and needs a

Celebrating National Customer Service Week (Part 1)

Times are tough and many organizations are looking for ways to reduce costs. However, even in difficult times, investing in the people, processes and technology used to serve customers is sure to reap a positive return. National Customer Service Week (NCSW), held October 5-9 in 2009, provides an excellent opportunity to explore ways to better serve your customers. It is also an excellent time to let the employees who serve your customers know how important they are to the success of your organization. Always the first week in October, NCSW is designed to raise awareness of customer service and the vital role it plays within an organization. It is also an opportunity to say thank you to those who work in customer service for a job well done. Organizations take part in NCSW by hosting events in their workplace. These events can be large or small, serious or fun, they can be held all through the week or just on one day…. it's up to each organization to decide how to celebrate.

MOF, ITIL and ISO/IEC 20000

Microsoft has recently published two interesting whitepapers mapping its Microsoft Operations Framework (MOF) to ITIL V3 and ISO/IEC 20000: Cross Reference ITIL® V3 and MOF 4.0 Using MOF for ISO/IEC 20000 I have always been a big fan of MOF - it makes sense, is filled with question-based guidance and it's free. Microsoft has graciously provided free job aids, templates and whitepapers such as the ones referenced above. I like to think of MOF as "service management for the masses." As the whitepapers describe, MOF can be used to complement ITIL implementations and/or fulfill the minimum critical activities required for ISO/IEC 20000 certification. Frankly, MOF's biggest obstacle is the big "M" that sits in front of the framework. There is a common misconception that MOF only applies to environments that are heavily invested in Microsoft technologies. The truth is that the best practices in MOF apply to any environment. The guidance is very generic and is not