Skip to main content

Pain Management

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.

Comments

Popular posts from this blog

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

The ITIL Maturity Model

Most organizations, especially service management organizations, strive to improve themselves. For those of us leveraging the ITIL® best practices, continual improvement is part of our DNA. We are constantly evaluating our organizations and looking for ways to improve. To aid in our improvement goals and underscore one of the major components of the ITIL Service Value System , Continual Improvement .   AXELOS has updated the ITIL Maturity Model and is offering new ITIL Assessment services. This will enable organizations to conduct evaluations and establish baselines to facilitate a continual improvement program. A while back I wrote an article on the importance of conducting an assessment . I explained the need to understand where you are before you can achieve your improvement goals. Understanding where you are deficient, how significant gaps are from your maturity objectives, and prioritizing which areas to focus on first are key to successfully improving. One method many organi

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