What is a Citizen Developer?

The term emerged as platforms like spreadsheet macros, workflow builders, and drag-and-drop app makers matured enough that people in operations, marketing, or finance could assemble working tools without waiting on an engineering backlog. A citizen developer typically works inside guardrails set by IT — approved connectors, governed templates, and review processes — rather than writing raw code against production systems. The appeal is speed: a process owner who deeply understands a workflow's edge cases can prototype and ship a fix in an afternoon instead of filing a ticket and waiting weeks. The risk is sprawl — unreviewed automations that touch sensitive data, duplicate logic across teams, or break silently when an underlying API changes, with no engineer accountable for maintaining them. Organizations that do this well pair citizen development with a lightweight governance layer: a shared catalog of what's been built, basic security review for anything touching customer data, and a path to hand a tool to engineering once it becomes business-critical.