Skip to content

2026 05 14 citizen development rollout empirical evidence

Jump to bottom
github-actions[bot] edited this page May 15, 2026 · 1 revision

Empirical evidence on rollout of organisation-wide low-code and no-code programs

Research Question

What does peer-reviewed and independently verified empirical evidence reveal about the outcomes, success factors, governance models, and failure modes of organisation-wide low-code or no-code (LCNC) programs that let non-Information Technology (IT) business staff build applications, often called citizen development?

Scope

In scope:

  • Peer-reviewed studies and independently conducted empirical research, including surveys, case studies, interview studies, and longitudinal analyses, on organisation-wide LCNC programs
  • Quantitative and qualitative outcome measures, including time-to-delivery, local productivity, software quality, user satisfaction, relationship with central IT, and risk from business-built tools operating outside formal IT visibility and control
  • Success factors identified across multiple independent studies
  • Failure modes and documented risks in LCNC rollout programs
  • Governance structures and their relationship to rollout outcomes
  • Challenges in moving from pilot efforts to organisation-wide rollout
  • Industry surveys with disclosed methodology when they materially sharpen the academic evidence

Out of scope:

  • Vendor marketing materials or case studies without independent verification
  • General low-code or no-code platform performance benchmarks not tied to rollout programs
  • Theoretical frameworks without empirical grounding
  • Application development methodology comparisons not focused on business-user builders

Constraints:

  • Prefer peer-reviewed or independently verified studies over vendor-produced content
  • Every source listed must include a verifiable URL
  • No specific time-horizon restriction, but flag recency risk on fast-moving findings

Context

[fact; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] Digital.gov defines citizen developers as non-technical employees enabled to create local automations, and the 2025 Journal of Systems and Software review describes LCNC as extending software creation beyond professional engineers to broader organisational participants. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890] The practical decision is whether an organisation can move from scattered local experimentation to a rollout model that preserves speed while keeping software quality, security, compliance, and accountability inside a workable business-IT operating model.

Approach

  1. Identify peer-reviewed and independently conducted studies that specifically examine LCNC rollout programs and describe outcomes. 1a. What quantitative outcomes, such as productivity gains, application quality, or time-to-delivery, have been measured across studies? 1b. What qualitative outcomes, such as user satisfaction, IT relationship, or governance strain, have been reported?
  2. Synthesize the success factors identified empirically across rollout studies, focusing on preconditions and operating practices associated with better outcomes.
  3. Document failure modes and risks that have been empirically observed, including what causes programs to stall, create tools outside formal IT visibility, or generate unsustainable technical debt.
  4. Examine how governance models differ between studied implementations and what the evidence says about which approaches produce better outcomes.
  5. Assess the rollout evidence, focusing on the transition from pilot activity to organisation-wide scale and the barriers that appear at that transition.

Sources

Research Skill Output

(Full output from running the research skill, retained verbatim in the completed item. Sections 0-5 are the investigation, and section 6 seeds the Findings section below.)

§0 Initialise

  • Question: what does empirical evidence show about the outcomes, success factors, governance models, failure modes, and rollout barriers of organisation-wide LCNC programs that let non-IT staff build applications?
  • Scope: peer-reviewed and independently published empirical evidence on outcomes, adoption barriers, governance patterns, and the move from pilot work to scaled rollout, excluding vendor-only success stories and generic platform benchmarks.
  • Constraints: accessible multi-case studies, interview studies, literature reviews, and independently published practice guidance were prioritized; access-gated analyst reports and blocked seeded publisher pages were excluded from downstream claims.
  • [fact; source: https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html; https://davidamitchell.github.io/Research/research/2026-04-26-systems-capability-debt-citizen-development-empirical-evidence.html] Prior completed repository work already argued that governed operating models and systems-capability debt shape low-code outcomes, so this item tests those themes against the strongest accessible empirical rollout literature.
  • Output format: knowledge.

§1 Question Decomposition

  • Root question: What does empirical evidence show about the outcomes, governance requirements, and failure modes of organisation-wide LCNC rollout programs?
  • A. Evidence base and outcome profile
    • A1. Which peer-reviewed or independently verified studies directly examine rollout programs rather than only platform features?
    • A2. Which quantitative outcomes have actually been measured?
    • A3. Which qualitative outcomes are reported repeatedly across studies?
  • B. Success factors
    • B1. Which governance and operating-model choices recur in successful programs?
    • B2. Which training, support, and collaboration practices recur in successful programs?
  • C. Failure modes
    • C1. Which recurring risks appear across rollout studies?
    • C2. Are the main failure modes technical, organisational, or mixed?
  • D. Governance models
    • D1. What roles do central IT teams, platform experts, and business teams play?
    • D2. What controls define bounded autonomy for business-user builders?
  • E. Scale and transition
    • E1. What changes when a program moves from pilot activity to enterprise scale?
    • E2. What barriers block that transition?

§2 Investigation

Source access and replacement notes

  • Access note: the seeded Gartner and Forrester reports were access-gated in this session and were not used for downstream claims.
  • Access note: the seeded Sanchis publisher page returned 403 in this session, so the paper remains identified but not consulted.
  • Access note: the seeded Waszkowski paper was identifiable via direct identifier metadata, but no directly fetchable abstract page was available in this session, so the paper remains identified but not consulted.
  • [fact; source: https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://ortus.rtu.lv/science/en/publications/35615] The seeded Rokis and Kirikova link was stale, but accessible metadata pages confirmed the current Digital Object Identifier (DOI), abstract, and publication details for the 2022 literature review.

A. Evidence base and what it can support

  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://www.fernuni-hagen.de/bima/forschung/publikationen/MISQE2024_CitizenDevelopLCNC.shtml] Binzer et al. draw on insights from 24 companies that had embarked on citizen-driven LCNC journeys and frame the core strategic problem as making design choices that address security, compliance, and organisational change.
  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://portal.fis.tum.de/en/publications/governing-citizen-development-to-address-low-code-platform-challe/] Viljoen et al. base their governance guidance on 30 interviews with citizen developers and low-code platform experts.
  • [fact; source: https://hdl.handle.net/10125/108890] Binzer et al. report a multi-case study covering 18 firms and 22 interviewees and identify 20 measures grouped into five collaboration mechanisms for enterprise citizen-developer programs.
  • [fact; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] Ajimati et al. review 40 primary studies published between 2017 and 2023 on LCNC adoption and citizen development for digital transformation.
  • [fact; source: https://colab.ws/articles/10.1109%2Faccess.2023.3258539] Kass et al. use semi-structured interviews and a Delphi study with 17 experts to identify 12 drivers and 19 inhibitors for low-code adoption.
  • [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] The accessible empirical base is strongest on governance patterns, collaboration mechanisms, and observed challenges, and much weaker on large cross-firm outcome datasets with hard before-and-after metrics.

B. Outcomes reported across studies

  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://www.fernuni-hagen.de/bima/forschung/publikationen/MISQE2024_CitizenDevelopLCNC.shtml] The 24-company strategy study states that LCNC platforms let employees with little or no IT background quickly create digital solutions.
  • [fact; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] The 2025 Journal of Systems and Software review identifies lower entry barriers, acceleration of digital transformation, empowerment of non-developers, and innovation as recurring reported benefits across the 40 reviewed studies.
  • [fact; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] Digital.gov says programs should count qualitative benefits such as better automation opportunity identification, decreased error rates, improved quality, faster processes, and stronger workforce understanding of automation.
  • [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] The available evidence supports claims of faster local solution delivery and broader participation, but it does not yet provide a robust, comparable enterprise-scale effect size for productivity, quality, or backlog reduction.

C. Success factors and governance structures

  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://www.fernuni-hagen.de/bima/forschung/publikationen/MISQE2024_CitizenDevelopLCNC.shtml] Binzer et al. state that the success of citizen development requires addressing security, compliance, and organisational change through deliberate strategic design choices rather than only deploying the platform.
  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://portal.fis.tum.de/en/publications/governing-citizen-development-to-address-low-code-platform-challe/] Viljoen et al. emphasize the crucial roles of technical experts and platform-specific functionalities in governing citizen development and say this governance differs from conventional software-development governance.
  • [fact; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] Digital.gov recommends a centralized repository, extensive code review, role-based access controls, separate development, test, and production environments, leadership sponsorship, careful license allocation, and collaboration with chief information officer (CIO) and IT teams.
  • [fact; source: https://hdl.handle.net/10125/108890] The 18-firm collaboration study identifies self-empowerment, ideation generation, coordinated scaling, project execution, and professional catalyst as distinct mechanisms in enterprise citizen-developer programs.
  • [fact; source: https://link.springer.com/article/10.1007/s10257-022-00553-8] Fischer et al. structure Robotic Process Automation (RPA) implementation into three major phases, initialization, implementation, and scaling, after analyzing 35 project reports and refining the framework through expert interviews and workshops.
  • [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://link.springer.com/article/10.1007/s10257-022-00553-8] Durable rollout depends on combining business-user enablement with central intake, training, review, escalation, and lifecycle controls rather than giving makers unrestricted autonomy.

D. Failure modes and barriers

  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://portal.fis.tum.de/en/publications/governing-citizen-development-to-address-low-code-platform-challe/] Viljoen et al. identify substandard software quality, tools outside formal IT visibility, and technical debt as core risks when software development is entrusted to novices.
  • [fact; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/] The 2025 systematic review and the 2022 LCNC literature review both identify governance, security, complexity, and platform lock-in as recurring challenges.
  • [fact; source: https://colab.ws/articles/10.1109%2Faccess.2023.3258539] Kass et al. show that adoption drivers and inhibitors are context dependent even when experts agree on the most and least important factors, which means rollout barriers vary by organisational setting and cannot be solved with a single template.
  • [fact; source: https://link.springer.com/article/10.1007/s10257-022-00553-8] Fischer et al. report that expert knowledge is still needed to create reliable and scalable automations and cite prior work estimating that up to 50% of initial RPA implementations fail.
  • [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://colab.ws/articles/10.1109%2Faccess.2023.3258539; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://link.springer.com/article/10.1007/s10257-022-00553-8] The main rollout failures are mixed socio-technical failures that combine weak governance, unclear ownership, training gaps, and complexity boundaries that exceed maker capability.

E. Scale-up and transition from pilot to rollout

  • [fact; source: https://hdl.handle.net/10125/108890] The 18-firm collaboration study treats coordinated scaling and professional catalyst roles as separate mechanisms from self-empowerment, which indicates that enterprise rollout needs capabilities that are not required in small local experiments.
  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/3] The 24-company strategy study presents citizen development as a strategic design problem, which implies that rollout success depends on organisation-wide choices rather than on isolated tool adoption.
  • [fact; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://link.springer.com/article/10.1007/s10257-022-00553-8] Digital.gov and Fischer et al. both distinguish initial enablement from later structured rollout by emphasizing leadership support, standard protocols, separate environments, and explicit scaling phases.
  • [inference; source: https://hdl.handle.net/10125/108890; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://link.springer.com/article/10.1007/s10257-022-00553-8] Pilot success does not translate into organisation-wide success unless the program adds intake, triage, support, training, and escalation mechanisms that absorb rising coordination cost.

§3 Reasoning

  • [fact; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890] The strongest direct evidence supports claims about governance design, collaboration patterns, and failure modes because three recent multi-organisation empirical studies converge on those topics.
  • [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] Outcome claims are intentionally narrow because the accessible literature reports directionally positive delivery effects more often than standardized, cross-firm quantitative measurements.
  • [inference; source: https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] RPA evidence is used as an adjacent rollout analogue for governance and scaling, not as proof that LCNC and RPA programs have identical technical characteristics.
  • [assumption; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] Government and practice-guidance sources are used to sharpen rollout-control patterns only where they align with the academic evidence base. Justification: the academic literature alone is thinner on stage-gate rollout mechanics than on general governance themes.

§4 Consistency Check

  • [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] No consulted source contradicts the central pattern that rollout success depends on governance design, business-IT collaboration, and bounded autonomy rather than on platform deployment alone.
  • [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] The main unresolved tension is between widely reported speed and enablement benefits and the weak supply of hard enterprise-scale effect-size measurements, so this item treats quantitative upside as plausible but not precisely measured.
  • [fact; source: https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html; https://davidamitchell.github.io/Research/research/2026-04-26-systems-capability-debt-citizen-development-empirical-evidence.html] Cross-item check: related completed items strengthen the interpretation that rollout outcomes depend on organisational capability and control design, and they do not materially contradict the external empirical literature used here.

§5 Depth and Breadth Expansion

  • [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://colab.ws/articles/10.1109%2Faccess.2023.3258539; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] Technical lens: rollout risk rises when organisations let business-user builders cross from simple local solutions into integration-heavy or maintenance-heavy work without matching increases in review, support, and ownership.
  • [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://hdl.handle.net/10125/108890; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] Behavioural lens: successful programs create a collaboration system that makes IT support visible and legitimate, instead of framing central IT as an obstacle to business-user autonomy.
  • [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539] Economic lens: faster local delivery can be offset by governance, security, lock-in, and maintenance costs when organisations scale usage faster than they scale controls and support.
  • [inference; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://link.springer.com/article/10.1007/s10257-022-00553-8; https://davidamitchell.github.io/Research/research/2026-04-26-deployment-pipeline-citizen-development-governed-gate.html] Governance lens: the empirical rollout literature and the related repository item on governed deployment gates both point toward bounded autonomy, stage separation, and central review as more credible scaling patterns than unrestricted self-service.

§6 Synthesis

Executive summary:

Empirical evidence shows that organisation-wide LCNC programs can improve local delivery speed and broaden participation, but durable rollout depends on treating citizen development as a governed operating model rather than as a simple tooling rollout. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] Across the strongest accessible studies, the recurring success pattern is bounded maker autonomy supported by central standards, technical experts, collaboration mechanisms, training, review paths, and escalation for higher-complexity work. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] The recurring failure pattern is socio-technical: studies repeatedly describe substandard software quality, tools outside formal IT visibility, technical debt, security strain, and context-specific adoption barriers when governance and support lag behind growth. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539] Evidence for exact enterprise-scale performance gains remains thin, because the best accessible multi-organisation studies focus much more on governance design and collaboration mechanics than on standardized before-and-after outcome metrics. [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://hdl.handle.net/10125/108890]

Key findings:

  1. The strongest accessible empirical studies show that enterprise citizen-development programs succeed when organisations treat them as governed operating models, pairing maker enablement with central standards, technical support, and explicit design choices around security, compliance, and organisational change. ([inference]; high confidence; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890)
  2. The available evidence supports faster local solution delivery and broader participation by non-IT staff, but the literature does not yet provide a robust cross-study enterprise effect size for productivity, software quality, backlog reduction, or cost savings. ([inference]; medium confidence; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/)
  3. Recurring failure modes across the consulted studies include substandard software quality, tools outside formal IT visibility, technical debt, security and compliance strain, and adoption barriers whose severity depends on the surrounding organisational context rather than on the platform alone. ([inference]; high confidence; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539)
  4. Successful rollout models repeatedly combine business-user autonomy with structured collaboration mechanisms, including training, ideation intake, coordinated scaling, project execution support, professional catalyst roles, and central review or repository controls. ([inference]; high confidence; source: https://hdl.handle.net/10125/108890; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/)
  5. The best adjacent scale-up evidence indicates that pilot success does not generalize automatically, because enterprise rollout introduces coordination, review, and support burdens that require separate scaling phases and more expert involvement than early local experiments do. ([inference]; low confidence; source: https://hdl.handle.net/10125/108890; https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/)
  6. Taken together with prior completed repository items on governed low-code operating models and systems-capability debt, the empirical literature supports reading citizen-development outcomes as a capability-and-governance problem first and a tooling-choice problem second. ([inference]; medium confidence; source: https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html; https://davidamitchell.github.io/Research/research/2026-04-26-systems-capability-debt-citizen-development-empirical-evidence.html; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6)

Evidence map:

Claim Source Confidence Notes
[inference] Enterprise rollout succeeds when maker enablement is paired with governance design, technical support, and explicit choices on security, compliance, and change. https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890 high 24-company study; 30-interview study; 18-firm multi-case
[inference] Evidence for faster local delivery exists, but hard enterprise-scale effect sizes remain weak and inconsistent across the accessible literature. https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/ medium Benefit direction clearer than benefit magnitude
[inference] Recurring failure modes include substandard quality, tools outside formal IT visibility, technical debt, security strain, and context-dependent adoption barriers. https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539 high Multi-source convergence on risk classes
[inference] Successful rollout models use collaboration mechanisms such as training, intake, scaling support, catalyst roles, and central review or repository controls. https://hdl.handle.net/10125/108890; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/ high Mechanism detail strongest in the conference abstract
[inference] Pilot success does not automatically translate to enterprise rollout, because scaling introduces new coordination and review burdens that need distinct phases and support structures. https://hdl.handle.net/10125/108890; https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/ low Adjacent RPA evidence used for scaling pattern
[inference] The empirical rollout literature aligns with prior repository findings that outcomes depend primarily on organisational capability and governance design. https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html; https://davidamitchell.github.io/Research/research/2026-04-26-systems-capability-debt-citizen-development-empirical-evidence.html; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6 medium Cross-item synthesis

Assumptions:

  • [assumption; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://link.springer.com/article/10.1007/s10257-022-00553-8] RPA citizen-development rollout evidence is used as an adjacent analogue for LCNC scaling because both move automation authoring toward business users under centrally managed platforms. Justification: the low-code literature is stronger on governance themes than on rollout-stage mechanics.
  • [assumption; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3] The absence of hard enterprise-scale performance metrics in the accessible literature is treated as an evidence gap rather than evidence that benefits are absent. Justification: several studies report benefits, but mostly in qualitative or review form.

Analysis:

The most plausible rival explanation is that LCNC rollout success or failure is driven mainly by platform maturity rather than by governance design. [inference; source: https://colab.ws/articles/10.1109%2Faccess.2023.3258539; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/] The consulted empirical studies do not fully reject that rival explanation, but they place much more explanatory weight on design choices, technical-expert involvement, collaboration mechanisms, and context-dependent adoption barriers than on any single platform capability. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://colab.ws/articles/10.1109%2Faccess.2023.3258539] That weighting justifies a conclusion that governance and organisational capability are the dominant levers for rollout quality, while tool choice matters mainly by shaping the complexity boundary and the control surfaces available to the organisation. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html] The weak state of quantitative outcome measurement is also decision-relevant, because it means executives should treat claims of large productivity gains as context-sensitive and should demand local measurement plans rather than assuming enterprise-wide benefits from the literature alone. [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/]

Risks, gaps, uncertainties:

  • Large public datasets with standardized before-and-after enterprise outcome measures remain scarce, so effect sizes for quality, backlog reduction, and cost savings are uncertain. [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3]
  • The accessible evidence base is concentrated in Europe and North America and is heavy on qualitative studies, so generalizability across sectors and governance regimes remains limited. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890]
  • The adjacent RPA literature strengthens the scaling argument, but it does not prove that LCNC rollout programs will show identical failure rates or lifecycle dynamics. [inference; source: https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/]

Open questions:

  • Which organisations have published before-and-after metrics on backlog reduction, defect rates, or maintenance cost after rolling out governed citizen-development programs?
  • How stable are LCNC program benefits over three to five years once maintenance, staff turnover, and platform lock-in are included?
  • Which governance controls are most predictive of safe scale in highly regulated sectors such as banking or health?

§7 Recursive Review

  • Review result: pass.
  • Confidence assessment: medium.
  • Acronym and domain-term audit: LCNC, IT, RPA, CIO, and DOI expanded on first use; specialist terms kept in plain language.
  • Cross-item integration audit: two materially related completed items cited and distinguished.

Findings

(Populated from section 6 synthesis above.)

Executive Summary

Empirical evidence shows that organisation-wide LCNC programs can improve local delivery speed and broaden participation, but durable rollout depends on treating citizen development as a governed operating model rather than as a simple tooling rollout. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/] Across the strongest accessible studies, the recurring success pattern is bounded maker autonomy supported by central standards, technical experts, collaboration mechanisms, training, review paths, and escalation for higher-complexity work. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/] The recurring failure pattern is socio-technical: studies repeatedly describe substandard software quality, tools outside formal IT visibility, technical debt, security strain, and context-specific adoption barriers when governance and support lag behind growth. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539] Evidence for exact enterprise-scale performance gains remains thin, because the best accessible multi-organisation studies focus much more on governance design and collaboration mechanics than on standardized before-and-after outcome metrics. [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://hdl.handle.net/10125/108890]

Key Findings

  1. The strongest accessible empirical studies show that enterprise citizen-development programs succeed when organisations treat them as governed operating models, pairing maker enablement with central standards, technical support, and explicit design choices around security, compliance, and organisational change. ([inference]; high confidence; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890)
  2. The available evidence supports faster local solution delivery and broader participation by non-IT staff, but the literature does not yet provide a robust cross-study enterprise effect size for productivity, software quality, backlog reduction, or cost savings. ([inference]; medium confidence; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/)
  3. Recurring failure modes across the consulted studies include substandard software quality, tools outside formal IT visibility, technical debt, security and compliance strain, and adoption barriers whose severity depends on the surrounding organisational context rather than on the platform alone. ([inference]; high confidence; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539)
  4. Successful rollout models repeatedly combine business-user autonomy with structured collaboration mechanisms, including training, ideation intake, coordinated scaling, project execution support, professional catalyst roles, and central review or repository controls. ([inference]; high confidence; source: https://hdl.handle.net/10125/108890; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/)
  5. The best adjacent scale-up evidence indicates that pilot success does not generalize automatically, because enterprise rollout introduces coordination, review, and support burdens that require separate scaling phases and more expert involvement than early local experiments do. ([inference]; low confidence; source: https://hdl.handle.net/10125/108890; https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/)
  6. Taken together with prior completed repository items on governed low-code operating models and systems-capability debt, the empirical literature supports reading citizen-development outcomes as a capability-and-governance problem first and a tooling-choice problem second. ([inference]; medium confidence; source: https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html; https://davidamitchell.github.io/Research/research/2026-04-26-systems-capability-debt-citizen-development-empirical-evidence.html; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6)

Evidence Map

Claim Source Confidence Notes
[inference] Enterprise rollout succeeds when maker enablement is paired with governance design, technical support, and explicit choices on security, compliance, and change. https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890 high 24-company study; 30-interview study; 18-firm multi-case
[inference] Evidence for faster local delivery exists, but hard enterprise-scale effect sizes remain weak and inconsistent across the accessible literature. https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/ medium Benefit direction clearer than benefit magnitude
[inference] Recurring failure modes include substandard quality, tools outside formal IT visibility, technical debt, security strain, and context-dependent adoption barriers. https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/; https://colab.ws/articles/10.1109%2Faccess.2023.3258539 high Multi-source convergence on risk classes
[inference] Successful rollout models use collaboration mechanisms such as training, intake, scaling support, catalyst roles, and central review or repository controls. https://hdl.handle.net/10125/108890; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/ high Mechanism detail strongest in the conference abstract
[inference] Pilot success does not automatically translate to enterprise rollout, because scaling introduces new coordination and review burdens that need distinct phases and support structures. https://hdl.handle.net/10125/108890; https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/ low Adjacent RPA evidence used for scaling pattern
[inference] The empirical rollout literature aligns with prior repository findings that outcomes depend primarily on organisational capability and governance design. https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html; https://davidamitchell.github.io/Research/research/2026-04-26-systems-capability-debt-citizen-development-empirical-evidence.html; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6 medium Cross-item synthesis

Assumptions

  • [assumption; source: https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/; https://link.springer.com/article/10.1007/s10257-022-00553-8] RPA citizen-development rollout evidence is used as an adjacent analogue for LCNC scaling because both move automation authoring toward business users under centrally managed platforms. Justification: the low-code literature is stronger on governance themes than on rollout-stage mechanics.
  • [assumption; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3] The absence of hard enterprise-scale performance metrics in the accessible literature is treated as an evidence gap rather than evidence that benefits are absent. Justification: several studies report benefits, but mostly in qualitative or review form.

Analysis

The most plausible rival explanation is that LCNC rollout success or failure is driven mainly by platform maturity rather than by governance design. [inference; source: https://colab.ws/articles/10.1109%2Faccess.2023.3258539; https://research.rtu.lv/en/publications/challenges-of-low-codeno-code-software-development-a-literature-r/] The consulted empirical studies do not fully reject that rival explanation, but they place much more explanatory weight on design choices, technical-expert involvement, collaboration mechanisms, and context-dependent adoption barriers than on any single platform capability. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890; https://colab.ws/articles/10.1109%2Faccess.2023.3258539] That weighting justifies a conclusion that governance and organisational capability are the dominant levers for rollout quality, while tool choice matters mainly by shaping the complexity boundary and the control surfaces available to the organisation. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/6; https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://davidamitchell.github.io/Research/research/2026-04-24-business-led-low-code-agent-governance.html] The weak state of quantitative outcome measurement is also decision-relevant, because it means executives should treat claims of large productivity gains as context-sensitive and should demand local measurement plans rather than assuming enterprise-wide benefits from the literature alone. [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/]

Risks, Gaps, and Uncertainties

  • Large public datasets with standardized before-and-after enterprise outcome measures remain scarce, so effect sizes for quality, backlog reduction, and cost savings are uncertain. [inference; source: https://research.universityofgalway.ie/en/publications/adoption-of-low-code-and-no-code-development-a-systematic-literat-6/; https://aisel.aisnet.org/misqe/vol23/iss3/3]
  • The accessible evidence base is concentrated in Europe and North America and is heavy on qualitative studies, so generalizability across sectors and governance regimes remains limited. [inference; source: https://aisel.aisnet.org/misqe/vol23/iss3/3; https://aisel.aisnet.org/misqe/vol23/iss3/6; https://hdl.handle.net/10125/108890]
  • The adjacent RPA literature strengthens the scaling argument, but it does not prove that LCNC rollout programs will show identical failure rates or lifecycle dynamics. [inference; source: https://link.springer.com/article/10.1007/s10257-022-00553-8; https://digital.gov/2021/08/16/5-tips-for-implementing-citizen-development-in-your-rpa-program/]

Open Questions

  • Which organisations have published before-and-after metrics on backlog reduction, defect rates, or maintenance cost after rolling out governed citizen-development programs?
  • How stable are LCNC program benefits over three to five years once maintenance, staff turnover, and platform lock-in are included?
  • Which governance controls are most predictive of safe scale in highly regulated sectors such as banking or health?

Output

(Filled in on completion, describing what this item produced.)

Navigation

Home

By Tag

bureaucracy

change-management

coase

constraint-analysis

control-model

decision-rights

delegation

delivery-risk

demand-segmentation

enterprise

exception-handling

execution

flow

flow-design

flow-metrics

governance

governance-patterns

incentives

instability

institutional-economics

leading-indicators

operating-model

organisation

organisational-design

queue-design

queueing

regulated-enterprise

routing

throughput

throughput-risk

transaction-costs

triage

williamson

Clone this wiki locally