<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

3 Ways to Measure the Usefulness of BPM

8-5

In the fair dinkum department, the most important question about BPM must be "is it worth the effort?" It works in theory, but does it work in practice? What is the return on process? How should we measure, and report, the outcomes of process-based management?

 

The Wrong Answer


Let's deal with the wrong answer first. It's not about the artifacts. No organization has a business problem called "we don't have enough process models." It is not a business improvement outcome to say we've trained 50 people on Six Sigma analysis, or appointed some process owners, or modelled a process architecture, or assigned process KPIs — these are all necessary, but none is sufficient.

To the executive not yet fully engaged with the promise of process-based management, all this activity might sound more like a problem than a solution, more like a waste of resources than a successful outcome. And if that is all that is happening, she would be correct.

We need good models, architecture, methods, and training — a metamodel of management — they are a means to an end, but not an end in themselves. Just having management tools is not the point; we must use them to deliver real organizational performance improvement.

If our process management and improvement activities are not delivering measurable, objective, proven organizational performance improvements — improvements better than we might have otherwise achieved — then our process activity is, by our own definitions, waste.

There is a Better Answer


We invest in process-based management because we think it is a better way to manage. Our objective is to make improvements in organizational performance, and that must be at the core of our assessment and reporting of the usefulness of BPM.

1. Identify Business Benefits


So, the first thing we must be able to do is to identify delivered business benefits, preferably supported by objective, quantitative evidence. The evidence here would be about reductions in time and cost, about solving specific customer satisfaction problems, about removing a quantifiable risk, or any other outcome that offers quantifiable proof of value. The benefits might be large or small, quick wins or longer projects, one-off gains or enduring benefits. It will be the aggregate of all benefits that will be the main assessment criteria. This may not be easy to do, but it must be done.

2. Assemble Compelling Evidence


Secondly, apart from the hard data of improvements, it may be possible to assemble compelling evidence by way of the support for process-based activity expressed by managers at various levels. Do managers across the organization think that the process activities are worthwhile? This is a customer satisfaction assessment.

The Net Promoter Score (NPS) approach might work well in that it would provide a single number on which to focus and the data collection is straightforward. NPS is criticized by some as being simplistic and too broad a measure. It would need to be properly tested and tailored to be sure it was reflecting the right outcome.

A common NPS question is "How likely is it that you would recommend our company/product/service to a friend or colleague?" The answer is usually a single number in the range 1–10. For our purposes in assessing the usefulness of process-based management, we might change that question to something like "How likely is it that you would recommend the BPM approach as you see it implemented in this organization to a friend or colleague?" Whatever technique is used, it should be possible to also make soft evidence compelling.

3. Measure & report on impact of BPM effort


The third type of required measurement and reporting is about how well the organization of process-based management is working and developing. This has more to do with the artifacts mentioned at the start. If we can demonstrate, using the hard and soft evidence discussed above, that process-based management is worth doing, then we must also show that the organization is developing its ability to do it. What is the health of the process management and improvement 'system'? Is it developing in accordance with a credible roadmap?

An important element in this regard is a regular assessment of BPM maturity and the development roadmap that such an assessment would produce.

If the organization agrees that the process approach is valuable, and the hard and soft evidence supports that it is, then knowing that the management infrastructure of BPM is being developed well is also important.


So, there are three types of assessments we should make to track and report the usefulness of process-based management:

  1. Hard data on problem solving and opportunity realization closely tied to the process approach, evidence of cost or time savings, of operational problems solved or averted — objective, quantitative, credible proof of value.
  2. Support coming from the set of managers and staff for whom the benefits should have meaning, evidence that they find the process approach making their working lives easier — subjective, qualitative, personal support.
  3. Evidence that the development of the infrastructure of process-based management is on track, that BPM maturity is developing according to a plan, giving confidence that the performance improvement outcomes delivered to date will continue and even increase — continuous development of the process of process management.
    If process-based management is to be supported, there must be proof that it is useful. That proof may not be obvious; some digging might be required to reveal it. Too often the need to measure and report, to tell and sell, the positive benefits of process-based management is overlooked.


The processes of process management and improvement can, quite rightly, be expected to be the most efficient and effective in the organization — and what do you think would happen if they were?

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