Thoughts on People and Process

The “Agile Manifesto” states that “We value Individuals and Interactions over processes and tools”. What? Some have taken that statement and interpreted it to mean that when it comes to design and development … “No Process” is required! In fact if we look further in the manifesto we see clearly that the value of process and tools is indeed recognized. The manifesto is trying to impart the importance of people and interactions. If we have a brilliant process that is defined and documented and yet drop the ball when it comes to people and interaction we will surely miss the mark every time. Therefore, while there is value in process and in tools service providers must value the people and interaction with them more.

In her book titled “The ITSM Process Design Guide” Donna Knapp stresses the importance of “Just Enough Process”. When designing ITSM processes such as Service Level Mgmt, Change Mgmt, Incident Mgmt and others, service providers could miss the mark and over design the process. An over designed process more often than not could create more bureaucracy, ambiguity, and frustration than it could ever deliver business value.

This ITSM process design guide is used as a source document in training for those practitioners who want to acquire a “Certified Process Design Engineer” certification. In addition to understanding how to design, re-engineer, or improve processes, there is a section that supports this same idea that we see in the Agile Manifesto. In order for a process to ensure valued outcomes the “people” aspect and the management of organizational change are essential.

“A key to successful organizational change is proactively planning for the change and the inevitable emotional responses that the change will evoke. Successful organizational change takes time and effort and must occur with people and for people, and not to people.”

For more information on:

How to design, re-engineer, or improve processes with just enough process while valuing people and interaction
How to become a “Certified Process Design Engineer”
And… how to gain 38 PDU’s

http://www.itsmacademy.com/certified-process-design-engineer-cpde-course-accredited/

For more information on people and processes:
http://www.itsmacademy.com/itsm-process-design-guide-book/

Comments

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services, which is people. Because the people element adds variability, the service is variable. This holds true, especially for the value proposition—not eve...

What Is A Service Offering?

The ITIL 4 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 1. 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. ...

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

This article was originally published in 2015. With the Introduction of ITIL 4, some of this best practice has changed. See ITIL 4 and the Evolving Role of Roles . Updated Definitions in ITIL 4: Process Owner: In ITIL 4, the concept of 'processes' has expanded into broader 'practices.' Consequently, the Process Owner is now often referred to as the 'Practice Owner.' This individual is accountable for the overall design, performance, integration, and improvement of a specific practice within the organization. They ensure that the practice achieves its intended outcomes and aligns with the organization's objectives. Process Manager: Now commonly known as the 'Practice Manager' in ITIL 4, this role is responsible for the day-to-day management of the practice. The Practice Manager ensures that activities are carried out as intended, manages resources assigned to the practice, and oversees the practitioners performing the work. Process Practit...

Search