Skip to main content

Culture Hack Required!

The risk is below the water and we are headed right towards it. Organizational Transformations, Business Transformations and IT Transformations are all at their very core really CULTURE Transformations! 

Ok friends, I’ve loaded this one up. For a deeper dive into some of the topics addressed in this blog, be sure to click on the embedded­­ links provided.

Culture must be considered to Drive Stakeholder Value - This is POWERFUL!

Think about how a culture shift enables the following:

  • Mapping the customer journey with all touchpoints and interactions. You can potentially map the customer journey and map the stakeholder’s roles and responsibilities brilliantly, but what about the cultural shift to enable these stakeholders? Without it we will likely fall short of our goals.
  • If we have any hope of converting demand into value via IT-enabled services – culture is key! 
  • Properly designing XLAs, SLAs and meaningful measurement models.  Without culture, the risk is high that even if you have a good plan, it will be a challenge for people to adapt! 
  • Managing multi-supplier environments is crucial for all of us – Culture! Culture! Culture! Do they fit? 
  • Finally, we must design for true customer and user experience (CX/UX) - an outside-in perspective that requires a cultural shift. A culture where it is failure encouraged!
You can have the best strategy and tactical plan for all the above but if your CULTURE is not ready, efforts are likely to fall short of optimization and efficiencies that you expect. Speed to value will suffer!

A culture shift is critical to:

Lead successful DevOps integrated pipelines.
  • Before we can work on CULTURE, we need to get level set and understand what DevOps really is! I find that when I go to a customer site, the understanding of what DevOps is is subjective. You cannot shift a culture for an integrated pipeline until at a minimum all stakeholders have the same shared goal in mind. Click on this link and then be sure to scroll down to download a free 10-page whitepaper titled “What is DevOps”.
  • DevOps Leaders and Culture (this paper will give you some tips)
  • DevOps Leader course – (be sure to check out the tab with Product Videos!)

Generate High Velocity IT
  • There are high performing organizations in the world that are exceeding speed to value, safety, and reliability expectations and they are provisioning co-created services fast. How?! They have a primary focus on the people. They incorporate things like trust and transparency. They transcend siloes and give autonomy to cross-functional teams. They continually shift the culture to meet dynamic business and customer need.  
Leadership is an ACTION not a title. Take Action!


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…