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 the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…