Arthur D Little Prism Low Code No Code
Arthur D Little Prism Low Code No Code
Prism / 1 / 2020
Over the last decade we have seen the “softwarization” of As the saying goes,
products, services and experiences. Organizations that spent “software is eating
decades developing and improving their business models the world,” forcing
companies to change
and core capabilities have been outcompeted by those that
their business models
disrupted their own business models with software. It has
and operations. In a
been famously said that “software
highly competitive
is eating the world”1, and in today’s environment, ensuring
highly competitive environment, they have the required
organizations find it challenging software capabilities is
to fulfill the development and a challenge. This article
operational demands needed to shows how adopting
keep their businesses running, while low-code/no-code
continuing to expand and enhance techniques enables
their digital capabilities. businesses to widen
their options, providing
tools for non-specialist
In this article we will explore
“citizen developers” to
how enterprises can leverage
digitize and transform
today’s low-code/no-code (LC/NC)
their operations.
solutions – declarative2 development
options with relatively low learning
curves that provide the company’s
workforce with tools to easily create software to grow and
transform the business.
1. “Why Software Is Eating the World”, Marc Andreessen, The Wall Street Journal, 2011
2. Declarative programming is a programming paradigm – a style of building the structure
and elements of computer programs – that expresses the logic of a computation without
describing its control flow.
Low-code and no-code tools are the latest stage in this
evolution. They allow anyone to create application
software through graphical user interfaces and declarative
programming. LC/NC development platforms provide tools
for designing applications or systems, along with their
required inputs, outputs and business logic. LC/NC takes a
visual approach to build business applications more efficiently.
This allows “citizen developers” – such as designers and
businesspeople – to build and test applications quickly,
without the need for developers.
Task
Event
Benefits of LC/NC
•S
mart stitching7: The availability of open APIs,
microservices, and developments around function-as-a-
service (FaaS) and serverless applications underline how
new-generation applications are moving towards collections
of connected services8. Over time, organizations often end
up with big suites of tools and systems (bespoke and off-
the shelf) from different vendors. This is usually the case
for global enterprises that have expanded and diversified
through both acquiring other companies and setting
up operations in new markets by building applications
quickly, without global IT growth strategies in mind. LC/NC
platforms enable rapid creation of pinpoint, domain-specific
applications, which, via connectors or building middle
layers, can be “stitched” together with legacy applications
to create end-to-end products. Businesses can use LC/NC
tools as tactical solutions to integrate different components
to “keep the lights on” while they decide if they need to
replace potential burning platforms in the long term.
Marketing
System A
CRM
Sales
Sales
Finance
System B Third-party system
ERP module 1
Supply chain management
Distribute ERP module 2
ERP module 3
Inventory
Third-party services
System 3
Help desk
Customer support
Help desk
Legacy New (LC/NC) Connector
•T
echnical savvy: Although LC/NC solutions make it
possible for non-technical people to build applications, there
could still be barriers to entry from a technical point of view.
Aspiring users of LC/NC solutions need to at least know
how to operate the tool itself, as well as be aware of some
“technical” concepts, such as APIs and databases. For the
fully customizable LC/NC options, some code will still need
to be written, possibly within the LC/NC tool itself – even if
they are basic requirements such as bits of Javascript, CSS
and simple SQL queries. Employees need to have the basic
technical skills to use the tools, or be able to acquire them,
potentially with some light support from the IT team.
•L
ock-in: All LC/NC development platforms result in lock-
in, unlike conventional application platforms. For example,
you can’t take an app created using Google App Maker and
transfer it into Microsoft PowerApps without rewriting the
entire application. Some platforms, such as Camunda, allow
you to port your application to a different cloud, but not
generally to a different tool. Note that vendor lock-in does
not have the same perfidious risk of the old days, when
there was complete dependency and prices were constantly
increasing. Healthy competition between vendors helps
drive both innovative new features and functionality on LC/
NC platforms, while keeping prices down (and, indeed,
reducing year on year). In our view, this is an acceptable risk
as long as the competitive differentiation enabled by the app
is low.
•C
onstrained performance: LC/NC development
tools decrease the amount of time needed to build an
application. However, the applications that result from LC/
NC development are rarely optimized for performance and
efficiency due to the abstract, declarative nature of LC/
NC solutions. Simply put, if you need an app that runs as
quickly as possible and consumes the fewest resources,
you will have to write bespoke code and go as close to the
silicone as you can. However, this does not mean “low” or
sluggish performance – this constrained performance refers
to low parallelism, rather than an unpleasant experience.
Most day-to-day users won’t care or even notice that the
platform showing a well-designed and well-thought-out
business dashboard is consuming, for example, 10 percent
more memory and 5 percent more CPU power than a non-
LC/NC equivalent. LC/NC platforms will thus do very well,
and modern platforms can scale to millions of users with
reasonable requirements if executed correctly.
Experience Layer
User interfaces can be built directly by business users to create the best
user experience – and allow for quick iteration
Logic Layer
Business logic can be built purely with LC/NC tools. This helps reduce communication overheads
between business and developers as business users know their required business logic best
The system API layer will hide the complexity away from
users further upstream. Developers and technical resources
with intimate knowledge of databases, servers and other
important components will be responsible for this layer. The
team responsible for building and maintaining the system API
layer will also have the tools necessary to safeguard critical
systems from improper use of applications further upstream.
Unleashing innovation using low code/no code 70/71
Prism / 1 / 2020
Greg Smith
is a Partner in Arthur D. Little’s London office and a member
of the Digital Problem Solving Practice.
Michael Papadopoulos
is a Chief Architect in Arthur D. Little’s London office and a
member of the Digital Problem Solving Practice.
Joshua Sanz
is a Manager in Arthur D. Little’s London office and a
member of the Digital Problem Solving Practice.
Michael Grech
is a Manager in Arthur D. Little’s London office and a
member of the Digital Problem Solving Practice.
Heather Norris
is a Consultant in Arthur D. Little’s London office and a
member of the Digital Problem Solving Practice.