Skip to main content

How to Move and SHIFT the CULTURE!

There are three core frameworks that can help us to shift the way we think, do work, and ultimately shape the behaviors and values that are the heartbeat of our organizations - CULTURE! Each of these models can be used to identify, analyze, and move an organization to new heights, new ways of collaborating and increasing speed and value for service consumers.

Models for learning how to "Shift the Culture!”

  • Erickson Model – Identifies the stages of psychosocial development 

The Erickson Model helps as a starting point for “Where are we now?”.
  • Westrum Model – Focus here is on the organizational types:
 - Pathological
 - Bureaucratic
 - Generative 


The Westrum Model helps providers get detail on the behaviors within their organization and teams. 

  • Laloux’s Culture Model – Frederic Laloux’s model provides a clear picture of how culture may evolve in an organization. Laloux expands the concepts of the two previous models.

The model comes from Reinventing Organizations – a landmark book in the development of organizations that unleashes the talents of people to get astonishing results. The book is grounded in case studies from organizations around the world that are succeeding in a new way of working. The book has inspired and helped many see what is possible. Here the focus is on the “Advice Process” and others that interact with the Ericson and Westrum models.

These models and more relating to CULTURE are addressed to ensure the success of many service management frameworks including; ITIL, DevOps, Agile, LEAN and others!

ITIL – CULTURE is a key element in all aspects of ITSM and is described in great detail in one of the four dimensions - Organizations and People.  Actually, culture is covered at some level in every ITIL certification course.

DevOps - CULTURE is one of the core principles of DevOps and the need to focus on CULTURE is addressed in the DevOps FND, DevSecOps, and DevOps Leader certification courses from ITSM Academy's DevOps Campus.

Agile – At its core, Agile Service Management (Agile expanded to ITSM and more of the value stream) has lessons for shifting the culture that are supported by the Agile Manifesto.

LEAN – Increased flow of work and removal of waste happens when there is a change in CULTURE!

Learn about these and other concepts that exploit CULTURE as a critical aspect for your service provisioning. 

Comments

Tom said…
Looks like a good post. I can't see the images at the moment though.

Tom
Thank you for alerting us to this issue, Tom! It's been fixed :) Happy reading!

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…