There is an interesting discussion initiated by Peter Schooff @bpm.com
Is Low-Code/No-Code BPM Too Disruptive?
— Peter Schooff (@PSchooff) September 21, 2017
Low-Code or No-Code primarily creates a herd of “citizen developers” or “tool jockeys“.
It shadows the pro-developer mode of working – by getting dirty with code, tailing through never-ending log files on a command prompt, debugging and troubleshooting itch-scratching error or exception.
There are pros & cons to the low-code / no-code adoption by an enterprise:
- The complexity of the implementation is masked and encapsulated by the fancy looking visualization tools with drag-n-drop features, pre-built components and configuration palette made available as out-of-the-box offerings
- Business gets a feel-good-factor, with some confidence to incorporate the change
- One-Stack Development Platform providing ease of maintenance / single pool of likely skilled team / one touch deployment (fast & quick with improved TimeToMarket – if all the needs are fulfilled by the platform)
- Adopting a low-code / no-code platform creates a single point of dependency on the part of enterprise to live forever with the product
- Flexibility is less compared to bespoke ways of implementation (low-code platforms primarily demand living within the defined boundaries created by the platform)
- At times, creating custom plugins or custom code adhering to the configurations/features/limitations provided by the platform – demand for additional effort
In summary, low-code or no-code platforms are like “Lego Building Blocks“. If all the model/shapes are available to meet your business functionality – that’s great. Else, additional effort needs to be considered to crafting and creating a block to fit with other building blocks in terms of design/shape/polish/color.
In a way, Low Code / No Code platforms reduce the bridge between the IT & Business stakeholder (which is also the same goal/objective BPM as a principle has been advocating & rattling for more than a decade).
So, it is not too disruptive with regards to BPM. But YES as a terminology it is catchy! And going by the buzz in the wild of disruption, it becomes important for enterprises, to innovate and differentiate addressing the C-P-Q (cost-pace-quality) factor and building solutions (faster, better & cheaper) enriching the customer experience.
Finally, whether to use or not to use a low-code/no code BPM as a launchpad for the enterprise depends on multiple factors and key ones being – vision, future architectural/functional roadmap, maintenance, cost, enterprise landscape, customer experience, customization effort (if any) etc. It’s unfair to consider Low-Code / No-Code as “one-taste-suits-all” kind of an offering for Enterprises (some may like it a bit tangy and spicy – customizations are inevitable) 🙂
Is Low-Code/No-Code BPM Too Disruptive? What’s your take?
Happy Learning!! 🙂
Image Source: link
Nice Read Links: