Not so fast! Why you can’t just forget the code and embrace the vibe

The risks

But, before you get rid of all your software engineers, think carefully about the danger of creating applications that contain significant coding errors or that are of inferior quality. Business users with little experience of software testing may not spot these issues, while software engineers may find their time is taken up debugging the creations of users who didn’t really know what they were doing.

The risks of writing code without professional expertise include:

• Software that lacks basic security protocols and/or incorporates compromised open-source code, rendering the organization vulnerable to cyberattack.
• Compliance failure – users may not know what’s required to develop compliant products.
• Intellectual property violation, which may leave the business vulnerable to legal challenges.
• Risk of chaos – you want to encourage creativity, but must avoid an unsupervised free-for-all, with users acting without regard to organizational priorities.

Risk vs reward

Here’s how to balance risk and reward:

• Put guardrails in place: good governance can protect the business while enabling it to reap the benefits of the low-code/no-code approach.
• Develop clear policies for the use of the tools, including development standards, approval processes, and deployment procedures.
• Use cybersecurity and regulatory professionals to assess security and compliance risks.
• Keep careful records of how the tools and platforms are used.
• Provide training for business users who want to explore the tools.
• Promote a culture of security awareness that empowers all employees to voice their concerns.
• Monitor everything – carefully track usage and output performance of all low-code/no-code solutions.
• Manage your data – implement clear policies on retention, storage, and disposal of data used by applications built by business users.