Skip to main content

Service Level Management Relationships

One of the most important goals of Service Level Management (SLM) is the need to build strong relationships between the customers and users of IT Services. It is incumbent on the roles of the Service Level Manager and Business Relationship Manager (a role defined with Demand Management) to serve as the Voice of the Customer. SLM must act as an agent on behalf of business customers, since those individuals or groups must focus on executing business processes or serving further the end-users of a company’s goods and services. The business should not have to spend its time worrying about the value they need from IT Services.

SLM needs to create a strong bond with the business and end-user customers. This bond needs to be a familiar and personal link that shows the customer that IT truly cares about the needs and success of the business. Good Service Level Management cannot be conducted solely through emails or phone calls. A good Service Level Manager knows they must meet their customers face-to-face and understand the customer to serve them in the best possible manner.

So how can a Service Level Manager (or Business Relationship Manager) build a strong personal and professional IT Service-based relationship with their customers? Here are some suggestions that I have found invaluable:

1. Visit your customers—Do not wait for your customers to come to you looking for help. Go to them proactively and offer your help. Find out what their needs and issues are before they even realize they have needs or issues.

2. Take your customers to lunch—Take some time to learn about your customer in a more relaxed and less intimidating atmosphere. Your company may have policies about actually buying the meal. That’s okay. But you can sit down and talk over coffee or tea about their needs.

3. Get to know your customer—Not just from a business and professional standpoint. Learn about their families and hobbies, likes and dislikes. They will begin to reveal their needs in subtle and informal ways.

4. Create a relationship of trust—Build a bond based on mutual respect, admiration and trust. Honor your customer with your words, deeds and behavior. Give them a reason to fully trust you.

5. Change the conversation—Move away from the never ending loop of “What do you want? What have you got?” to the more pragmatic “What do you do for your work? How can I help you do it better using technology?”

These are just starters. It is up to each Service Level Manager to build that individual link and bond with the customers they represent. That is the key—you must not simply serve your customers, you must represent their best interests before your own. This fosters trust and respect. They will then reward and compensate you equitably based on that feeling of trust. That is what a truly excellent IT Service provider and receiver relationship looks like.

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