<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1907245749562386&amp;ev=PageView&amp;noscript=1">
Event_bg

The Leonardo Blog

All Posts

The Need of Process Performance Measurement

2019 Blog Images (2) (3)

A common scenario is that organizations seeking to gain the benefits of process-based management first invest a lot of time and effort into business process modelling, then develop and use process analysis methods, and perhaps even realize good intentions in some form of launch of the ‘new process approach’. So far, so good. After a short while, however, the process emphasis is waning, the initial enthusiasm is dwindling, and the new process approach is starting to look a bit old. What happened?

Maybe lots of things, but a common catalyst is that process performance measurement was not sufficiently emphasized. Bottom line was that there was no bottom line. There was no way to showcase the benefits delivered as a result of the additional effort required to do process-based management.

The most important question is “What’s the problem we are trying to fix?” and we must have a detailed, specific answer.

A common assessment: “Yeah, we got lots of diagrams and models, and we fixed some stuff, but it was a lot of work and we don’t have time to keep doing that. We’ve got plenty of problems and we’re keen on anything that helps in solving them, but this process approach seemed more like a new problem, than a solution. Where’s the benefit?

Surround ourselves with evidence

What do we need to do differently? Measure. Measure. Measure. Surround ourselves with objective, measured evidence, firstly of the impact of the process problem or opportunity, and then with the benefits of success.

Surely, we can all agree that having the right performance data at the right time in the right format is a prerequisite for effective management. Of course, ‘having data’ is just one part of good management—it is necessary, but not sufficient. We need to use that data to determine where, when, and how we should actively intervene to secure a well-understood organizational performance outcome.

It is also obvious that we need good process performance measurement if we are to prove that process improvement has worked, that it has delivered real benefits. “Seems faster” or “probably cheaper” or “customers seem happier” are not the evidence we need for a solid business case. In developing support for process-based management there is no substitute for credible evidence of proven positive results.

A measured response?

Why is it then that process performance measurement is both an obvious requirement and commonly absent management tool? I think there are four main reasons—all of which can, and should, be overcome with appropriate responses.

LC Graphics (2)

Figure 1: Why is process performance measurement often a missed management tool ?


  1. Lack of motivation. Why bother? We already have lots of KPIs. Some people immediately see the benefits of process-based management, some never get it, and the majority don’t care much either way. Benefits need to be defined and continually sold. Organizations always have functional KPIs (think KPIs related to boxes on the organization chart), but not so many that measure cross-functional processes, perhaps none. For process measurement to gain traction, the benefits of process-based management must be clear and accepted.
  2. Wary of measurement. In this organization measurement is a precursor to punishment. A manager in an IT services company resisted process improvements that would radically improve a serious customer satisfaction problem. What would he do that? Because he knew that he would be sacked for not improving the problem earlier. That sort of organizational culture will never be conducive to active process performance measurement—to believing that continuous problem finding is an obvious prerequisite for continuous improvement.
  3. Swamped by measurement. You’ve got to be joking—we’ve got hundreds of KPIs already. This is true. Organizations inevitably have lots of informal and formal performance measures. They are given different names, they are derived in different ways, and they have different impacts on management. Mainly though these existing measures are functionally bounded, i.e. they relate to something is within the control span of one organization chart box. This says nothing about end-to-end, or customer-to-customer, performance. Measuring the critical few KPIs of the high-impact processes will, over time, reduce the aggregate number of active KPIs as cross-functional process performance becomes more important than isolated points of performance. Process performance measurement rollout can be done one process at a time.
  4. Daunted by perceived complexity. How can we have KPIs for our thousands of processes? The idea of ‘measuring all of our processes’, is obviously daunting. However, not every process needs to be measured. A hierarchy of processes is defined by the process architecture. The measurement of the performance of any process also reflects the performance of its subprocesses. Starting at the top of the process architecture, and identifying the subset of high-impact processes, allows the capture of practical process performance without the need to continuously measure every process. Which processes need to be actively measured will also change over time. Process performance measurement need not be complex if approached in a structured, methodical way.

These four reasons for a lack of effective and sustained process performance measurement can be summarized as: a lack of knowledge of the benefits, an organizational culture that is not measurement friendly, mistaken concerns about the enormity of having to actively measure a very large number of processes, and unnecessary concerns about the complexity of building a new measurement system.

A practical approach to process performance management is needed that will deal with all these potential barriers to success.

Taking the measure of process

The first step is to document a process architecture from the top down, to visualize the processes that execute the organization’s strategy. I’ve written about this in detail before here, there, and everywhere. In short, start with the strategy and the promises it makes to customers and other stakeholders. From those promises (value propositions) determine the highest-level core processes. Decompose those processes down a couple of levels to give a comprehensive and coherent high-level process architecture.

A common mistake is to then try to measure and manage every process named so far in the architecture. Even with just three levels of the hierarchy defined this can be at least 50-100 processes depending on the number of highest-level core processes. It doesn’t need to be like that. Start with just a few processes—with just one if you prefer.

For the selected process(es) determine the measures or KPIs (or whatever terminology you prefer). If this process was performing as well as its key stakeholders would want it to, what would it be doing and how would we know? What are the critical few measures; if we could only measure three things about this process what would they be?

It is critically important to determine the measurement method for each KPI, i.e. where is the performance data to come from, how will it be gathered, and by whom? If it’s not reasonably easy to gather credible data in a timely way, the measurement of process performance will lose its appeal.

We have the KPIs, e.g. customer waiting time, now we need to set specific targets, e.g. 98% of customers wait no longer than three minutes. It might be more complicated than that if, to continue the same example, there are platinum, gold, and silver status customers with each getting a different service level. Targets might also vary by time of day, day of month etc. The target for a KPI might be a matrix rather than a single number.

Targets change over time. What was once important to measure is now not so important. Perhaps some measure we had originally chosen is now stable and not changing—we don’t need to measure a constant. A new process problem or ecosystem change might require different measures. This is not set-and-forget, it requires a continuous review cycle.

Collect and analyze the performance data and report the outcomes so that evidence-based decisions can be made about where to best invest in process improvement. Get the circles turning!

Taking the measure of management

Some processes are harder to measure than others, but none are impossible to measure. Process performance can never be simultaneously both important and unmeasurable.

If we are not measuring process performance then we are not doing process management, and we cannot know if we are doing process improvement.

 

New Call-to-action

 

 

 

Roger Tregear
Roger Tregear
Roger is a Consulting Associate with Leonardo. He delivers consulting and education assignments around the world. This work has involved many industry sectors, diverse cultures, and organization types. Roger briefs executives, coach managers, and support project teams to develop process-based management. Several thousand people have attended Roger's training courses and seminars in many countries - and Roger frequently presents at international business conferences. Roger has been writing a column on BPTrends called Practical Process for over 10 years. This led to the 2013 book of the same name. In 2011, he co-authored Establishing the Office of Business Process Management. He contributed a chapter in The International Handbook on Business Process Management (2010, 2015). With Paul Harmon in 2016, Roger co-edited Questioning BPM?, a book discussing key BPM questions. Roger's own book, Reimagining Management, was published in 2016.

Related Posts

10 Common Problems in Container Adoption - And How to Fix It

The Compelling Origins of Containers A number of years ago, it become clear that the rise of container platforms was more than just a passing technology trend.  A genuine technology shift was taking place that would undoubtedly change the IT industry forever. Early indicators were everywhere.  Investment by the largest software industry giants was significant, as was their marketing positioning.  Pivotal and IBM were aggressive with Cloud Foundry and Blue Mix.  Red Hat was progressive with Openshift and receiving industry praise.  Docker Inc stormed onto the scene.  Then Google started the Kubernetes opensource project with immediate impact. Locally, there were also strong indicators.  MeetUp groups were started and quickly became well-attended - especially the Docker meetups based in Australia.  In the early days, the meetings were sold-out, and eager attendees weren't able to secure a spot.   After a humble start, the Kubernetes MeetUp was became very popular and continues to be so to this day. There was something brewing, and everyone wanted to be a part of it.

How to Swap Between Different PAMlets

The following set of instructions are for swapping between the different PIE PAMlet environments. NOTE: These instructions follow the use case of swapping between DEMO-PIE and DEV-PIE, but the scenario is similar if you intend to swap in the other direction. Step 1 - Execute the script and follow the prompts

  • 45 min read
  • Jul 31, 2019 9:22:00 AM

How to Demonstrate the Mortgage Process PAMlet

Scenario : A mortgage application is automatically qualified and becomes ready for final approval In this scenario we will: give you a high-level introduction to using Red Hat's Business Central to view the Mortgage process and to view a Decision Table in the process (see Demo Steps: Business Central) allow a customer to submit an application for a Mortgage using the applicant's UI developed in Entando (see Demo Steps: Applicant UI) allow the mortgage lender to view the status of a mortgage application and then claim the application and move it to Final Approval (see Demo Steps: Lender UI)

  • 12 min read
  • Jul 31, 2019 9:01:00 AM