Citizen developer

What is a citizen developer?

A citizen developer is someone outside a traditional software role who builds business apps and automations with approved low-code or no-code tools. The research firm Gartner, which popularised the term, describes a citizen developer as a user who creates applications for others using development and runtime environments sanctioned by IT. They usually report to a business function such as operations, finance, or sales, not to the IT department.

Citizen developer is a role, not a job title that grants technical authority on its own. A finance clerk might build an app for expense requests and still be an ordinary user of other systems. The role only works well inside agreements on data, security, testing, ownership, and support. Low-code lowers the technical barrier, but a business app is still software with consequences for other people.

What a citizen developer builds

Typical solutions built on tools like the Microsoft Power Platform are a Power Apps app for on-site registration, a Power Automate flow for document approval, or a simple dashboard for a team process. They usually solve a bounded problem that used to run on email and spreadsheets.

A maker can also build a prototype that helps the team sharpen what it actually needs. If the solution turns out to be business-critical, complex, or widely used, a professional development team can take it over or extend it. Not every problem fits citizen development: public products, heavy integrations, sensitive decision logic, and apps with high scale or availability demands need technical and architectural guidance early.

A worked example

A safety officer wants to record workplace inspections digitally. That person knows the questions, the exceptions, and the follow-up better than the central IT team does. With Power Apps they build a form for tablet and phone.

A flow automatically creates a task and alerts the person responsible when there is a serious defect. The data lands in Dataverse with roles for inspectors and managers. Before go-live, a platform team reviews the data model, access rights, error handling, and the path to production, and a professional developer builds a reusable component for offline photos. The safety officer stays owner of the process content. This is collaboration, not a handover of all IT responsibility to the business.

Citizen developer versus end user and professional developer

An end user works with a solution and may change some configuration, but does not necessarily build application logic. A citizen developer makes components that other people also use. Citizen development is the app-and-automation cousin of self-service analytics, where business users build their own reports and dashboards instead of applications.

A professional developer works daily with software architecture, code, tests, integrations, and operations. That expertise stays necessary for extensions, technical risk, and shared platform building blocks. The line is not absolute: a maker can grow technical skill, and a developer can use low-code. Split the work by risk and complexity, not by the prestige of a tool.

Guardrails and training

An organisation gives makers a clear starting point: approved environments, a connector policy, naming, templates, and a route to production. Training covers more than the designer surface; it also teaches data modelling, access rights, privacy, and error handling.

A risk classification decides which solutions can be built independently and which need review. A personal reminder flow needs less oversight than an app that processes payroll or health data. A maker community and a set of champions help with recurring questions, while a Center of Excellence maintains the guidelines, the inventory, and reusable components. Guardrails should make the safe path the easy one, not only punish mistakes after the fact.

Ownership and lifecycle

Every shared solution needs a process owner, a technical owner, and a support route. Write down who looks at errors and what happens when the original maker changes jobs.

Use separate development, test, and production environments for solutions with business impact. Solutions, source control, and pipelines make changes reproducible; test with real user roles and exceptions. Track usage, errors, orphaned resources, and value. An unused app does not have to be maintained forever. Citizen development stays healthy when building, running, and retiring are all normal parts of the process.