BPM is about to change

Dynamics in a process is complex, there is no one ideal way of getting things done in todays business. Process change so does people and business.

So how do you account for these changes when you are building your business processes, fact of the matter is you cannot. During the design phase, it is not practical to accommodate all permutation and combination of a process flow from end to end neither can you account for external factors that will influence your business process execution. So process cannot be structured, you have to empower process participants (end users) to expand or change process as they go without any strict restrictions just because someone designed the process that way. BPM is all about process improvement and not always process automation. Most vendors capabilities today revolves around process automation on structured processes, I make that distinction because I believe you can improve your process without having to define the process before hand. The reason you can do this is because you are implicitly turning your process participants a contributor to how the process should be in real life, you are getting direct feedback from the "knowledge workers" in your organization.

This concept is coined as Dynamic BPM at Fujitsu. Dynamic BPM is a platform on which users collaboratively not only get their actual work done help build the process. While getting their actual work done is the direct action, the result is process that gets constructed automatically. An example could be an RFP process, when account executive (AE) receives the RFP from a customer, AE can define a team to complete the RFP, delegate/subtask to other members within the organization and own the process and control it. Lets say AE tasks it to product management (PM) and sales engineering (SE) to complete the RFP, PM can add their input and further task it to more people for additional inputs. Once all chain of events (tasking) is complete, the result is completed RFP that is ready for AE to be sent it to the customer. While RFP process participants have done nothing new but do their job, implicitly what we could generate is a "real-life" business process for an RFP process. This process is rich and clearly depicts the process routes. It is true that a structured process for automating the RFP process could have been built before hand but inflexibility will result if AE or PM decides to take a different route in getting the RFP completed. Since that was never captured in the structured process, people will fail to do their job which results in going back to the re-design of the process. But doing this entirely as a dynamic business process will result in improved productivity and better visibility to actual real life process.

The beauty of this approach is as more RFP process gets completed, the visualization will provide common patterns across these processes and eventually extract those common patterns and provide recommendation for context based process improvement.

Based on all my BPM experiences, this is an inevitable feature that all vendors will soon realize and jump into. You just cannot dictate users to do their work a certain way, Dynamic BPM helps overcome that at the same time govern the way work is done.

Do it your way...