While low code and no code citizen development programmes are often popular in the corporate world, they are not without their limitations. While some see citizen development programmes as an important part of building automation-friendly company culture, others have concerns about spreading employees too thinly and training them away from their expertise. Join Mike Fitzmaurice, Chief Evangelist and VP at WEBCON, as he chairs this debate between Christine Hawkins, Director of Digital and Process Transformation at HP, and Linford Dailey, Global Digitalisation and Automation Leader at Bosch as they discuss:

• What are the benefits of low code and no code citizen development programmes?
• How effective are citizen development programmes at boosting productivity and reducing costs?
• When is it appropriate to employ low code & no code tools? When is it NOT?
• Can citizen development programmes distract employees from their expertise?
• Governance: how much power should be given to citizen developers?

No matter who builds it, why they build it, how they build it, or for whom they build it, every application of any worth eventually (sometimes immediately) crosses a line. It becomes important to people beyond its original audience. And when that happens, it can longer afford to be “quick and dirty.”

Treating every workflow like an enterprise solution starts with addressing security, scalability, usability, and accountability from the start instead of getting around to them later on (often after a mistake is made). But most importantly, it requires looking beyond the tactical automation task at hand and focusing on the strategic process it serves. Design choices made in locally-scoped, citizen developed vacuums can be a source of great headaches or great utility — depending on mindset.

We’ve got principles, real-world examples, and recommendations to share, and we hope you’ll join us.