Managing citizen development.
WHY GOVERNANCE MATTERS HERE PARTICULARLY
Anyone with a licence can build something the business comes to depend on.
WHAT GOES WRONG WITHOUT IT
Business-critical processes in applications nobody documented Data moved between systems inappropriately Applications that stop working when someone leaves Duplicated solutions Licensing surprises
WHAT TO ESTABLISH
Who may build, and where Data loss prevention policies Environment strategy A register of what exists and who owns it A path for escalating something important to proper support
WHAT THAT LAST POINT MEANS
When a personal tool becomes business-critical, it should be taken over, documented and supported.
WHAT TO MONITOR
What is being created Which connectors are used Applications and flows with many users
WHAT TO REVIEW
Ownership, particularly after people leave Items unused for long periods
WHAT TO PROVIDE
Training, templates and a support channel.
WHY
Prohibition produces workarounds; enablement with guardrails produces better outcomes.
WHAT TO DOCUMENT
The rules, plainly.
