<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 Case for Process Architecture

23A Business Process Architecture (BPA) is the primary artifact of process management and improvement. If you don't have a BPA, you aren't doing process management. If you don't have a documented and agreed understanding of the relationships and interdependencies between your key business processes, then you can't be sure you are really doing effective process improvement. Cross-functional business processes are the only way any organization can deliver value (products or services) to customers, and other stakeholders outside the organization. This gives the BPA primacy. A BPA discovers, defines, and documents the value pathways. More than just a picture or a model, the Business Process Architecture is a daily aid to strategic and operational management in an organization focused on continuous improvement and delivery of service excellence.

Creating a BPA is not a trivial exercise, and since it will always be subject to change and the exploration of greater detail, it is a never-ending job. Nevertheless a useful, working BPA can be developed in a few months and the immediate value of doing so can be remarkable. Quite apart from creating a solid basis for effective ongoing process management, discovery of the BPA focuses the organization wonderfully on really understanding how it executes its strategic intent.

If you read the above as strong, uncompromising, and unbending, then you start to understand my point of view. Let me explain…

What is a Business Process Architecture (BPA)?

For me, a BPA is something quite specific. It is a hierarchical model of the business processes of an organization. Usually created, initially at least, to include the three highest levels, the process architecture provides a powerful visualization and management tool. Over time, the BPA comes to include not just the hierarchical description of process activities, but also the related resources, documentation, performance measures, measurement methods, and governance arrangements.

I am not talking about what might generally be called a “Business Architecture” or some variation on that and the other artifacts of “Enterprise Architecture”. I am talking about the documentation of the highest levels of business processes in an organization, i.e. the pathways through which value is exchanged with customers and other stakeholders.

The increasingly common predilection to want to define every object in an organization, and then show its relationship to every other object via an impressively complicated and abstract diagram, seems to me to be of limited benefit to business managers. Organizational management is difficult enough without creating more complexity.

A comment I hear regularly amongst managers, especially senior executives, is that the frameworks they see are too complicated and offer little practical benefit in day-to-day operational management. They want something that is practical, proven, and effective.

As I define and use it, a BPA is a simple, but not simplistic, view of how the organization creates, accumulates, and delivers value.

It is a practical and pragmatic management tool.

Figure 1 below shows an example.

Process Architecture for University
Figure 1: A University Example BPA

The above image shows the top two levels of business process for a university. Now, many readers will have suggestions about how it could have been done differently, but that's not the point of this Column. This example was thought to be a very good reflection of the university operation by some 100 people who participated (and argued, and debated, and challenged, and disputed, and contested … after all, it was a university!).

The format of the BPA picture used here is common enough showing management, core, and supporting (aka enabling) processes. At this level, the modelling requirement is quite simple and the most useful tool might be ‘pen and paper'. Beyond this level, of course, if you intend to do serious process management and improvement, then you need a good repository-based modelling tool and the related infrastructure and expertise to use it properly.

Figure 2 below shows another BPA example, this time for a teaching hospital.

Business Process Architecture for a Hospital
Figure 2: Hospital BPA Example

Both of these examples of the highest levels of a process architecture hierarchy represent everything that the organizations do. The university creates graduates, conducts research and contributes to society. The hospital cares for patients, develops healthcare professionals, carries out research, and reaches out to improve community health. In both cases there are many other management and supporting processes that make those core activities possible.

The value propositions of, for example, create graduates and care for patients are embedded in the BPA because the highest level processes were derived from the organization's strategy. An organization's strategic intent is executed via its business processes so the BPA shows how strategy is operationalized.

A BPA is a hierarchy of business processes. The examples above show just two levels for the university and one for the hospital. When first developed, two or three levels of the BPA is usually sufficient. Over time, many more levels are defined and detailed as required to address specific organizational performance issues. Every process can be decomposed into sub-processes, so there is no theoretical depth limit. However, in practice, we go only as deep as is needed to address a particular issue. It makes no sense to say “we will identify all of our processes”.

Having documented a BPA, the obvious next question is how do we measure and manage performance of the processes so identified. That's a topic for another time, and you'll find much of that discussion in my previous Columns. Suffice to say here that the BPA does need to be maintained and that this needs to be done in a controlled and coordinated way. This is at the heart of process-based management

Watch 7 Enablers of BPM Video

Using a Process Architecture

A well-formed BPA is a powerful management and decision making tool that can be used in many ways, some of which are outlined below.

1. Focus on value

  • Visualize the organization's processes. If processes are to be managed and improved they must be defined, collected, and collated – that's a BPA.

  • Concentrate organizational focus on value delivery. If you develop and maintain a BPA you are constantly focused on value delivery via the business processes.

  • Expose ‘value pathways'. Value is created, accumulated, and delivered across the organization chart. A process view means this critical aspect is proactively managed.

  • Gain agreement about process deliverables. To agree on a BPA it is necessary to get agreement about the processes, what value they should deliver, and to whom.

2. Enhance communication

  • Provoke powerful conversations. When you ask “who are our customers and what value do they get from us?” get ready for powerful and valuable conversations.

  • Engage all stakeholders (internal and external). To develop a BPA, a list of stakeholders, and an assessment of the value delivered to them, are prerequisites.

  • Provide repository of process information. A BPA model provides a single place where all process information can be stored or linked, a portal to the process view.

3. Facilitate process performance management

  • Communicate process performance information. To focus everyone on value delivery, process performance needs to be defined, measured, reported, and discussed.

  • Define interfaces to external parties. Processes traverse organization boundaries to interact with external processes. Such interfaces can be defined in a BPA.

  • Understand process interdependencies. No process exists in isolation; change one process and others will also change. A BPA uncovers these interdependencies.

  • Prioritize process analysis/improvement activity. Every organization has many processes. Where is the Return On Effort in analysis and improvement?

  • Coordinate process project portfolio management. The output of one process is an input to another. Uncoordinated process change might just create a new problem.

  • Developing and maintaining a BPA is not about abstraction (or abstract art), it is about providing practical, proven, and effective support for the achievement of organizational performance goals through evidence-based, coordinated improvement in the ecosystem of business processes.


 DOWNLOAD PROCESS ARCHITECTURE PAPER

This article was originally published at BPTrends

 

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

Forget the distracting buzzwords - focus on organisational improvement instead.

  The development of organizational management theory should seek to make operational management simpler, not more complex. Is it possible that the primary goal of organizational performance improvement gets lost in the ever-increasing list of shiny objects such as transformation, digitalization, robotization, valuation, acceleration, innovation, automation, and disruption? Are the -ion ideas a distraction or a boon for good management? "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." Antoine de Saint-Exupéry [1]

What Are The Consequences of Unbalanced BPM?

As some readers will know from my previous writing, for example here, there, and everywhere, I take a broad view of BPM, seeing it as a management philosophy, preferring the term process-based management over business process management. A brief summary of that view is as follows. An organization's resources are managed 'vertically' via the organization chart. Value is created, accumulated, and delivered 'horizontally' across that chart, i.e., via cross-functional processes. Value is accumulated across, not up and down, the functional organization as the various parts collaborate to create, accumulate, and deliver value in the form of a desired product or service. It follows that an organization executes its strategic intent via its business processes. In this context, where cross-functional processes are key to the delivery of value and execution of strategy, the improvement and management of processes is critical to the optimization of an organization's performance. BPM is not a one-off project, nor an IT system; it is a management philosophy.

Leonardo announces partnership with Dell Boomi

MELBOURNE, Australia, March 18, 2018 – Leonardo, a technology firm specialising in end-to-end process improvement, has announced a partnership with Dell Boomi (Boomi), the only unified platform that radically accelerates business outcomes with intelligence that speeds the flow of data across systems, processes and people, to deliver digital innovations to a connected business.