Lean Citizen Development in Manufacturing: Why Lean and No-Code Belong Together
Lean citizen development links continuous improvement with no-code apps built by employees. Why leading plants already work this way, and how to get started.
By Johannes Mohren ·
What do the Toyota Production System and no-code have in common?
More than you'd think.
At its core, lean revolves around a single conviction: the people who work in the process every day understand the problem best. That's why kaizen, A3 and shopfloor management exist. All of them are methods that bring problem-solving to where the problem arises.
Citizen development follows the same logic, but for software. Instead of waiting for the IT department to work through a ticket, the employee in the maintenance team, the warehouse or assembly builds their own app. In plain language, without a single line of code.
That's no coincidence. It's lean taken to its digital conclusion.
What exactly is lean citizen development?
Lean citizen development brings two approaches together:
- Lean aims to eliminate waste, stabilize processes and enable employees to solve problems themselves.
- Citizen development gives non-technical employees the tools to build their own digital applications, on low-code or no-code platforms.
Together, digital solutions emerge exactly where the pain is: with the shift supervisor who enters KPIs by hand every day. With the maintenance technician who keeps maintenance reports in Excel. With the logistics planner who has been waiting 18 months for an IT solution.
The three lean principles carry over directly:
- Eliminate waste: no waiting on the IT backlog.
- Enable people: the department builds its own apps.
- Iterate fast: a solution in hours, not months.
Why does classic citizen development fail without lean?
Citizen development without lean discipline often ends in chaos: uncontrolled shadow IT, apps nobody maintains, security gaps, contradictory data. Every company that enabled Power Apps and then forgot about it knows this.
Lean brings the structure back.
First: process before tool. A basic lean principle, and just as important here. If you digitalize a bad process, you get a bad digital process. Lean forces you to understand and stabilize the process first, before putting an app on top of it.
Second: governance through standards. Lean has standards, not to block innovation but to make it scalable. In lean citizen development, that's the center of excellence: central IT guidelines, approved platforms, clear escalation paths. The department builds, but within defined guardrails.
Third: PDCA instead of deploy-and-forget. In lean, every improvement is followed by a check. Citizen-developer apps need the same cycle: build, test, adjust, standardize.
A lean plant built a digital SQDC board without waiting for IT
In a plant that has relied on lean for decades, someone formulated a requirement every shopfloor manager knows: a digital SQDC board, meaning a visualization of safety, quality, delivery and cost, combined with a PDCA ticket system.
The classic route: ask IT, wait six months, get a compromise.
The lean citizen development route: the person responsible for production describes the app in plain language. An AI-based no-code platform builds the first version within minutes. Database connection, role management, live deployment on tablets and touchscreens, all without a line of code.
The reaction from the operational staff was clear. It wasn't the managers who got excited. It was the people on the line, at the machines, in the warehouse. Because suddenly they had solutions in their hands that solve their problems, and that they can shape themselves.
That's the difference between lean on paper and lean as a culture.
Which citizen development use cases work best in manufacturing?
Conversations with plant managers and production managers in German industry point to these areas:
Logistics and material flow: digital staging lists, transport orders, stock recording without ERP overhead.
Maintenance: maintenance checklists, fault reports, machine history, which until now lived in Excel or on paper.
Shopfloor management: SQDC boards, action trackers, shift reports, real-time KPI visualization.
Production and assembly: digital production orders, 5S audits, quality reports right at the line.
What these use cases have in common: they're too specific for standard software and too frequent for manual processes. That's exactly the gap lean citizen development closes.
Does lean citizen development work in a brownfield plant?
The most common objection: "We're not a modern greenfield plant. Our infrastructure dates from the '60s, and our machines don't have APIs."
Ingo Hild, plant manager at ams OSRAM and a lean practitioner for years, has this to say (translated from German):
"We're a brownfield plant. That's important for everyone else, as an indication: this isn't something you can only do in new factories. Whenever we do something in the plant, we always do it through lean thinking: first make the processes lean, then digitalize. Have courage, lead the way. It works the same in any other plant."
— Ingo Hild, Plant Manager, ams OSRAM
The answer from practice: yes, it works.
Lean never waited for perfect conditions, and neither does citizen development. The deciding factor isn't the infrastructure. It's the culture. Do you trust employees to solve problems themselves? Do you give them the tools and the freedom to do it?
Plants that have practiced low-cost automation for years, with sensors from the hardware store, self-built gateways and pick-by-light made from supermarket parts, are often better prepared for lean citizen development than plants with expensive, rigid standard software. They already have the mindset.
The technology is simple enough today. What's missing is courage.
How to introduce lean citizen development: a pragmatic start
No big transformation program. No steering committee. No consultants.
Step 1: Pick a real pain point. Not the most strategically important use case. The one that annoys everyone every day. The one you've been waiting on IT for a year to solve.
Step 2: Understand the process before you build. Lean first. Which steps are necessary? Where is the waste? Only then comes the app.
Step 3: Pilot with the right people. Not the tech-savvy ones. The experts who know the process inside out. They build the best app, if you let them.
Step 4: Set the guardrails. Which platform is approved? Which data may be connected? Who takes over an app when its creator leaves the company? Settle these questions up front, not afterwards.
Step 5: Show the result, scale the pattern. Document what worked in the pilot, not as software documentation but as a lean standard. Then replicate it.
Lean without citizen development only goes halfway
The question is no longer whether lean and citizen development fit together. They're growing together right now, in plants from ZF to Festool to mid-sized brownfield operations.
The deeper question is: who really enables the employees? Who gives them not just methods, but tools too? Who turns the passive user into an active shaper, not just in the continuous improvement (CIP) workshop, but every day, right in the process?
Lean was always a mindset, not a collection of methods. Lean citizen development is that mindset, thought through consistently into the digital world.
Go deeper
Webinar: "Citizen Development – Jetzt baue ich meine Software selbst" (Now I build my own software, in German)
This webinar with Industrie 4.0 Award winner ams OSRAM and Georg Wasserloos (Macils) shows what lean citizen development looks like in practice. ams OSRAM uses Arctory in its own plant and shows live how citizen development works in a real brownfield production: which apps were built and what other plants can adopt right away.
Watch the webinar recording on Lernreise.com →
Back to the blog
