Net; Net:
Processes in the future will leverage rigid snippets (portions of fixed proceses) or processes will exhibt great adaptbility with the contraints of some rigid policies, but the days of pure rigid processes are numbered.
Tuesday, April 23, 2013
Days are Numbered for Rigid Processes
The name BPM generally conjures up preplanned and well modeled processes, but things are changing fast. In July, 2011 I introduced the concept of designing processes by doing and that was near the beginning of more flexible process design at Gartner. The idea of flexible/unstructured processes started to become popular. Now the worm has turned and inflexible/structured processes appear to be on the way out. Rigid processes are becoming a bit like a dinosaur.
Processes have to be dynamic and ad-hoc to chase the changing business outcomes in today's world. Like gymnast on floor exercise, she pursues excellence within the constraints of the floor mat and varies her paths and adjusts the routine as the music, pressure and mounting scores dictate. Processes have to do the same. Proceses have to be dynamic with explicit rules and dynamic orchestration. Proceses have to be ad-hoc with events, case mangement and social collaboration. Processes have to be intelligent with constraints, adaptive case management and goal directed. Processes of the future will contain various aspects of process adaptability and intelligence.
Net; Net:
Processes in the future will leverage rigid snippets (portions of fixed proceses) or processes will exhibt great adaptbility with the contraints of some rigid policies, but the days of pure rigid processes are numbered.
Net; Net:
Processes in the future will leverage rigid snippets (portions of fixed proceses) or processes will exhibt great adaptbility with the contraints of some rigid policies, but the days of pure rigid processes are numbered.
Subscribe to:
Post Comments (Atom)
Agree 100% with the need for "snippets" - we have been calling these "process fragments" and making good use of these for a long time.
ReplyDeleteThe transition required a shift from a BPM platform to an ACM/BPM platform, the essential difference being fixed processes with goals/objectives defined plan-side under BPM, versus a menu of process fragments linked by users, software, robots run-time side with goals/objectives defined at the Case level under ACM/BPM.
ACM is one way. Another is smart snippets that are goal directed and assemble just in time. Another is swarming agents made up of snippets. All leveraging emergent processes that are an instantiation of complexity behavior.
Delete