Skip to main content

Service Management - Education vs. Training

Although these terms are frequently used synonymously, “Training” is not “Education”.   This is not to say that training is not important because without training, education would be incomplete.  When investing your capital to increase performance and change behavior it could be beneficial to understand the distinction.

Education
When we are educated we learn facts, theory or required details about the who, what, where, when and why of a particular subject.  Sometimes education will build on a foundation of knowledge so that you may become more expert in that area.  A simple example is given with the idea of a language.  You may know how to speak it.  When you go to school and are educated you learn what a verb is, and how adjectives are used.  We learn the syntax and constructs of the language.  Some move on to be expert linguist. They become educated and highly skilled in the subject of language.
When you are attending a Service Management or DevOps course you are learning about industry best practices, standards, process activities, the roles and responsibilities required and more.  This is a form of education.  When a learner takes those concepts and puts them into practice one could say that the cost of your education has proven to be a good investment!  
Another benefit of taking your education and putting it into practice is the tacit knowledge or experiential knowledge gained.  Education inspires.  Education can change ones viewpoint and outlook.  Inspiration can lead to changed behavior. Those who are educated are skilled and are generally able to operate in higher performing job role functions with a higher pay scale.

Training
There are many forms of training, but simply put training is a way to teach someone how to perform a task. Sometimes these are repetitive tasks and an individual can become very skilled at performing them.  A soldier is trained in warfare.  Another form of training is physical training.   The linguist although educated may require repetitive training to speak the language just right.
If we take the situation above where an individual was educated on service management best practices, then an example of training in this area might be the training required for tools.  The operators and support personnel would need to be trained on how to record an incident with the tool that is selected by their company.  Other technicians will need to be trained on how to configure the tool.  But wait!  How can they configure the tool if they do not know the concepts of service management and are not educated?  How will they know what the processes are or where the integration points should be?  How can they configure or even use the tools for best practices if they are not educated?  On the other hand, if we do not have training on how to use and automate with tools, how can we hope for excellence?
Therefore, it is likely that in order to optimize resources and produce the best business outcomes possible, both education and training will be required.  When selected properly, the return on investment could be astounding.


“Educate and Inspire”  http://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…