Improvement / Transformation As a Result of Disruptive Processes

I was recently asked about companies that have made improvements and/or had significant transformation as a result of disruptive processes. The one that I am familiar with is Netflix and their philosophy of injecting failure into the production environment to ensure systems are fault-tolerant and how they continually test their ability to survive “once in a blue moon” failures.

Introducing Chaos Engineering - Netflix Simian Army

http://techblog.netflix.com/2014/09/introducing-chaos-engineering.html

I did some additional Google searches: “Disruptive improvements” & “Improving your IT services in a disruptive way”. I think the following sites and resources provide more insight:

Disruptive Business growth steps – Dow Corning

https://www.dowcorning.com/content/publishedlit/solarticles/simple_steps.pdf

IPhone success: Disruptive innovation and continuous improvement

http://businesstheory.com/apple-teach-product-development/

Disruptive technologies: Advances that will transform life, business, and the global economy

http://www.mckinsey.com/insights/business_technology/disruptive_technologies

Disruptive Innovation – Third Degree

http://www.thirddegreeadv.com/disruptive-innovation

This book has additional information as well: The Innovators Dilemma, by Harvard Business School professor Clayton Christensen.

Comments

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

Search