Skip to main content

Pain Management

Image
By
Picture this: A patient walks into the doctor’s office and says “doc, every time I raise my arm it hurts”.  Of course you know the punch line.   But can you see the analogy?    Fill in the blank:  Every time we _____, our customers/services/users hurt (how?) 

To identify and improve pain areas, you must analyze the overall performance and capabilities of your services, processes, people, partners and underpinning technology.  Do you know how they support desired business outcomes and where they fall short?   
The first step is to identify the “as-is” state in order to document current performance and justify the need for improvement.   Part of this step will involve determining what needs to be measured and who is going to collect, process, analyze and synthesize the data into useable information.  Key stakeholders will need to be identified and engaged in order to understand the intensity of their pain, the residual impact and their input into possible opportunities for improvement.

The “as-is” state can serve as a launchpad for envisioning and documenting the desired “to be” state.  A gap analysis between the two will serve as the basis for building a strategic plan for improvement
Improvement requires resources (human, technical and financial).   To justify the improvement, a business case will need to be developed that describes both the pain and potential remedies.   Business cases must speak to value - as both return on investment and value on investment.  It must be aligned to customer goals and objectives.   And it must speak to risk - the risk of making the improvement and the risk of not making the improvement.     
Pain is unpleasant.  And unfortunately, many of us choose to live with the pain instead of identifying ways to lessen or eliminate it.    But pain can be managed - both medically and corporately.  You just have to be willing to acknowledge it and commit to reducing or eliminating it.
Labels:

Comments

Post a Comment

Popular posts from this blog

Four Service Characteristics

By
Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.”  Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...
Post a Comment
Read more

What Is A Service Offering?

By
The ITIL 4 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 1. 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 then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.      ...
Post a Comment
Read more

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

By
This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See  ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...
Post a Comment
Read more