CLEVR, a company that assists enterprises with digital transitions with Mendix low-code and no-code (LCNC) development solutions, recently announced the findings of a survey that reveals a high number of executives from North America have not yet heard about low-code and no-code software development. Specifically, CLEVR found that 27 percent of the C-suite executives from North America surveyed were unaware of the low-code and no-code development.
Not only is the level of knowledge about LCNC technology low in C-suite executives, but it was also low with regard to North American chief technology officers (CTO), who are typically the most tech-savvy people within an organization. Of the CTOs surveyed in North America, 38 percent admitted to not knowing anything about LCNC. This result was in strong contrast with their European counterparts. Only 24 percent of CTOs based in Europe were unfamiliar with this technology.
Gartner predicts that by 2024, 75 percent of large enterprises will use at least four low-code development tools for IT and citizen development initiatives. According to CLEVR’s study, 78 percent of the C-level executives that indicated they were aware of the LCNC trend confirmed that they are now using some form of LCNC development tools within their organizations. Additionally, those who responded that are currently using LCNC tools were asked to list the top five reasons why, which include:
In a media statement, Angelique Schouten, CEO of CLEVR, said, “the environment feels a little like when cloud technology was beginning to take off and many businesses thought it was the same thing as iCloud or Dropbox. They had no understanding of the kind of impact it would have on their organizations. Back then, there was little understanding of the cloud’s power and what it could bring to larger organizations and start-ups alike. LCNC is on the same track. Only through better understanding of LCNC can leaders extract all the value the technology has to offer.”
To learn more about low-code development click here.
Transforming BPM to Process Automation