What will be the lasting impact of citizen developers?
Sort by:
But then you need governance to run governance, too. Some of the companies I was at had five or six subcommittees. Pretty soon, I wasn’t running IT anymore, I was participating in all these subcommittees—governance and steering committees—just trying to keep everything straight.
On a single node, there's less likelihood of a race condition where two things are battling to see who can change the state of something faster. It's dangerous when things are doing some type of trigger response on an enterprise scale across multiple systems, whether that's a citizen developer tool or built-in, out-of-the-box integrations. Whether it's the Cobalt disaster or Y2K, I think there will be an era where one of us will get pulled out of retirement to go solve some Cloud race condition or enterprise race condition caused by citizen developers. In other words, I'll probably look smarter later, but it's going to happen. If you can't figure out why something keeps getting overwritten, it's a lack of governance.
We’ve found that there's a specific group of people that can properly run these RPA scripts. These “citizen developers” are trying to run them but they're not experts, and they don't really understand what it's doing on the back end. There's no governance on who's doing it and when. Having a process and a control or security layer around what each RPA tool is capable of doing at any one time, is important.