What is a citizen developer?
A citizen developer is an employee outside the engineering team who builds real working software: an ops manager who builds an approvals form, a sales lead who builds a lead-routing tool. Gartner coined the label. The hard part arrives after launch, when someone has to own and maintain what got built.
What is a citizen developer?
A citizen developer is an employee in ops, sales, finance or support who builds working software without sitting in the engineering org. Gartner's wording is deliberately loose: an employee who creates application capabilities for themselves or others, using tools that are not actively forbidden by IT or business units. Persona, not job title. Nobody gets hired as one.
What they are allowed to build
The limit is usually drawn around data, not difficulty. A working program gives people an approved list of platforms, access to a copy of records rather than the live system, and a review before anything touches money or personal data. Skill level is lower than most people assume: in a QuickBase study of business users, 8% had traditional coding skills while 68% already counted app building as part of the job.
Who owns it after launch
Citizen development and shadow IT are the same activity with different paperwork. The difference is a sanctioned tool list and someone reviewing the result. The complaint engineers repeat on Hacker News is the handoff: users build, IT maintains, and the approvals form running a payroll step lands on them with no tests, no documentation, and the builder gone. Gartner expects citizen developers at large enterprises to outnumber professional developers 4 to 1 by 2026, so that pile grows.
Build it yourself when the tool touches only your own team's data and a week of manual work would cover a failure. Anything touching customer records, money, or another team's process needs a named owner and a sign-off from IT before the build, not after the break.
Last updated: Sep 5, 2026