BPM often overreaches. Understanding, modeling and managing a business capability effectively requires a balanced view of six basic questions, not just one, as given in the table below. I follow Zachman in these matters, so yes, the table is Zachmanesque.
Basic Business Question
Kind of Model
||What inventory of things needs to be managed to support business activity?
||structural model (e.g., concept model, data model)
||How do transforms of things in business activity need to take place to add value?
||Where does business activity occur?
||Who collaborates with whom to undertake business activity?
||interaction model (e.g., organizational chart, use case)
||When does business activity take place?
||temporal model (e.g., schedule, event model, milestone model)
||Why are results of business activity deemed appropriate or not?
||strategy model (e.g., Policy Charter, constraint model)
If your business does nothing but manufacture or produce physical widgets (forget all the meta-data about those widgets), you will probably emphasize question 2 (i.e., process
) above the others. Your overall approach and architecture will reflect that. You will naturally gravitate toward BPM.
That tendency has at least three basic risks, even for organizations that do fall into the nothing-but-widgets
- Your metrics will largely focus on process productivity (e.g., throughput, bottlenecks, latency), rather than strategic goals and alerts centered on external risks. E-suite executives tend to be much more focused on the latter.
- Your mindset will be procedural, rather than declarative, which can cause you to embed business rules in process flows rather than externalize them. As a result your process models will be unnecessarily complex and your overall solutions un-agile.
- You approach will fall woefully short in addressing the intellectual capital that underlies your processes. Such operation business knowledge ranges from simple meta-data, to the business logic that underlies operational business decisions.
Fewer and fewer business problems these days fall into nothing-but-widgets
category. Even for widget-centric
businesses, at least three needs are increasingly urgent:
- Ensuring the quality of meta-data.
- Demonstrating compliance based actual rules, rather than the artifacts and effects that IT systems produce.
- Retaining, teaching and repurposing intellectual capital.
These are not strengths of common BPM practices.
Read more about the future for processes:
What is the Future for Processes?
Are Processes and BPM Relevant in the Digital Economy? http://www.brsolutions.com/2015/10/19/are-processes-and-bpm-relevant-in-the-digital-economy/
Measuring Quality and Defects in the Knowledge Economy: http://www.brsolutions.com/2015/10/27/measuring-quality-and-defects-in-the-knowledge-economy/
Quality and Tolerances in the Knowledge Economy: http://www.brsolutions.com/2015/10/29/quality-and-tolerances-in-the-knowledge-economy/