Skip to main content

Simplifying Service Management

One of the things that troubles me at times is how often people try to make the world more complex than it needs to be. The world is really a rather simple place if you take the time to step back and avoid complexity. I recently read a statement that made think upon this problem again.
The opposite of “simple” is “elaborate”, not “complex”— Dan Roam, The Back of the Napkin
What people call complex, may in reality be elaborate. They confuse the two ideas. This can lead to issues in the delivery of Business and IT Services to customers. If someone believes a service is too complex they can often be less willing to make the effort to provide the service, or support it or improve it. Most likely the service is just elaborate (having lots of underpinning elements and components), not really complex (being of a nature that is difficult to understand).

So how do we move away from complexity and towards seeing Service Management in terms of simplicity and elaboration? Here are several techniques that might help:

1. Visualize: Draw out concepts, topologies, hierarchies, structures, models etc. on paper or using a tool like Microsoft Visio. Seeing the idea put into a visual structure can help someone see the paths and interconnections that make up a system or service.

2. Quantify: Put numbers and facts to systems and services using measurement and metrics techniques like the 7-Step Improvement Process found in the ITIL© Continual Service Improvement publication. Having factual data and information tied to systems and services can help show volumes, durations and frequencies associated with systems

3. Qualify: Use Deming’s Plan-Do-Check-Act cycle. Map terminology and actions into the four steps of the cycle to see how the process or flow of actions or steps can be simplified to some basic ideas.

4. Analyze: Use deductive and inductive reasoning techniques to break apart (deduction) or recompose (induction) structures, processes, steps, models, etc. to see the interrelations and structures

5. Map: Use mind-mapping or brainstorming tools to again visualize the ideas and concepts, or parts and pieces of a system or service. These diagrams show how elaborate systems and services often point back to a single central idea.

Each of these techniques has its own uses and appropriate place and time. The key with any of the techniques is to maintain the approach that delivery of service is at its most basic a simple idea. By keeping in mind the goal of finding the simplicity rather than focusing on the complexity, these techniques can be very powerful.

Comments

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service than toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you. Roles and Responsibilities: Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance. Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables.  An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and th