Skip to main content

ITSM … We’ve Gone Loopy! [ Part 1 of 2 ]

Feedback Loops Negative and Positive  
IT professionals agree that vital information is required in order for a service provider to adapt to the ever changing dynamic needs of the business.  Best practice tells us we should create a culture of ongoing continual service improvement (CSI).  In order to propose strategies for service improvement plans that will allow us to meet the ever changing demands of our customer we need to get a pulse on what is really happening in our internal and external environment.  Taking a SWAG at it is not good enough. Data, information and knowledge are not enough.  A service provider needs to provision the measurement systems that will enable success.  In comes “Feedback Loops”.
Negative Feedback loops are positive for ITSM
A Negative feedback loop brings you toward your target set point to optimize and sustain an internal stable environment.  An animal maintains homeostasis or a stable body temperature through negative feedback loops.  Humans use a negative feedback loop to maintain a body temperature of 98.6 degrees which is our internal target set point.  We see this when our body is over heated  and produces sweat to cool us down and also when the body produces goose bumps to warm us up. Both are a means to move us toward our target set point.   Your body is consistently monitoring, measuring and reporting via negative feedback loops to sustain a stable internal environment.
Closing the Loop
Defining Critical Success Factors (CSF) for our strategies and for our processes in ITSM is a good starting point for determining what is required in your measurement system.
Key Performance Indicators (KPI) allow us to quantify the CSF’s for targets.  These KPI’s make tangible our target set point.  Having a target set point can enable the service provider to scope the depth and breadth of measurement and ensure the target set point is stable. Using targets or set points in a closed loop system allow for appropriate thresholds, vital reporting, and most importantly set the tone and direction for all cross functional teams in the value stream.  The service provider and the business are able to work lock step together toward the same common goals and outcomes.   In the same way that an animal uses homeostasis to sustain stable internal body functions through multiple complex systems, a service provider can use nested feedback loops to sustain consistent performance while adopting and adapting to dynamic business requirements.  We get real-time information, scoped effort, and the means to automagically self-correct for ongoing continual service improvement.  
With negative feedback loops we speed up or slow down based on a target set point. We the service provider become dynamic in order to shift or change to meet customer demand.
 

If negative feedback loops are positive then what about positive feedback loops?



Stay tuned for - “ITSM …. We’ve Gone Loopy [Part 2 of 2]
 

 
 
 

 

 


 

 
 


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…