According to Stack Overflow's 2022 Developer Survey, 2/3 of developers run up against "knowledge silos" that slow them down. When needed data is stored in other, inaccessible systems, it compromises the effectiveness of your organization.
Especially at tech companies, when workers quit, you not only have a loss of expertise, but you also suffer a loss of institutional knowledge.
What's the difference? If you lose a python developer, for example, you've lost the expertise of python development (which you can recover by hiring a new developer). But, if that developer knew the quirks of the accounting software that your company sells, and can quickly resolve bugs, then that is institutional knowledge that will take time and experience for someone to learn.
To guard against this, you need to encourage employees to document their knowledge of your applications and work processes. The worst way to do this is through requiring them to create complex, formal documents. Your workers are already busy, and this will get put off.
The best way is to encourage them to informally record what they learned as they solve issues. Blogs and wikis are ideal formats.
60% of IT leaders feel that Digital project ROIs are threatened because end-users aren't adopting new tech quickly enough.
This is why my Strategic Simplicity® framework, with its 4 components (change simplicity, message simplicity, decision simplicity, user simplicity), is so important.
Change can't be "dumped" onto end-users. Their needs have to be incoporated in new products. Tech needs to serve the business. Users should not have to adopt sub-optimal processes to adjust to technology.
No. I think that low / no code tools will mostly be used at the front-end, by power end-users, for tasks such as creating custom reports and configuring menus. The applications and back-end infrastructure will still depend on modern programming languages and experienced developers, because low/no code tools will not be fast enough and robust enough to scale and handle security.