Skip to main content

Adding Value - GIVE EM THE PICKLE

Recently I was having a discussion with a colleague. The discussion centered on value, what it means and how we deliver it to customers and users of IT Services. One particular part of the discussion focused on how you can easily add value in small increments that combine to bring satisfaction to customers. My colleague mentioned an interesting idea from a restaurateur named Bob Farrell, the founder of a chain of Ice Cream Parlors. He sold the chain and became a motivational speaker based on what he learned from the restaurant industry and how to drive better value and customer satisfaction.

Bob had once received a letter from a customer indicating loss of satisfaction when the server was going to charge him for a single pickle slice to go with his burger. From this letter Bob Farrell derived the importance of the small things we should do for customers and users of our goods and services to ensure satisfaction. Providing value to customers does not have to arrive in large portions. Oftentimes it is the small, low-cost, seemingly insignificant things that customers appreciate and acknowledge the most. These small acts and demonstrations of value lead to big payoffs.
FARRELL'S ICE CREAM PARLOURS - GIVE EM THE PICKLE by Bob Farrell http://www.youtube.com/watch?v=JJjf6ifg7U0
So how can we learn some fundamentals for IT Service Management from the need to give a customer an extra pickle slice at no cost? Let’s look at a number of small ways we can add value to the provisioning and delivery of Services to customers and users.

  • Service Solutions: Determine the most used functionality of a service. Then build in discounts over time for continued use and loyalty to those common features. Supply every fifth requirement at a deep discount or free.
  • Service Management Tools: Go Open Source or look to use full inherent features in tools rather than purchasing or building tools to meet highly customized, specific needs. Avoid customization and adjust your thinking rather than the tool.
  • Architecture: Seek simplicity and flexibility. Avoid overcomplicated or difficult to support, cutting edge technologies until they have settled into the mainstream. Avoid “Keeping up with the Joneses”.
  • Measurements and Metrics: Avoid overwhelming customers with lots of measures, metrics and reports. Reduce the number of measures and focus on the relationship with the customer more than the numbers. Use smiley faces to indicate satisfaction. Use simple, to-the-point reports rather than fancy dashboards.
  • Process: Keep process to around 4-5 steps; keep procedures to 4-5 steps. Provide more comprehensive training on process rather than overly detailed work instructions.
The key to adding value is to understand your customer and users; also knowing yourself. What makes you happy? What brings you satisfaction? What are the small things you can do to bring a smile to your customers and users? Once we get a handle on the bigger picture of customer satisfaction, then providing that pickle slice can be seen as a small means to a greater end.

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