Skip to main content

Best Practice as a Meme

When looking at ITSM best practices we need to look at the culture of our organizations and understand how we would transform our organizations into value-laden delivery mechanisms. A culture is just the "known environment in which we live and work." Cultures are organic constructs--they are grown and guided, not imposed or dictated. Every person, group and organization has its own culture. The culture of an organization is really the aggregation of the individual or group cultures found within the organization. As a result if the culture of an individual, group or organization is not an environment focused on delivering value to customers, then transformation should occur.

So how do we go about transforming our cultures? We can look to some of the liberal arts for assistance in this. From the study of sociology we find the concept of "memes". 

meme--an idea, behavior, or style that spreads from person to person within a culture.

Many of you might be familiar with the term "meme" as being a funny picture or phrase reused across social media. The term "meme" has a much deeper meaning and function than a picture of a kitty with a humorous statement associated to it. "Memes" are modes of transferring cultural behavior from one person to another. "Memes" are a very effective way of transforming ourselves, our cultures and ultimately our organizations.

Based on the definition, ITSM best practices are in fact a type of "meme". They are a means or mode of transferring an optimal way of approaching the delivery of value through IT Services. So we should be looking at ITSM best practices not just as a set of practices, rather as a means of cultural and behavioral transformation. As a "meme" ITIL and ITSM best practices help us to instill desired behaviors and actions that result in optimal outcomes for our customers. Because "memes" are a means of behavioral modification we should not forget that a bit psychology and sociology (from which the idea of "memes" originate) would be helpful in managing the transformation of our cultures and organizations. This helps us remember that when using ITSM best practices we are really talking about people and their behavior, not just a set of activities or processes.

So as you progress through an ITSM implementation initiative or effort, do not forget about the people. Use ITSM Best practices as a "meme" to help transform those people and your organization.

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…