When to Use Low Code (And When Not To)

The best way to summarise the sweet spot for low-code tools is to compare it to the IKEA analogy. Low-code tools, like the market-leading Power Platform, are akin to assembling pre-configured IKEA bits and bobs into simple solutions. Power Apps, Power Automate, and Power Pages are examples of such tools. They are excellent for citizen development, where business users can create solutions without waiting for IT, much like quickly assembling IKEA furniture without needing custom-made pieces.

Citizen development harkens back to the original marketing spiels from almost a decade ago, emphasising accessibility to all organisational levels. Like spreadsheets, low-code tools allow users to bypass IT backlogs by quickly throwing together simple, often manually integrated, solutions. Spreadsheets, the ultimate low-code tool, have been around for decades and are accessible to anyone in the organisation.

The sweet spot for low-code tools sits between the simplest technology for citizen development (spreadsheets) and more sophisticated solutions requiring pro-code (professional code using ubiquitous, free, open-source technologies). When IT professionals use low-code technologies, it indicates that the technology is being misapplied. These tools should be a safety valve for businesses to act independently while waiting for IT to deliver more robust, documented, and cost-effective solutions.

A practical way to determine appropriate use is to consider the solution's size and complexity. Low-code solutions should not aim to serve 100-300 users. Instead, they are best for automating processes within small teams (one to three people) with minimal external interaction. Typically, these processes involve a form submission leading to a dashboard actioned by one person or coordinated actions by a small team.

A general rule of thumb is to use low-code technology for simple, single-trigger business processes with one response. These solutions can be interim measures before IT develops more comprehensive solutions or long-lived yet simple processes. It's important to recognise the limitations of citizen-built solutions, particularly the challenge of maintaining and understanding these solutions once the original creator has left the organisation.

The analogy of building IKEA furniture is apt here. You might use IKEA shelves for a short-term need around your TV, but ultimately, custom-built shelves designed for that specific space are more suitable. Similarly, while low-code tools can address immediate needs, more complex, long-term solutions require professional development. Organisations like major banks have found that these citizen-built solutions can be "brutal," as they become difficult to maintain when the original builder departs.

In summary, the sweet spot for low-code technology is citizen-built solutions that act as interim measures before IT builds bigger solutions or are simple, long-lived processes managed by small teams. They provide quick, accessible solutions but are limited in scope and sustainability compared to professionally developed applications.

Andrew Walker
Technology consulting for charities
https://www.linkedin.com/in/andrew-walker-the-impatient-futurist/