Citizen developers are non-technical employees who understand their company's operations deeply but have never had tools to fix problems themselves. Giving them the ability to experiment unlocks faster innovation in manufacturing without waiting for IT approval and external developers.
A citizen developer, in essence, is somebody who hasn't got any specialized development skills, but somebody who fundamentally understands the organization they work in, the bureaucracies, the politics, the people, the data, the manufacturing process. It's those kinds of people who we task to improve processes, or manufacturing processes, but we don't really give them the tools or the or the skill set to be able to do that. And so those citizen developers are perfectly placed if they only could build the solution. You know, in times gone by, there'd be multiple stakeholders involved in, in building a single use case. You'd need an IT department, you'd need a manager's approval, you would need sourcing of skills and developers to be able to come in and build a solution for you. But the idea of having a citizen developer is something where someone without real development skills can experiment. And that's the key word here, is experimentation. How can we allow people who fully understand what they want to achieve to experiment?
