Skip to main content

Culture Hack Required!

Image
By
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!)
And..

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!

Labels:

Comments

Post a Comment

Popular posts from this blog

The Four Ps of Service Design - It’s not all about Technology

By
People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People:   Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products:   These are the technology managem
Post a Comment
Read more

What Is A Service Offering?

By
The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group .   As a service provider, we can’t stop there!   We must know what the contracts of our service offering are and be able to put them into context as required by the customer.     Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include:     Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods.   Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you.   You the consumer own these and they are yours to take with you.               Note: Goods may not always be provided for every Service Offe
Post a Comment
Read more

What is the difference between Process Owner, Process Manager and Process Practitioner?

By
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
Post a Comment
Read more