<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

8 Benefits For Your Business When BPM is Managed Right

2019 Blog Images (2)

For nearly two decades I have worked with many organizations in different countries, cultures, and corporate structures to understand and advance the theory and practice of process-based management.


There is a common problem, a change of mindset and practice that many organizations fail to make. Process improvement alone is not enough. Successful process-based management also requires … management.
My goal is always to better understand, and help others understand, how all organizations execute their strategies through cross-functional business processes and, that in traditional management modes, those processes are not actively managed. We get work done in collaboration across the organization, and yet we mainly manage up and down.

More and more people are understanding what this means and, importantly, want to do something about it — they get it. I am encouraged by the increasing number of conversations I have on these topics with senior people in a variety of organizations around the world:

  • A regulation authority in the Middle East — they get it.
  • A specialty manufacturer in Europe — they get it.
  • A fresh food distributor in Asia Pacific — they get it.
  • A social services agency in the Arab States — they get it.
  • An infrastructure management group in India — they get it.
  • A government agency in southern Africa — they get it.
  • A national promotion agency in the Arab States — they get it.

They get that in actively managing cross-functional processes, as well as functional organizational units, management becomes less complex and more effective, organizations have more resilience and become more agile, and people are more motivated and engaged as they better understand the role they play in realizing the vision. They get that while process improvement is vital, indeed it's the end game, to make it efficient and effective requires process management.


It's not magic, it's not easy, but neither does it need to be so difficult, costly, or time consuming that it ends up in the too-hard basket. In designing a process-based management approach we need to avoid some common fatal flaws, flaws that are often deliberate design features hiding in plain sight.


The M stands for Management


The M in BPM is for management. That sounds obvious, hardly worth saying, but if you look at many, perhaps most, 'BPM' initiatives they have more to do with ad hoc process improvement, often via some form of technology implementation. Process performance improvement is the end game, and without that we are wasting time. However, to optimize the impact of process improvement we must be choosing the correct processes to improve and then actively manage to maintain the new level of performance.

Organizations need both continuous process management and continuous process improvement. Which processes should be analyzed and improved? Why now? In which order should processes be tackled? What will be the impacts of any change? Should we address processes based on the volume or source of complaints, or is there a better evidence-based approach? Where is the best return on process?


Process-based Management


I have described my view of process-based management in many places, including here, here, and here, so I won't repeat the details. Suffice to say here that the critical elements are that organizations must discover and document their processes, understand how they should perform, know how they are performing, decide what performance gaps are worth closing, and take steps to make the required closures. And repeat, forever. They must do this in the context that most traditional management effort is directed up and down the organization chart rather than across it where value is created, accumulated, and delivered.


Return on Process


There is no immediate, hard, measurable ROI for setting up process-based management. This is foundational work and to argue otherwise will result in loss of credibility. Establishing process-based management takes some time and resources (but less than many think) and creates an active process management environment, a system, that will deliver significant and measurable benefits later. These benefits come from:

  1. More active management of the high-impact, cross-functional processes (processes that may not be getting much management now).
  2. Detecting problems before they occur by analyzing and responding to process performance trend data.
  3. Identifying opportunities for common processes that can lead to shared service delivery mechanisms.
  4. Improved ability to measure organizational performance in meaningful ways, leading to enhanced management control.
  5. Making evidence-based decisions about which processes should be improved first, resulting in better prioritization decisions.
  6. Better understanding and continual assessment of the risk of process failure, and an enhanced ability to implement countermeasures.
  7. Greater organizational agility derived from a deep knowledge of how work gets done and how strategy is executed.
  8. Supercharged organizational culture where everyone is aware of how they contribute to the cross-functional processes that deliver customer value.


Many benefits flow from enhanced process management, and the main benefit is much better process improvement.

 

New Call-to-action

Roger Tregear
Roger Tregear
Roger is a Consulting Director 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

8 Benefits For Your Business When BPM is Managed Right

For nearly two decades I have worked with many organizations in different countries, cultures, and corporate structures to understand and advance the theory and practice of process-based management. There is a common problem, a change of mindset and practice that many organizations fail to make. Process improvement alone is not enough. Successful process-based management also requires … management.

The Ultimate Guide to Process Modelling

A new day, a new process modelling project. The project plan has been signed off, reference documentation was gathered, all stakeholders have been identified and now…now what? While process models increase in popularity and most businesses seem to agree that process models are indeed a good way of representing how an organisation creates and delivers value, there is little to no guidance on what a good process model is, how to create one and how to successfully go about executing a process modelling project. While this guide does not claim to be a silver bullet for all your process modelling problems (look at our Modelling Excellence framework for that!), it aims to be a guide for Project Managers and BPM Professionals in every stage of the modelling journey, regardless of whether you’re just kicking off a new modelling project, are in the middle of a major project, or are just looking for a refresh. Please note that this guide does not address steps to set up or configure a process modelling tool. It is focused on the activity of process modelling.   Let’s get started! This section includes topics that should be covered prior to kicking off any process modelling project. If a project is already underway, but struggling, we recommend revisiting this section to ensure the basics have been covered. If your project is already underway and going well, you may opt to skip ahead to the “Business Process Modelling” section. It’s all about the purpose… Firstly, ensure the purpose for modelling has been identified and agreed upon by all stakeholders. Whether it is communication, training, process measurement, improvement or configuration of a workflow tool, any modelling effort must serve a purpose. Major decisions such as “What modelling tool is the right one?” as well as minor decisions such as “Should I include this detail in my model?” can easily, logically and consistently be answered once the purpose has been identified. Consequently, if a clear purpose for modelling cannot be identified, no time and money should be spent on modelling as the models would end up being waste. The start of a process modelling project is also a good time to identify additional use cases for process models and pitch those to the stakeholders. The more use cases there are, the more robust the business case for process modelling becomes. Models that are re-used often are valuable to the organisation, rather than just useful for a one-off project. This does not mean that creating models for one-off use is waste. Although we generally recommend maintaining and re-using process models as much as possible, there are many valid use cases for and circumstances under which organisations choose to create process models that will be deleted once the project is completed. We do however emphasise that this purpose needs to be clearly identified and agreed upon, so nobody comes looking for the model two years later and needs to then kick off another modelling project since the former models are either out-of-date or nowhere to be found. Understanding the purpose of modelling will also help Modellers in the information elicitation and model validation stages of the project. They must always be prepared to explain what they are doing, why they are doing it and how it benefits the organisation. A strong pitch for modelling, tied back to the purpose, will help to keep stakeholders focused during workshops.

Moving From Continuous Improvement to Continuous Process Management

  Continuous process improvement is a common organizational aspiration, and it is one of the most difficult things an organization can attempt. The continuous aspect is quite a challenge, as is realizing business performance improvements—especially once the easy and obvious changes have been made. Organizations need an ‘internal improvement engine’ that replaces insistence with evidence.