Skip to main content

Biggest misconceptions about no-code BPM

Simplification of business through IT is often seen among primary benefits of the ongoing digital revolution. Low-code / no-code business applications are considered as a primary way to facilitate digital transformation of business. Complex digital solutions are respectively seen as failures in delivery of this expected and promised simplicity.

This collision is not related to IT or to modern technological age. Rather, it is a result of irrational and deeply rooted belief in miracles. It is so tempting and attractive to believe in a magic new software, which will instantly resolve all business problems, that many experienced managers eventually fall into this dangerous illusion. Multiplied by poor IT awareness and aggressive advertising of vendors, it yields false strategic decisions based on misconception of an illusive simplicity.

Why true and efficient business platform cannot be low-code / no-code? Because it must hold and enforce objectively complex real business logic of a company. Bigger company is, more information should hold its digital management system. Any attempt to cut this information for simplicity will result in a truncated and inadequate system, which ignores essential business information. Adequate platform should be as rich and versatile in code as business itself. Low-code slogan is generally a characteristic of oversimplified and not flexible platform incapable of adapting to broad and unpredictable business requirements.

On another hand, mission of BPM is in cherishing and embracing existing complexities of business environments into complementary business models, which simplify understanding of this complexity and facilitate its further transformation for increased business efficiency (but not artificial simplification).

Comments

Popular posts from this blog

CaseAgile Will Show BPMN Data Exchange between Visio and Leading BPMN Tools

CaseAgile announces a new release of Enterprise Composer™ add-on for Microsoft® Visio, which supports transparent exchange of BPMN diagrams designed in Visio with leading BPMN tools. CaseAgile will demonstrate capabilities of Enterprise Composer™ on upcoming "BPMN IN ACTION" event organized by The Object Management Group (OMG) in Seattle at December 10, 2018. Enterprise Composer™ offers a seamless and efficient way for every Visio® user into the world of professional business process management (BPM) systems and process automation. By using Enterprise Composer™, Microsoft® Visio can create executable processes fully compatible with BPMN™ 2.0 standard from OMG®, which is the global de-facto etalon for modeling business processes and can be used both by businesses and IT. Every BPM practitioner working with Microsoft® Visio now can import BPM models created in most popular BPM suites directly into Visio® and can export models cre...

Gap between process model and real process

There always exists a discrepancy between a model of business process, however well designed and accurate, and real execution of this process in a business environment. The reason for this gap is an unforeseen depth and hidden details inherent to any real process. Real business model of organization is ultimately unlimited in its depth. Going from highest management levels, it descends to individual departments, client relations, production units, technical code of equipment and controllers etc. In vast majority of cases, it is impossible and senseless to build a complete model covering all and every fine detail of the business. Omitted lower layers of the model create (pseudo) random fluctuations during execution of the model. Real execution paths of a process never follow its model exactly. However, in case of the correct model, we can expect to see that an ensemble of execution paths statistically converges to the model as to its average path over a significant set of observation...

Difference between workflow and process

Workflow is an implementation of process. Process is a template defining structure, rules, objects and their relations in a business environment associated with certain business goal or case. Workflow is a concrete realization of process in given business context. In other words, process is a plan, while workflow is a sequence of business actions taken according to this plan. Process is an architectural project, while workflow is a building created on this architecture. Multiple buildings can be erected from the same architecture. Unlimited sequences of actions can run along the same plan. But the plan or architecture behind all these varieties of buildings and sequences is a common ground cementing their distinguished similarity as a family.