What About Unstructured Processes?

Comments: 1
Rate this:
Total votes: 4

The race to define, standardize, automate and improve processes started with Henry Ford’s assembly lines. This ‘structuring’ of processes has driven tremendous productivity benefits for organizations, and managers are therefore trained to consider the organization to be a sum total of its processes. A key management goal is to drive more structure into business processes with automation being the desired end-state. While most data-driven, transactional processes have been automated over the decades, there is a class of knowledge-driven processes that have eluded efforts to structure or automate them. These ‘unstructured’ processes are variously referred to as Manual Processes, Expert Processes, Case Management, Supervisory Functions and similar. And the goal has been to apply process-centric thinking to structure and automate these pesky but high-value-add processes. This is not working and a new decision-centric approach needs to be considered.


Unstructured Processes need Knowledge

Fig 1


Pushing the automation boundary deeper into Unstructured Processes (Figure 1) is a desirable goal but challenging due to the following characteristics of Unstructured Processes.

  1. Systems Support = Content Library: Since unstructured processes are loosely defined and rely on access to readily available knowledge, they are provided with ‘Support’ systems like an Enterprise Content Management (ECM) system, an Adaptive Case Management (ACM) system or a variety of collaboration toolsets. This is a more of a support role compared to the ‘Automation’ systems like Enterprise Resource Planning (ERP) and Business Process Management Systems (BPMS) that run structured processes.
  2. Knowledge-Intensive: Unstructured processes cannot run just based on raw data. They require a higher level of knowledge abstraction generally codified as Business Rules, Advanced Predictive Models, Optimization Algorithms and Learning Feedback Loops. These knowledge representation technologies have traditionally been difficult to work with but have now become much more accessible and scalable. Big Data is available now for mechanical knowledge extraction and learning. Being able to ‘inject’ this knowledge into processes is now much easily understood using Decision Modeling.
  3. Probabilistic Answers: Instead of programmatically deriving one answer, unstructured processes consider a variety of dynamic pieces of contextual knowledge and then make the ‘best’ choice depending on ‘chances’ of success. Decision Models capture this decision making and allow powerful technologies to be applied for plugging knowledge into processes.
  4. Predictive Capabilities: Unstructured processes involve using hunches and educated guesses for what might happen in the future given current data. These predictions are informal and vary greatly depending on the skills and experience of the agent. Formal predictive models can be generated from historical data and applied to decision making if decision requirements have been explicitly captured using Decision Models.


Decision Models inject Knowledge into Processes

Fig 2


Unstructured processes can be managed better if organizational knowledge can be systematically ‘injected’ into them. A Decision-Centric approach allows knowledge and data to be organized and accessed in a way that it can be consumed by explicit decisions that are part of processes (Figure 2). The Decision Model Notation (DMN) standard from Object Management Group (OMG) defines decision models and decision requirement models, along with the peer relationship with business process models defined using Business Process Model Notation (BPMN).

The key breakthrough is the realization that a process-centric view alone cannot push the automation boundary deeper into unstructured processes, but a decision-centric view is a critical requirement. A formal Decision Management Manifesto establishes the principles of this decision-centric view.


Deploy Structured Decision Services to Manage Processes

Fig 3


Explicit Decision Modeling results in detailed specifications and design for Decision Services. These are stand-alone services encapsulating powerful Decision Management Technologies. All modern systems can access these decision services and thereby take advantage of organizational knowledge in their processing (Figure 3).

A decision-centric approach that describes Decisions and Knowledge in terms of Decision Models opens up practical means for using advanced technology for Unstructured Processes. Whether all processes can be structured or not is a philosophical debate and irrelevant in the short run, since the goals of structured management are readily achieved by explicitly modeled, Structured Decisions.


Marek Szelagowski
posted 5 years 23 weeks ago

Very interesting

Very interesting article.
I’ve only some notes:
1. Generally I recommend to divide processes for:
• -static (structured) -we can prepare full algorithm, and usually they are changing in long period of time. And
• dynamic (unstructured, ad-hoc) –we can't prepare full algorithm, because it is impossible to predict and model all potential possibilities or all of the different customers' potential requirements. A need arises for the dynamic adaptation of business processes to the individual conditions of each particular case. (In consequence, the individualization of customers' needs requires in turn the individualization of business processes.) Or we have not enough knowledge to describe process in details.
2. We can identify dynamic activities or processes using BPMN ad-hoc processes. We can automate dynamic processes using dynamic BPMS (dBPMS -eg necessary functionality have IBM, Bizflow, Tibco, Bonitasoft, Bosch Software Innovations).
3. Of course I agree that "Unstructured processes can be managed better if organizational knowledge can be systematically ‘injected’ into them." Exactly 10 years ago in Warsaw School of Economic I prepared the concept dynamic business process management (dynamic BPM). It is a solution which enables enterprises to react to ever-changing conditions of operation (both interior and/or exterior) and cater to the individual needs of their clients in a timely fashion (and even provide a practically instant response in critical conditions), in accordance with process adaptations entered in real time by their direct process performers with access to codified knowledge of their enterprises. dynamic BPM is an extension of traditional (static) business process management (BPM) contains all the features of BPM and additionally allows to connect with knowledge management. It requires the implementation among others following rules:
I. Process execution should guarantee evolutionary flexibility,
II. Processes are considered completed only after having been documented,
The ability to change processes dynamically by their performers enables the whole enterprise management system to embrace the creative initiatives (new knowledge) of a wide range of employees, without running the risk of chaos created by unrestricted alterations to operational standards. Furthermore, the ability to trace the effects of changes enables users to enrich the enterprise's shared knowledge with information on which practices and solutions bring about the best and the worst effects. This approach centers on making actual, ongoing improvements and adaptations to business processes on the basis of the knowledge of a wide range of employees, verified by the client.
4. Sorry but I disagree that “The key breakthrough is the realization that a process-centric view alone cannot push the automation boundary deeper into unstructured processes”. Using ad-hoc activities we can describe dynamic processes enough to convey the knowledge included in them and to automate them. For example, using the dynamic BPM methodology we described the processes carried out by the air operations center. It seems completely dynamic the decision-making process of dispatcher's aircraft .
5. Including managing aircrafts which are in the air, taking off and being prepared for flight. Describing it as a dynamic sub-process, we used both the elements of knowledge bases, standard reference processes (eg reaction to the failure of the aircraft), the possibility of viewing earlier case and the possibility of contact with experts. All in BPMN, on the level of complexity understandable to users.
As a result we have working process and possibility to acquire knowledge day-by-day.
6. In some elements dynamic BPMS have functionality exactly like ACMS. What do you think about necessity merging dynamic BPM and ACM? And as a consequences merging systems BPMS (dynamicBPMS) and ACMS?

Join the Discussion