Low-code Development Has Entered a Maturity Spurt
Closing the gap between the applications and services a company needs — and the ones they can actually produce — has long been a missing keystone for attaining digital transformation.
For increasingly software-driven organizations, the speed by which developers produce the needed processes, data flows, and business transactions has been much too slow for much too long. Fast-forward to the pressing new requirements of pervasively digital business in 2022, and it’s abundantly clear that something has to change.
Stay with us now as BriefingsDirect explores the latest capabilities and burgeoning strengths of Low-Code software development. To learn how the current maturity of Low-Code development will revolutionize the delivery of essential business applications, please join Matt Calkins, Founder and CEO of Appian in Reston, VA. The interview is moderated by Dana Gardner, Principal Analyst at Interarbor Solutions.
Here are some excerpts:
Gardner: Matt, in a nutshell, what is Low Code, and why is this a great time for it to revolutionize digital business?
Calkins: Low Code is a new way to build applications and processes. Instead of using code, drawing your code line by line, you make a picture. You draw a flowchart with lines, boxes, and arrows — with a start node and an end node — and that becomes your program.
Instead of thinking of a program, it’s now like a series of characters and instructions. At its essence, it’s a drawing. That’s a very human way to program and to envision a process. It’s a very human way — and it’s empowering to people because it’s intuitive to all of us. It’s also a lot faster. And this is the key advantage of low code. When you do less coding, you move faster.
Now a person can describe a new process by drawing a flowchart — maybe 10 times as fast, even 20 times as fast, as they could have described the same process using lines of code. When you put that kind of power of speed in the hands of a person, they can develop a lot more software. They can not only develop it, but they can also go back and change it periodically to keep up with the times. It allows far greater flexibility in the way your organization behaves as expressed through software.
Gardner: What is it about the maturity of Low Code now that has more people excited about using it?
Speeding the inevitability of change
Calkins: Low Code is about speed, and speed is helpful because it helps you keep up with change. There’s never been a time that there’s been so much change to keep up with. In the last few years, change has gone from being a nice-to-have to being a must-have.
In the pandemic, every organization had to change to survive, to keep up with the way their customers wanted to do business, the way their employees wanted to work, the locations from which they wanted to work, and to keep up with regulations.
We’ve been talking about change and digital transformation for years, but it’s never been so imperative as in the last few years. We’ve now reached a turning point where change is no longer an option. It’s a necessity. The speed of Low Code allows you to change — and change is what we’re all about at Appian.
Gardner: So, what can make software development more of a wind in your sail rather than an obstacle to overcome?
Calkins: Software has been too difficult to create — and to change. Someday we’re going to look back on this period of history and be amazed at how hard we made it on ourselves to program our machines. And how difficult it was to change the behavior of our organizations, because, of course, our behavior is written in software. We’re going to look back and think it’s astonishing that our software was the most immutable thing about our organizations. It’s harder to change than our building, our logo, or our management. Anything could be changed more easily than our software.
That makes no sense to me, because software is ideas, and it should be easy to change them. But the way we’ve created code is so difficult. This structured language with which we instruct machines, it is so complicated, it is so inscrutable. If you didn’t write it, it’s hard to know what the person who did write it was thinking.
It remains very difficult to create and to change our applications. This has got to change. We know we need more software — and we’re not getting more developers. So, one way or another, we need a faster way to create and change our software.
Low Code is such a way because it makes it intuitive. You’re drawing, you’re dragging and dropping boxes and arrows; it’s very human-like in the way we’re communicating. It’s the last link in a long chain of advancements in the ease by which people instruct their machines. Starting with Ada Lovelace programming the Babbage machine, and all the way up to the present day, we have kept making it easier to program our computers.
Low Code is just one more step in that direction. It’s not a finished step, we keep trying to make Low Code more intuitive, using more wizards, more drag-and-drop, and minimizing the need for anything that looks like code. We keep working on that, and now we understand the urgency between the global demand for new processes or software and the urgency of change in the pandemic era. We have every reason to be as fast as possible in the way we provide change to our customers.
Gardner: I suppose another difficulty has been the communication of requirements from those who are in the trenches, so to speak, to those who are doing the software development. Is there something about Low Code too that helps understand what the business is doing? Is there a benefit not only in the coding, but also in the communication?
Calkins: Yes, absolutely, there is. If you or I were to look at a Low-Code application, we would understand the main structure of how it works. We would understand the flow because it is a flowchart.
By making it understandable to everybody, even the ones who didn’t program it, we’ve democratized the meaning of a program. We’ve made it easier to create that program, but also easier to understand it and therefore, to validate it, to look at it and think that’s not exactly the way I believe it should work. If I’m in the trenches, you may have written it, but I’m looking at it and I know that it’s not right.
That’s a higher degree of common knowledge that will help us be on the same page, write better software, and pivot our organizations more quickly to match the needs that only our people in the trenches, as you say, know that we have.
Gardner: You mentioned earlier, Matt, that we’re having a hard time finding developers. Seems like we’re having a hard time finding all sorts of skills and labor, but development seems near the top. If we have a finite set of resources, but we have growing demand for software, how do we reconcile these two realities?
Calkins: We’re just going to have to get better at creating applications more cheaply and with less time. Because we can’t continue these two curves; they’re diverging, and we need way more software and we’re not getting way more developers.
And for that matter, the cost of a developer we can get is very expensive. So, we need to be more efficient and get more applications per developer, per year. So, if it’s not Low Code, it’s going to have to be something very much like Low Code, a more human, intuitive, and faster way to express our instructions to a machine.
Another way you do this, of course, is to democratize programming to the point where not everybody who does it has to be a “developer,” maybe we could take somebody who’s a power user and bring them in and make them a programmer.
Maybe we could create a programming language, a Low-Code programming language, that is easy enough so a fairly technical person could spend a month and become a productive professional developer in this medium. That’s what we’re going for. We want to democratize access to programming so that more people become developers — and developers become far more efficient.
Pioneers in democratizing programming
Gardner: What is it about Appian’s legacy that puts you in a position to be helpful in all of this? What is it about what Appian brings to the table that helps make this transformation?
Calkins: We’ve been focused on this for a long time. For about 15 years, we’ve been on this exact issue. How do you create a program by drawing a picture? I encountered that idea nearly 20 years ago, loved the concept, felt it was necessary.
The way the world was going — more software, not more programmers — I realized we’re going to need something like that. So, we have been working on it for more than a decade and a half. We were the first Low-Code company to go public in 2017. We’ve been pioneering this space; we’re not the only pioneer, but we’re definitely one of them.
We’ve put a lot of thought into this, and our entire business is focused on just this: Empowering people to create their processes. And so, we’ve a lot to add. We’re setting the standards. We’re creating the new shape of the market. We’re introducing the new nomenclature.
Low Code wasn’t a big thing when we decided that that was the right term. We went public with “Low Code” as our headline, and a lot of people thought, “Oh, you shouldn’t do that. You should always go public with a very famous well-known market.” But we were first. And now, it’s a much bigger deal.
Gardner: I’ve been curious over the years as to why, as software become more sophisticated – with computer aided design (CAD), engineering, and media and video production, and the design of homes and buildings – that it seems like developers put all their emphasis into automating the business tasks of others. Have they been too busy to automate what they were doing? Do the cobblers’ children have no shoes? Why has the development of software for the development of software lagged?
Calkins: You know, it’s funny. You’re right on this dichotomy. You could think of the advances in software as being of two types. There’s the sheer power inside the software application. And then there’s the connection from the user to the application. And, of course, according to Moore’s Law, the processing power is increasing all the time.
We have so much more power to work with. It’s incredible what these programs can do. But the interface hasn’t advanced as much, has it? The connection between a human and the machine is not advancing, not according to the pace of Moore’s Law.
Sometimes it seems pretty backward. It seems like we ought to be able to do better in facilitating human-to-machine collaboration and instruction. And at Appian, that’s what we’re all about. You can’t just surf the advances in the latest chip technology. You have got to think about what would be more human and what would be more intuitive and empowering. That has to be a critical area of advancement as well.
Gardner: Well, the need for improvement is very clear. So, Matt, as an industry, where is Low Code going?
Low Code with a purpose
Calkins: Low Code is in the midst of a dramatic change. Like all industries that reach maturity, it has to change at some point from focusing on what it does to focusing on what it’s for. So far, the Low-Code industry is focused on what it does, and you can see that in the name Low Code even. That’s what it does. It gives you an interface to create a program with less code, that’s Low Code.
We need to make it easier to conceive of a new process, design it, deploy it, run it, and change it — end to end.
What it doesn’t address is what it’s for, and what it’s for has changed. This industry is now about providing the ability to bring change to our customers. Our customers want to create a new behavior, and these days behavior is done in software. You’re going to create a new process.
We therefore need to make it easy for a customer to conceive of that new process, design it, deploy it, run it, and change it — everything about it, end-to-end. We are going to be a change engine that allows them to create — and do everything — with a new process.
That’s the emerging mission for our industry. We can’t afford any longer to be about the technology. We must be about the effect of the technology.
Gardner: Matt, can we unpack this for two different constituencies? One would be the business leader, so they understand what you’re getting at. But also the technologists, the IT people and developers. What does this mean for businesses, and what does this mean for technologists?
Calkins: First, it means that business and technology are going to be using the same product. Instead of having a product for business, a product for technology, and yet another product later on — we need a unified suite. We need a change engine that gets you from discovering your new process to designing your new process to automating and deploying your new process. The business will be involved in this largely in the discovery phase and the return on investment (ROI) phase.
And then, the technologists and the developers are involved in the design, deployment, and automation. It’s going to be one platform, a single product with a single stock keeping unit (SKU) getting you from the beginning to the end on a new process as fast as possible. By bringing all these people together via a common language and common interface, we make it so much easier for businesses to change. And if you don’t think this is necessary, just consider how much difficulty businesses have today with changing fast enough.
They’re always behind the times, always behaving a little too slowly, always reacting to new ideas slower than they should; always, like you said, having their aspirations unmet and their backlog too big. Businesses need to move faster. They need change. And so, we’re providing a change engine to facilitate that most fundamental want in every business I’ve seen.
Gardner: Another trend I’ve noticed over the years, Matt, is that in development, we go through a pendulum swing between centralization and decentralization. On one end there are a lot of different new tools, better testing environments, and yet a lack of integration between them all. That gets too unwieldy, and we swing back to more centralized and integrated platforms.
Is that what’s happening with Low Code as well? Are we swinging in one direction or the other?
Calkins: You’re completely right about that pendulum. I’ve seen the same thing over the last few decades. And lately, the pendulum has swung pretty far toward the power of the largest stack vendors and the big technology vendors. They’ve become exceptionally powerful, pervasive, and irreplaceable in many organizations.
I believe that the pendulum, when it swings, is going to swing back in the other direction. It’s going back to best-of-breed because best-of-breed tends to have better products. It’s going to be very important for customers to get the speed of change that they want and the agility in the way they execute their plans.
Big tech is going to be a straitjacket to achieving that. So, they’re going to want freedom of choice. They’re going to want to be able to plug into whatever data sources they may have around the enterprise instead of having to move all the data to one location.
There’s going to be a swing back in that pendulum toward best-of-breed and freedom, and the natural idiosyncrasy that emerges in any large organization. You can’t put that in a straitjacket or a cookie cutter. They’re going to want to express their unique plans and their unique backgrounds.
Low Code is empowering because you can program quickly — and so you can change quickly. You can adapt to your unique organization and your own data from many different places.
Low Code is an empowerment tool in this way. It’s empowering because you can program quickly — and so you can change quickly. But it’s also empowering in that you can adapt to the unique organization that you already are. You can adapt to the fact that you have your data in 27 different places. Some of them are in the cloud, and some of them are on-premises. They’re in different formats. Some of them are databases that you haven’t touched in 20 years.
Your data is scattered, right? That’s a situation that demands freedom, and Low Code is very good at adapting to unique situations like that. So, Low Code is empowering in that it facilitates idiosyncrasy and it also is going to benefit from that swing away from centralization and toward best-of-breed and individual empowerment.
Gardner: When we look for the best-of-breed approach to things like process mining, Low Code, and democratization of skills, are there specific use cases that come to mind where this will be the most valuable the soonest? Is there a low-lying fruit, if you will, to where Low Code platforms will emerge so that the early adopters get the best, empowering results?
Behavioral change in software
Calkins: Every organization of scale needs change, especially in the last few years, because change has become such a norm. Every organization is going to need to make changes.
Imagine a new regulation. Imagine entering a new business. Imagine launching a new product. Imagine having your customers expect something different from you and needing to change your behavior to adapt to that. Imagine your employees saying that they want to work in a new way from a new location, in a new pattern, and on different hours. All of these things require new behaviors. And when you adopt a behavior at scale in an organization, you are always facilitating it with software. So, every change an organization needs to make now is a change that is written or drawn in software.
For example, we recently helped a large financial institution, maybe the most famous financial institution in the world. They were launching a new product, entering a new market. They needed new behaviors and they realized they couldn’t code it fast enough, so they turned to us.
They used our Low-Code platform to program the new behaviors, the new case management that they required to launch this product, and then they were able to launch on time. It was successful. Every time they have to make a new launch or adjustment or behavior around this product, they can come right back to this platform and write some new processes and it’s as easy as drawing.
It’s Low Code, very simple. It’s become a major part of the way they do business. They’ve relied on Low Code to enable their agility — and every large organization is facing the same situation. They need to be agile. They’re looking for a means to change quickly and Low Code can be that.
Gardner: Matt, are there any misconceptions that you find in the field about Low Code? Perhaps it’s time to better understand the reality. It sounds like from that last example that there are some people who might not be understanding the benefits.
Calkins: The biggest misconception about Low Code is that it isn’t powerful. It’s simple and so, people assume that it’s a toy. But it’s anything but. In fact, it is as powerful as a development language. It’s in use today by the largest organizations in the world to create some of the most important processes that they run, processes that are a matter of law or a matter of satisfying the customer that addresses the core workflows in an organization. Low Code is used for some of the world’s most important processes today, and so, that’s the number one misconception.
The next misconception is that it’s hard to get into. Low Code in fact is exceptionally simple to get into. In fact, you could log on to Appian’s website and learn right there. We have videos, there’s a training course, there’s a free environment that you can use. We’re making it as easy as possible to learn Low Code, make that part of your skill set and make use of it. So, Low Code is actually easy to get into and very powerful, but not everyone realizes it.
Gardner: How do traditional software developers feel about Low Code? How do they react to it?
Calkins: Well, some of them dive right in and realize that it’s very empowering. Others are very attached to a programming language that they’ve used in the past and preferred to stick with it. I see all kinds of reactions.
Low Code is simple so people assume it’s a toy. But it’s anything but, it’s as powerful as a development language. And it’s used for some of the most important processes today.
But to those on the edge of programming, let’s say they’re starting a career. They’re in their 20s, they’re learning their place in the world of development and this Low Code tool comes along. Well, they love it, they love it. Those who are getting going with their careers see this as an unqualified positive — and they enthusiastically get involved.
It’s true, the wages are very high right now, salaries are high for people who know how to do this. There’s a shortage of Low-Code developers. The people who know how to do this are commanding a lot of money and influence in the market. So, I see Low Code as a great tool for those who are finding their way into the development field.
Gardner: If you’re a chief technology officer (CTO), a chief executive officer (CEO), or on the board, if you’re a chief information officer (CIO), how does Appian help you in your role and your company?
Empowered processes and partners
Calkins: If you’re an executive at a big organization, you have to ask yourself, “Are we changing fast enough?” Almost certainly, the answer is going to be, “No.” Seriously think about that. Don’t measure yourself against what you thought was possible. Measure yourself against what your customers would like.
Are we moving as fast as our customers wish we were moving? Are we introducing new products? Are we changing our behavior? Are we as responsive as, ideally, we could be? There’s almost no business I know of that could say yes to that question.
If it’s true that you would like to move faster, now is your chance. There’s now such a thing as a Low-Code suite that can take you from discovering a new process, to designing it, and automating it in the same product. You can increase the rate at which you launch a new process by 10x or 20x.
So, an executive can ask these questions and then direct the organization to look into Low Code. Whether you’re on the board, the CEO, the CTO, or the CIO, the direction would be the same. Ask that question and then talk to some Low-Code vendors.
Gardner: How about the ecosystem that’s around you? It seems like over the years, there have been consultancies that have developed within vertical industries and focus on solutions. It seems to me that Low Code would be very important and of interest to them. They’re not interested in selling software; they’re interested in creating solutions in vertical industries. What is your partner ecosystem like?
Calkins: There’s been a lot of enthusiasm. If you have expertise in one vertical industry and you want to bring that expertise to value by instantiating it. Well, there’s no better way to instantiate it than in a Low-Code framework. It’s so easy to deploy and adjust. Every client you have is going to want a variation on your expertise, but the core expertise can be expressed and then modified to fit each circumstance so quickly in Low Code.
Instead of selling your time on an hourly basis, you’re selling your ideas and they’re reproducible. This is a critical pivot where you go from selling the minutes to selling the ideas. This has been very enthusiastically adopted by people who are consultants and who have expertise in one industry or another.
Gardner: Matt, where should we expect the direction of Low Code productivity to go next?
See the process mining big picture
Calkins: Appian recently announced a major new product. We announced our process mining module, which we’ve been working on for a long time. We bought a company, and we’ve been developing it. We finally merged it all into our platform and Low-Code suite.
Process mining is like an x-ray giving you a view into what behaviors happen inside your enterprise. It looks at the usage logs of your applications, weaves them together to create a unified understanding of the sequences and the patterns of behaviors that happen whenever you launch a new use case of any kind.
Process mining is like an x-ray giving you a view into what behaviors happen inside your enterprise. It creates a unified understanding of behaviors.
So, after a customer calls, as an example of a use case, what do you do? If a problem happens in such a process, what sequence of actions do you then best pursue? Based on that process mining look — that x-ray into your actions — you can tell whether it’s too slow, you’re being inefficient, you’re spending too much money routing work to the wrong resource or keeping your customers waiting too long. This x-ray can tell you a lot about where you need to build a new process or improve your existing processes.
When you get that diagnostic, you can convert it. You can make a workflow based on what you learned. So, this is the natural starting point for the journey of process optimization. First, we take the x-ray, and we understand what’s inefficient and where we need to make an improvement. Then, we develop the new process. We use a Low-Code workflow interface to drag and drop the right process — and then we automate it.
You start with discovery, go to design, and then you go to automation — and it’s on the same product. I think it’s a big step. It’s going to be a great way to measure ROI. It’s going to be a great way to find new places to use Low Code. And it will be well in demand by our partners because they’re going to enjoy deploying their expertise to discover new places where they could be of use.
Gardner: The timing is very auspicious in that processes are now distributed across multiple organizations. As we’ve gone to cloud-native services and using third parties as software as a service (SaaS) services for so much, it’s hard to grasp the whole process. They are not necessarily inside your four walls, and probably never will be again. Is there something about process mining that helps ameliorate this complexity of a distributed business?
Calkins: Yes. Process mining looks at all the usage logs and brings them together. That’s the magic of the technology. So, whereas we used to see only an aspect of the business and one dimension of our behavior at a time, now we see all of it. Just like if you’re going from a 2D view to a 3D view, things start popping out at you. It becomes much clearer about what could be improved and where the inefficiencies lie. It’s a great clarification tool.
Gardner: It sounds like that’s something we could dive deeper into at some point and it’s very interesting. Any other ways that people can learn more if they’re intrigued about Low Code? What do you advise them in terms of making this move from a lesson into an engagement?
Calkins: We’re so eager to make it easy to learn Low Code. We’re building our community as fast as we can. We have free resources, free environments to use, a great program to get you involved, a forum where you can post your work and learn from other people’s work. Just go to Appian.com or lowcode.com and avail yourself of all these resources. It’s a booming industry.
By Dana Gardner
The ‘Cloud Syndicate’ is a mix of short term guest contributors, curated resources and syndication partners covering a variety of interesting technology related topics. Contact us for syndication details on how to connect your technology article or news feed to our syndication network.