Low-Code/No-Code Solutions in Real Life – How to Save the End-User Developers Revolution?
In a rapidly changing field of technology, hype bubbles sometimes emerge that end up being too far ahead of their time. End-user development with Low-Code and No-Code tools is at risk to remain such a bubble, as end-user development is still a marginal thing in many organizations and LC/NC tools are becoming more of a toolkit for professional developers. What went wrong?
End-user development as an ideology arose in response to a globally imminent developer deficit. As the world digitalizes at an accelerating pace, the need for application and automation developers is growing faster than supply. The world’s largest technology giants have invested heavily in nurturing the idea of end-user development, and at the same time in developing the LC/NC tools and platforms.
The challenge is that the visions about end-user development have been unnecessarily rosy, and at the same time LC/NC tools have proved too difficult to use. Many technology leaders have also raised concerns about the quality and security of end-user-developed applications.
This threatens to tie the hands of end-user developers or divert their attention to “secondary fuss,” and the development of actual business solutions will remain in the hands of overworked professionals.
Codelessness alone does not yet secure the conditions for end-user development
Application and automation development professionals are able to jump from one customer and project to another, and when well briefed, they deliver solutions to even large business entities efficiently and securely. On the other hand, they are not experts in the customer’s business and their time is quite expensive.
The idea behind end-user development is to utilize the business understanding of the organization to address workflow gaps or bottlenecks. The challenge is that developing solutions that deliver real business benefits requires considerable technical understanding, even if the actual coding is not required.
In addition, the development of organization-wide processes through automation requires a deep understanding of how different processes in an organization work in relation to each other.
In order to have the conditions for large-scale end-user development, a good understanding technical and business operating environment is required of an end-user developer.
Better end-user development and better solutions with business insight
The unique value of end-user developers – a business director, a terminal or customer service manager or a customer service representative – is that they see areas for development in their daily life that others do not notice.
An end-user developer who is able to detect workflow bottlenecks and understand the digital (and manual) processes behind them has the power to come up with genuinely useful business solutions.
The greatest value generated by an end-user developer lies in its unique perspective and the ideas that emerge from it. A workable idea of an streamlined business process is often more valuable than an application or automation that is code-free developed from the beginning.
Get the most out of Low-Code/No-Code tools
The insight of an end-user developer is invaluable. Technical competence grows through doing and training, but insight arises only through work experience and business understanding.
Therefore, when considering low-code / no-code tools and promoting a culture of civic development, it is worth considering how to support the implementation of the civic developer’s insight from the outset and allow technical know-how to develop at its own pace?
A solution like the Derobia Hyperautomation SaaS platform can help with this: The development work begins with process design and the functionality of the process can be tested within the tool without the need to immediately connect to data warehouses, ERP or legacy production system.
Again, when connections need to be built or other technical expertise is needed, tasks can be created for different parts of the process for professional developers or more advanced end-user developers. As knowledge is accumulated, the end-use developer can later take a more strict grip on the more technical stages of NC / LC development, if he or she so wishes.
The most important thing is that the technical threshold does not rise too high and that the insight of the end-user developer is taken advantage of from the outset.