Introducing new apps or software platforms into an organization is always challenging. The author of this article spoke with a company that implemented a 'No-Code/Low-Code' platform so discusses some of the fundamental, yet often overlooked aspects like:
- Define overall low/no-code strategy
- Define a data architecture and data movement strategy
- Centrally manage data/user security
However a couple recommendations stood out.
"Make low/no-code development a mainstream technology, not a skunk-works"
We couldn't agree more - top management always needs to be fully on-board for the success of any major project, but particularly with 'No-Code/Low-Code' because it's vitally important to create an atmosphere of 'openness' when empowering team members.
"Provide/require database administrator assistance/approval on all shadow IT driven projects"
As the author points out, this is for "data consistency" and build quality across platform apps. But, with 'empowerment' also comes responsibility. Therefore having a second review of the apps built will most likely be reassuring to 'citizen developers':
- "The users will most likely appreciate the help and IT will have the benefit of not having to redesign and rebuild systems that have been improperly created. "