Skip to main content

Your Comfort Zone is NOT Comfortable

We have all heard mantras and messages like “If it’s not broke, don’t fix it”. Some might still cling to values like “We have always done it that way” but great leaders in contrast will see a different vision and say “There is a better way to do this”. IT service providers in today’s industry need to get uncomfortable. This is especially true for executive management. Some of the best leaders in the world make it their business to experiment, get creative and challenge the status quo.

Whether your needs and interests correspond with the early stages of innovation, like education and professional enhancement, or at a later stage like funding and business development, Innovation is key and cannot be propagated by cynics whose horizons are limited by the obvious realities. So how do we manage the naysayers?

Successful DevOps, Agile, ITIL and ITSM all require cultural change. One thing we can all agree on: Change is Hard. However, with the right knowledge your team can be guided to become enthusiastic agents of change.

Organizational Change Management (OCM) helps to support, encourage and educate people throughout change in an effort to:
  • Maximize benefits of the change
  • Minimize the risks
  • Institutionalize the behaviors
In order to ensure success CIO’s and their peers will need to gain valuable knowledge about human dynamics and best practices for leading successful change. Executives and IT Staff alike should prepare to roll up their sleeves and build tangible assets to support business and IT alignment.

Delivering effective IT services is more about changing the way people think and behave than designing and implementing processes. Focus on behavior and culture will shift.

Comments

Popular posts from this blog

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

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

What Is A Service Offering?

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 than 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

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 th