Skip to main content

Process Design

I looked up “Process Design” and found:

“The activity of determining the workflowequipment 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 cost that won’t break the bank.  We could invest in all the best talent and tools in the world but without good process still not achieve the outcomes that we had hoped for. Good process design is agnostic to any framework or standard that you might follow in your organization and is critical for every service provider to meet their desired outcomes. 

There are many frameworks and standards that define best practices for achieving quality IT service management (ITSM) - ITIL, ISO/IEC 20000, COBIT, CMMI, DevOps, Knowledge-Centered Support, etc.

While each describes processes and controls (what to do), none provide clear, step-by-step methods and techniques for actually designing, re-engineering and improving processes (how to do it).


For more information on how to design, re-engineer and improve processes for yourself or for your staff:  “Certified Process Design Engineer”  or  “Certified Agile Process Owner”

Comments

All models are wrong" is a common aphorism in statistics; it is often expanded as "All models are wrong, but some are useful" The first aphorism is generally attributed to the statistician George Box, but it turns up quite frequently in process design and process maturity and capability frameworks. Currently, DevOps is becoming increasingly aware of the intersection between other process design and management tools and frameworks, in particular CMMI for Dev and CMMI for Services, TSP and PSP. The Development side of DevOps and the IT Service side have to mesh with each other to create a value-chain synergy. ITIL v3 and COBIT could also provide process skeletons upon which organizations could tailor the meat which captures their unique business model.

Popular posts from this blog

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 policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

ITIL 4 – Mapping the Customer Journey

All service providers are in the business of customer and user experience. It is not enough to compete on products and services, how services are delivered is as important as what is delivered.

The customer journey is the complete end-to-end experience customers have with one or more service providers and/or their products through the touchpoints and service interactions with those providers. In order to focus on the outcomes and on the customer/user experience, service providers are seeking to master the art of mapping their customer journey. Doing so allows them to maximize stakeholder value through co-creation of value throughout the entire value chain.

The customer journey begins by understanding the overall macro-level of steps or groups of activities that generate the need for interaction between the customer and the service provider. These activities begin at “Explore” and end with “Realize” where the value is actually being consumed by the end-users.
The Band of Visibility