Skip to main content

FAIL


We all know failure!  If a deployment for a critical service fails and negatively impacts business partners and consumers that can not be good.   One would have to consider why did this happen?  And even more critical is, why does it happen more than once? There are times when failure can be viewed as good. That of course is when we admit and then correct the reason or the cause of that failure.  Many organizations struggle with a culture that fosters hiding failure.   It is very difficult in this type of stringent culture to be effective and even more difficult to be efficient and innovative.   Not being able to admit or to discuss failure generally will lead to repeated and more disruptive failure.    What is a service provider supposed to do?  Do we fire individuals who drop the ball and fail?  If so, what size of failure would instigate such an action?  Do we restrict staff from elements or areas of the value stream so that their failure does not have the opportunity to impact us negatively again?  Both of these seem very harsh.  Even so this is the stance that some employers take. 

In order to optimize outcomes for service providers, a shift to a culture that is safe for all levels of management and staff will be required.  A safe environment is one where individuals feel free to speak up and are comfortable to express ideas.  I think it boils down to respect.  Having a culture where “respect” is at the foreground would ensure that we value each individual for what they bring to the table and it means that when mistakes are made leaders and staff alike are very vocal about them.  This means that not only could they admit error or failure but could broadcast it out in such a way as to omit repeat mistakes in the future.  

A safe environment requires high trust and a zeal for learning.  Learning comes from failure.  Some leaders will recognize teams or individuals that enable the organization to learn from failure.  Such awards send a message about their values and that message helps instigate a cultural shift to one that is safe.  High-trust organizations encourage good information flow, cross-functional collaboration, shared responsibilities, learning from failures and new ideas.  They also empower people which enables them to move more quickly. They don’t have to wait for someone else to make a decision or take action.  Companies that really want to show their commitment to success will continue to foster a high trust culture where experimentation and learning are enabled.  They encourage freedom to fail and model how learning from failure can lead to action.  What could you do in your organization to propagate a high trust environment where learning from failure with openness and respect leads to success?

For more information: http://www.itsmacademy.com/brands/DevOps.html and http://www.itsmacademy.com/orgchange/  



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

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