Another challenge is the perception among full-time developers that low-code development tools are incapable of
creating production-grade, mission-critical applications. Some developers are likely to resist adoption of such tools based
on the belief that command-line coding tools are uniquely capable of developing production-grade applications.
Additionally, developers may feel that digital solutions developed using low-code developer tools are not sufficiently
extensible or lack the depth of sophistication that is characteristic of command-line coding developer tools. That said,
professional developers are likely to revise this perception and adopt the view that low-code developer tools expand
their range of choices for development and accelerate the development process after they acquire more knowledge of
tools within this landscape.
How should organizations prepare to address and manage the key
challenges associated with the adoption of low-code development tools?
Organizations can provide developers with guidance about which use cases are optimal for low-code developer tools.
They can do this by developing an adoption strategy that features a road map for the progressive adoption of low-code
developer tools into application development initiatives. Such a strategy should specify goals for the adoption of
low-code developer tools among full-time developers as well as their use for the development of both customer-facing
and internal mission-critical, production-grade applications. Organizations should delineate an annual percentage share
of their application development portfolio that will be completed using low-code development tools that includes details
of how that percentage is forecast to increase annually over the next five years. Additionally, organizations would do well
to provide IT leaders with a set of criteria that can be used to evaluate whether a development project falls best within
the purview of low-code development tools or pro-code integrated development environments (IDEs).
Meanwhile, organizations can address the perceptions of low-code development tools among developers by illustrating
the expanded range of development options available to them as a result of such tools. Deepening the exposure of
low-code professional developers to low-code developer tooling is likely to underscore the sophistication and value of
the technology for a multitude of development use cases. Given that professional developers are tasked with shipping
code faster without compromising security or quality, their enhanced experience with low-code development tools gives
them the insight to accelerate development while enabling them to create richly nuanced functionality.
Further, organizations can create a low-code center of excellence that takes responsibility for creating and refining best
practices for developing, testing, deploying, monitoring, and managing low-code applications. This center of excellence
should also centralize training-related resources and documentation and render them easily accessible to interested
parties. Moreover, organizations would do well to implement governance protocols that provide guidance regarding
application design, data security, testing, monitoring, role-based access control, and ongoing operational management.