Skip to main content

Posts

Showing posts with the label Certified Process Design Engineer

Confessions of a Change Manager

By Donna Knapp   At one point in my career, I was a change manager. I ran my company’s change advisory board (CAB), and I spent endless hours trying to convince project managers to submit requests for change (RFCs). Despite my best efforts, I invariably had to explain, fairly often, that ‘poor planning on your part does not constitute an emergency change on mine.’ At that time, the change manager role was one of the many hats that I wore. My ‘real’ job was service desk manager. We called it a ‘hotline’ then and so yes… it was many, many years ago. In that role, I and my team saw the impact of poorly executed and failed changes. We dealt every Monday morning with the chaos that came out of the massive changes made over the weekend. That was then. Since then, much has changed. But it was through that lens that, more than 10 years ago, I first started researching a movement in the IT industry called DevOps. At the time, it was early days for DevOps and individuals and organizations were s

The New Four Ps of Service Management

By Donna Knapp For years, people , process , and technology (PPT) was a widely recognized framework for balancing and integrating the components needed to achieve optimal performance and outcomes. In the ITIL v3 Service Design publication, this framework was expanded to the four Ps: people , processes , products , and partners . ITIL 4 has further expanded and evolved this framework to the four dimensions of service management. These four dimensions are collectively critical to the effective and efficient facilitation of value for customers and other stakeholders in the form of products and services. The four dimensions of service management are: Organizations and people Information and technology Partners and suppliers Value streams and processes. These four dimensions represent perspectives which are relevant to the whole service value system (SVS), including the entirety of the service value chain and all ITIL practices. Each ITIL practice is a set of organizational resources base

Focusing on the Fundamentals

By Donna Knapp Have you ever done business with an organization that liked to brag about all the extras that it provides, but doesn’t get the basics right? To some extent, the accelerated innovation that was sparked by the pandemic fueled this need to focus on the new and shiny. And for some organizations, it is what’s needed to stand out in the crowd, or to compete, or simply to survive. But here is what we know. All the new and shiny in the world can’t make up for a poor customer experience. You cannot sacrifice quality for speed. And a perk here and there can’t overcome the lack of trust that builds up when an organization fails to get the basics right day in and day out. So, what we’ve got to do is strike a balance. A feat that is easier said than done. According to the 2022 State of CIO report, 76% of CIOs say that it’s challenging to find the right balance between business innovation and operational excellence. And yet it is exactly what organizations today need to do… C. All of

Filling the Process and Framework Skills Gap

By Donna Knapp For many organizations, the COVID-19 pandemic exposed one of two ends of a spectrum: poorly defined processes, or overly-rigorous processes. At either end of the spectrum, these organizations likely struggled to adapt as the pandemic impacted our lives. For those with poorly defined processes, things were probably pretty chaotic. For those with overly-rigorous processes, things were most certainly taking way too long. Even organizations with well-defined processes felt, and continue to feel, pressure to speed up the flow of work, minimize toil, and automate processes where possible. To do this, they must develop a culture of continuous improvement and learning. Continuous improvement is an ongoing effort to improve all aspects of an organization; its people, processes, tools, products, services, and experiences… all of which are tightly integrated. Whether improvements are large or small, what matters most is that they are constant. The highest performing organizations a

Optimizing Value Streams and Processes

Value streams are getting a lot of attention these days for a couple of reasons. One is that value streams allow us to identify opportunities to minimize waste or bottlenecks across organizations, processes and functional silos, and to improve the flow of value. Organizations adopting DevOps , for example, are using value stream mapping as a way to improve the flow of activities during the software development lifecycle, and to improve cross-functional collaboration. Another reason is that value streams direct our attention to what customers value. For example, organizations can use value stream mapping to streamline new product development activities, improve time-based measures such as lead time and time to market, and identify ways to improve product quality. They can also use it to streamline the activities involved in integrating a new employee into the company and its culture. What these both have in common is that the focus is on optimizing the value-adding activities; with the

Up YOUR Game – Become a Certified Process Design Engineer!

I find that there are many people that do not understand WHAT a Certified Process Design Engineer (CPDE) really is (be sure to scroll down on the page and then download the free whitepaper for surprising details). The CPDE role is likely much broader and deeper than you might think! Time and Money?! Yes, but not at the expense of quality and stability!  The role of a Certified Process Design Engineer is a critical skill set for all IT service  providers. There are many frameworks and standards that  define practices and methods for achieving success; ITIL 4 , Agile , Lean , DevOps , COBIT, ISO, and Site Reliability Engineering (SRE) are only a few. My point is that while each describes processes and controls (what to do), they don’t provide clear, step-by-step methods and techniques for designing, reengineering and improving processes (how to do it).  A Certified Process Design Engineer equips managers and staff at all levels to lead the organization to do t

Process Design

I looked up “Process Design” and found: “The  activity  of determining the  workflow ,  equipment  needs and implementation  requirements  for a particular  process . Process design typically uses a number of tools including flowcharting, process  simulation   software  and  scale  models.”  Hmm… that is good but “So What”?  Why should a service provider care about process?  I have heard some say that process is secondary to automation.  Okay, sounds good, but then we have to consider, “What are we going to automate?” Every Certified Process Design Engineer knows that when it comes to process we are talking about activity.  The key is that we need just enough process and just enough governance to meet requirements.  Process design contributes to our ability to balance speed and agility with stability.   Having good process design allows for a smooth service belt that delivers value to customers and also gives a service provider the ability to meet business and customer dem

It’s Still All About “The Process”

Organizations adopting DevOps cultures and practices are able to deliver high-quality software faster. This means the business can deliver value to customers faster. You sometimes hear that DevOps and ITSM aren’t compatible.  In a recent ITSM for DevOps workshop an attendee asked whether process is still relevant for digital transformation initiatives in today’s environment.  The answer is emphatically Yes.   Now more than ever before the attention to process is critical.  Whether your company is striving to achieve traction for a cultural shift, for a digital transformation, to create a DevOps pipeline or any other improvement initiative, Process will always be a critical success factor.   Remember we are talking about just enough process. We cannot have over engineered bureaucratic processes. For our purpose here, we will focus high level on some of the process design considerations and mistakes to avoid.   To learn more about what is just enough and how to design or redesign your

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 with you information from our Certified Process Design Engineer (CPDE) class. Roles and Responsibilities : Process Owner – This individual is “Accountable” for the process. They are the go-to person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed, and documented ( check out our free process design templates !). They also 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 could be… “All Incidents must be logged”. Policies are rules that govern the process. The Process Owner

CPDE - Process Design Considerations

S o who should consider becoming a Certified Process Design Engineer (CPDE)?  Well anyone can consider it.  Is your organization engaged in some type of certification, working to reach some optimized level of maturity, trying to improve the processes you already have or create a process to meet some new customer requirement? All of these scenarios would employ the skills of a CPDE. To start with, no matter which framework or standard you are utilizing processes must be: Defined Documented Managed via performance metrics Continually improved  Undertaking this effort is not as simple as it may appear and having a staff member with the necessary skills and capabilities (a CPDE) ensures that clear and measurable improvement targets, along with a process design approach, can and will be carried out.   You first must understand the factors that are triggering a process improvement initiative.  These are just a few factors, but understanding why an initiative is needed is an ex

Process Design

I looked up “Process Design” and found: “The activity of determining the workflow , equipment needs and implementation requirements for a particular process . Process design typically uses a number of tools including flowcharting, process simulation software and scale models.”  Hmm… that is good but “So What”?  Why should a service provider care about process?  I have heard some say that process is secondary to automation.  Okay, sounds good, but then we have to consider, “What are we going to automate?” Every Certified Process Design Engineer knows that when it comes to process we are talking about activity.  The key is that we need just enough process and just enough governance to meet requirements.  Process design contributes to our ability to balance speed and agility with stability.   Having good process design allows for a smooth service belt that delivers value to customers and also gives a service provider the ability to meet business and customer demand at a

Process Maturity

So unlike the Billy Joel lyric “Love you just the way you are”, we can never be satisfied with our processes being just the way they are.  As the organizations that we are engaged by continually change and mature to meet customers dynamic requirements, our processes must be continually assessed, measured and matured to ensure that they stay relevant and deliver value long into the future.  This takes real time, effort and resources.  Organizations cannot possibly move from being informal or ad-hoc to having a fully integrated ITSM program in a short period of time.  Just being able to gather the correct components (people, process, technology and information) can be a lengthy process and, of course, there is the decision of which processes do I begin with. The saying “Rome was not built in a day” really applies in this situation.  We must begin from the perspective that each level of maturity forms the foundation for the next level of maturity. Trying to jump over levels will almo

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