<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

4 things to remember when creating Business Process Architecture (BPA)

Case-For-Process_fig1

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. This article details why Business Process Architecture is crucial as a strategic and operational management tool. 

Here are four practical steps you might consider doing now to get started on the creation Business Process Architecture (BPA)

  1. Just build it 

    You (yes, you) don't need permission to start building a BPA for your organization. Find the strategy statements and determine who are the customers and others stakeholders and your organization's value proposition for them. These are likely your core highest level processes (I'd call them Value Chains). Start decomposing those processes. You will need permission and agreement (and lots of it) to make it official, but you can start right now without anyone's approval.
  2. Hang it on the wall

    Once you've got something you and a few others think is reasonable, socialize it on internal websites or notice boards. ‘Hang it on the wall' and see what people say. Give folks the opportunity to comment and take note of who comments as well as what they say.
  3. Test performance

    Pick a process and try to measure its performance. If it was working well, how would you know? How is it performing? Is the performance gap something that should be fixed now?
  4. Continue the Discussion

    You've started the process performance discussion with a group of people who have expressed interest in the idea of process and the BPA. Keep talking.

 

New Call-to-action

This article was originally published at www.BPTrends.com

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.

The Process Life — What's It All About?

What's it all about? If you google "what's it all about" you get 4.5 billion results. Seems that we are keen to answer that question. Of course, it would be much more useful if there were just one answer. I have a similar experience when I ask people what they understand by "business process management" and related phrases. [2.5 billion, in case you were wondering.] It would be of significant benefit if there were just one answer here also. Good news! There is just one answer. The bad news is we all agree with that but have a different version. The great news is that we can solve this problem — if you all repent and agree with me!

Why BPM Maturity is an Untapped Organisational Superpower

  Processes deliver Every organization makes promises to customers and other stakeholders. Such promises are its reason for existence and are shaped as value propositions in the organizational strategy. Traditional management follows the organization chart with most management activity directed up and down that chart. But how do we get work done? How do we deliver on those promises? We work in collaboration across the organization, not up and down. Is there any box on that chart that can, by itself, deliver products or services externally? No there is not, that’s not the way it works. Processes deliver on our promises.