Citizen Development: DIY Applications Without Writing Code

A buzzword I have recently come across is “Citizen Development”. Citizen development is a practice that lets individuals without formal software development training build applications, often with little or no involvement from IT. In simpler terms, it is “do-it-yourself” IT for the workplace.

What Is Citizen Development

At its core, citizen development allows individuals, often called citizen developers, to create applications using low-code (LC) or no-code (NC) platforms. These platforms typically offer user-friendly visual interfaces, drag-and-drop components, and pre-built templates. The idea is to let people quickly solve their own problems, rather than wait for IT to prioritize and deliver a solution. It is like LEGO for application development.

This approach helps bridge the technology skills gap, where the demand for digital tools exceeds the supply of professional developers. When people with business knowledge (and some elbow grease) can build their own solutions, organizations become more agile and reduce the burden on IT teams.

Unlike traditional software development, which often requires coding expertise and lengthy timelines, LC/NC platforms allow users to create tools for data entry, workflow automation, and reporting. Many applications can be customized primarily through settings and visual components rather than traditional programming. This flexibility enables users to iterate faster and take ownership of their solutions, improving productivity and engagement.

Some popular LC/NC tools include Microsoft Power Platform and Airtable. I have used both Microsoft Power Apps and Power Automate in several projects as well as Airtable to build a static site contact form for this website.

New Term, Old Concept

While the term “citizen development” may be new (add it to the buzzword bingo card), the concept is not. Anyone who has worked in IT for years has seen many of these ideas return in new forms. They often come with a fresh label but carry the same underlying goal: enabling business users to build their own tools without relying on developers. A few examples are noted here, though this is simply my perspective and not an exhaustive list or accurate timeline.

Even before LC/NC tools existed, platforms like Microsoft Excel offered automation through macros. A user could record a series of steps and automate repetitive tasks using Excel Macro Language (XLM) and later Visual Basic for Applications (VBA). This allowed non-programmers to process data or format reports, although modifying the macro often required some coding knowledge and the macros were not easily scalable.

The trend continued with visual, drag-and-drop development environments like Visual Basic, which let users build desktop application interfaces without hand-coding every element, though adding functionality to those components still required programming skills.

Then came WYSIWYG HTML editors like Microsoft FrontPage and Adobe Dreamweaver, which allowed users to build web pages through visual interfaces. These tools made web development more accessible, but they still had limitations on what could be created without writing code. Additionally, the underlying code they generated was often bloated and non-standard, making it difficult to maintain.

Business Process Management (BPM) platforms followed, with visual workflow builders designed to let business users automate approval processes and other operations. In practice, simple flows were easy to configure, but anything beyond basic tasks often required IT support.

Later, Web Content Management Systems (WCMS) like WordPress, Wix, and Squarespace made it possible for anyone to launch a website without coding. Users could select a theme, enter content, and publish. However, as I have experienced firsthand with WordPress, deeper customization often required coding and sometimes more effort than coding from scratch.

Today’s LC/NC platforms are simply the next step in this long evolution, offering more power and flexibility than ever before.

Challenges of Citizen Development

While citizen development offers major benefits such as faster delivery, increased agility, and reduced IT workload, it also introduces risks that must be managed. Without oversight, user-built applications can create security vulnerabilities, compliance issues, and integration problems.

Anybody Can Do IT, but Can They Do IT Well?

Because computers are everywhere, there is this common misconception that “anybody can do computers” (yes, someone actually said that to me). But owning a laptop and using a browser and Microsoft Office does not make a user ready to build business systems. I own a hammer, but nobody should hire me to build a house.

Consider a department that builds a Power Apps intake form to collect customer requests. It works well until someone asks how long the data is retained, who can access it, or whether it satisfies a recent compliance requirement. Because the application was never reviewed by IT, none of that has been documented.

By definition, citizen developers are not trained software engineers. While their business expertise is valuable, they may lack the technical knowledge to build applications that are secure, scalable, and maintainable. As applications grow, performance can degrade if scalability was not contemplated as part of the design. Long-term maintenance also becomes difficult if the original creator leaves and the application lacks documentation or standard design practices, such as a written description of what the application does, who depends on it, and how its data is structured.

Platform dependency introduces its own risk. If an LC/NC vendor changes pricing, discontinues a feature, or shuts down entirely, applications built on that platform may need to be rebuilt on short notice, regardless of how well they were designed.

Without development standards, applications may vary widely in appearance, usability, and functionality, leading to confusion and redundancy. This inconsistency reduces overall efficiency and makes system integration harder.

From a security perspective, non-technical users may overlook critical practices such as access controls, data encryption, system patching, and secure authentication. These gaps can expose the organization to data breaches and unauthorized access.

From a compliance standpoint, user-created applications may fail to meet internal policies or external regulations such as GDPR or, where applicable, HIPAA, as well as industry-specific standards. For example, collecting customer data without a valid legal basis, appropriate safeguards, or proper audit trails could result in legal penalties or reputational damage.

Another growing concern is shadow IT, where applications are created and used outside of IT’s knowledge or control. While often well-intentioned, shadow IT solutions can bypass security policies, create data silos, and complicate enterprise architecture. They may also duplicate existing systems, leading to unnecessary overhead and confusion. Shadow IT applications are often discovered only after an incident, an audit, or the departure of the employee who built them, at which point identifying who owns the data and whether it meets compliance requirements can be difficult.

Managing Citizen Development

Organizations that adopt citizen development successfully typically pair it with lightweight governance rather than leaving it unmanaged. Common practices include a sanctioned list of approved LC/NC platforms, a security review before an application touches production data, required documentation for anything beyond personal use, and a clear escalation path when an application outgrows what a citizen developer can safely maintain. A center of excellence, a small IT team dedicated to supporting and reviewing citizen-built applications, is one common structure for this.

Replacement for IT?

Will citizen development replace traditional IT? No, but the relationship may evolve as business users adopt a more digital mindset. LC/NC platforms are typically used to build simple applications and basic automated workflows, making them well-suited for creating small, task-specific tools. IT remains essential for developing and maintaining complex systems, managing infrastructure, enforcing security and compliance, and ensuring scalability and integration. IT will also continue to establish and govern the foundational platforms that citizen developers build upon.

AI-assisted coding tools are extending this trend further, letting people describe an application in plain language and generate working code from it. The line between citizen development and traditional development may blur further as a result, though the underlying tradeoffs of security, scalability, and maintainability remain the same.

Summary

Citizen development is reshaping how organizations build and deliver digital tools. With thoughtful implementation, it increases employee autonomy, accelerates innovation, and reduces dependency on IT. But success requires strong governance, proper training, and ongoing collaboration between business users and IT teams.