Skip to main content

Three Golden Keys to Unlock the Power of Your ITIL Qualification

These “Three Golden Keys” are powerful! They can unlock the power of your ITIL 4 Qualification and will accelerate your journey in the right direction as you achieve one goal after another!

Believe in Challenging the Status Quo With ITIL 4 
Get out of the box. It is a new world. Leaders and teams will succeed by creating an environment to challenge the status quo. You are free, give yourself permission to question the status quo of your organization and invite others to join you. We must stop doing the same thing over and over again and yet expect a different result. Use the idea of a Service Value System, Value Steams and the four dimensions and apply the ITIL Guiding Principles as you “Challenge The Status Quo”. Real change begins with YOU! 

Keep The Momentum Going! 
Getting your ITIL 4 Qualification is a huge milestone in your learning and career path. Once there, the real journey begins. Be sure to get the most value from your accomplishment and the best practices that you have learned. Use it! Honor the past and leverage from all the valuable work and effort that is in play today. Recognize that there will be some areas where we will have to radically rethink the way we do work. Things like security, regulatory and legal requirements will always be there but when and how we accomplish this will need to be modernized and accelerated. So yes, honor the past but don’t be bound to it. To keep the momentum going set short simple goals at first, use what you have learned to achieve them. Set the next short simple goal. Use the idea of systems thinking along with the ITIL 4 Practices and Principles you learned to “Keep the Momentum Going. Continue innovating and continue learning more. Watch for “Managing Professional Transition” and other follow on courses that are available to you and others in your organization. Don’t Stop!

Shift the Culture – Change the way we Speak! 
Words or terms are powerful. To change a culture, we must change the way we think. Once we change the way we think we can begin to get creative about the way we work. Be aware and be very intent to listen for how you and your colleagues talk. You will find that many speak a language of exclusion, a language about “what is not,” instead of “what is” or “what can be”. Using the proper terms that you learned in ITIL 4 certification classes can shift the way you and others think and help to trigger a change in culture. A culture that is energized and empowered to be dynamic. 

Examples of how some organizations begin to change the way they speak: 
Use the term Speed to Value vs. Time To Market. 
(Focus on Outcomes and Customer Value) – Shift for engagement of all stakeholders 

Engagement Plan vs. Communication Plan 
(Focus on Co-Creation of service rather than silos) Learn how to collaborate rather than tell! 

Us vs. Them 
(Focus on integrated cross functional collaboration) – Shatter the Silos! 

Your journey does not end with the ITIL Qualification. Be empowered now. These Three Golden Keys are simple and yet, a very mighty way to begin the journey to unlock the power of your ITIL 4 Qualification. 

...educate and inspire…

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…