Came across this article about no code data governance while researching something for a client. The thinking is directionally accurate but assumes a near perfect environment where this becomes possible. Reality is that the time to reach perfection is untenable for most businesses so systems and applications get stood up that address the burning, time sensitive need. A vendor rolls in with the tools and services and rigs up what it takes. Across a large enterprise there are any number of such "pockets of brilliance" where some problems are being answered perfectly by solutions built just to that. In such an environment which is more norm than exception deploying a low-code/no-code data governance solution is unlikely to work.
What I have seen work better is customers making data governance table stakes in how any work is done that has to do with production, consumption and movement of data. That build an enterprise data environment where certain guardrails are built in and data is fully observable. This is not just a technology problem to solve. It requires organizational will for self-discipline and top-down support for governance and making hard people and process changes to make all this happen. Technology is the easiest part of the solution.
This article glosses over the difficulty of building that stable eco-system and jumps several steps ahead where the world is perfect by default. It's hard when such fantasies are purveyed by the "experts" and customers start to believe such dreams could come true in their world where reality looks wildly different.
Comments