top of page

๐‹๐จ๐ฐ ๐œ๐จ๐๐ž ๐š๐ซ๐ž ๐จ๐ง ๐ญ๐ก๐ž ๐ซ๐ข๐ฌ๐ž- what are ๐’๐Œ๐„๐ฌ ๐ซ๐จ๐š๐๐›๐ฅoks?



It can be said that the benefits of using low-code platforms with the participation of personnel who knows the processes across the business are known. The raising of low code (and no code) solutions already forecasted by Gartner since 2017 show a progressive adoption across businesses worldwide.


Particular attention now is directed to SMEs: it has been widely accepted with RPA-Robotic Process automation (See previous article here), and they represent a great way to approach Digital Transformation.


However, it must be considered that there are still roadblocks to adopting Low (and no) code solutions in SMEs. And it is crucial to increase their awareness of them.


A general potential roadblock is the lack of awareness of the benefits, the high-level technical solutions required, and how to approach a change proposition and cultural impacts.


The concerns about these strategic choices are based on four linked factors: vendor lock-in, security and scalability, and increasing user customisation requests.


Vendor lock-in?

The current situation related to the technical aspects of platforms is that in case one solution canโ€™t satisfy the original requirements, is not switchable with others creating disruption in terms of missed ROI achievement, new investments, morale and change fatigue. The intangible part related to human resources becomes exceptionally crucial for firms with low resource capability and financial aspects.


BAU with hybrid IT support

There are situations where always, cause of limited resources, companies use as support both internal and external IT services. Thus, the transformation towards a more internal dependency is not easy and requires extending training to IT, of course, but also to the citizen developers, and the first phase involves vendor resources. This can be a challenge that must be appropriately managed in the implementation and maintenance phases. New roles or new processes need to be in place.


Adaptability customisation: fears of internal IT resources?

Based on research, IT internal resources are sceptical about the full adoption of the approach from citizen developers: they fear that for reasons related to 1โ€”individual capabilities and skills 2. Old habits (letโ€™s ask ITโ€ฆ) 3. Perceived complexity before, during and after implementation


Security and scaling capabilities: fears of IT resources and the company.

There isnโ€™t much to add as information: security is both a technical and risk assessment; scalability is related to a holistic vendor evaluation; the latter should be related either to a potential new business model ( as a guide) or a business strategy (developed from BM) to foresees possible further changes in business processes, markets, segments, marketing activities that can help in preparing a bucket list to add to current requirements.


Propension to change/ Change readiness

Well, this is something that business, culture and change assessments can give a preventive view of what further resistance could be and take the results as anticipated lessons learned to shape the overall project, and mainly, manage constraints in the current requirements, internal challenges and create forms of alignment between, people and external resources,


Whatโ€™s next?

The are two relevant appointments:

1. An interview with Gabriel Paunescu Based on a vendor view of roadblocks for adopting Low code( or no-code) solutions

2. A white paper built on several publications to increase awareness from a consultancy and managerial point of view.

Recent Posts
No tags yet.
bottom of page