Skip to main content

CSI & Knowledge



Stuart Rance wrote in a blog “Knowledge only has value when it is available to someone, either because they remember it or because they are guided towards it at the time they need it”.  One of the key elements in support of CSI is Knowledge Management. An organization must continually gather knowledge about its services and support processes in order to look for trends, find improvement opportunities and develop strategies that will move them into the future.  The philosopher and essayist George Santayana wrote, “Those that cannot remember the past are doomed to repeat it”.

In today’s reality of increased rates of change, increased employee turnover, increased access to information and greater market completion it is ever more critical to build meaningful knowledge bases that allow an organization can create and capture value by insuring that data, information, knowledge and wisdom are being brought forward to benefit how and what the ITSM organization does to support business outcomes.
Through this undertaking, we can optimize the benefits of these lessons learned and in turn:
  • Enhance the organizations overall effectiveness by basing decisions on this valid information and knowledge.
  • Encourage greater customer supplier relationships, through increased cooperation from mutually advantageous experiences and information.
  • Continually improved ITSM and business processes from lessons learned from previous iterations and changes.


There are two important elements that all organizations must engage in order for there to be a successful Knowledge Management / CSI initiative:
  • Open culture, which maybe one of the more difficult undertakings to accomplish, because it so heavily relies on people changing the way people think and act with one another.  Best practices, lessons learned and tribal knowledge has to be shared across individuals, groups, departments and the whole organization.  This practice needs to be encouraged and rewarded, so involvement from the HR department can be essential for its success.  Growing the knowledge base for all will present opportunities for all to grow and learn.
  • Infrastructure will be needed to support this open culture.  This can come in the form of technical application or systems which enable and enhance the ability to record, store and share knowledge and experiences.  It also can be in the form of processes which allow individuals to have a defined methodology for ensuring these activities take place.

Data, information and knowledge can be captured throughout the entire lifecycle.  It is critical that it be gathered, recorded, organized and accessible by all stakeholders.  Using best practice Knowledge Management techniques ensures it enhances any CSI initiative.

In addition to education opportunities be sure to check out some of the resources at this site: www.itsmacademy.com  



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…