A CDO’s Adventure in Generative AI

Generative AI is extremely appealing for non-technical users, who feel like they’ve gained access to magic powers. But as this story shows, a little knowledge is a dangerous thing.

The Magic Genie

Once upon a time, there was a Chief Data Officer who believed that the new wave of Generative AI, such as ChatGPT and Gemini, could bridge any technical hurdle. At a local AI meetup, they met a founder with no technical background who had proudly built an entire prototype website using nothing but natural language prompts. It seemed like a genie in a bottle. Rub it a little bit (give it tokens), make a wish (give your prompt), and *poof* you have code, text, or some description of what you need to do.

Every day, back in their own enterprise, this data leader watched as more team members treated these general-purpose tools as magical little helpers. However, as a data expert, the CDO began to worry about the “fuzziness” of the results. Unlike the Predictive AI they were used to—which is deterministic, consistent, and built on specific statistical mathematics—Generative AI was proving to be non-deterministic. If you gave it the same prompt twice, you’d get two different answers, making it a liability for rigorous production environments.

But then one day, the genie was asked to build a web site. It did so, but did not build all the infrastructure necessary to support a web site. The CDO realized that a little knowledge is a dangerous thing.  While the Generative AI could only build a beautiful facade, it couldn’t account for what the user “didn’t know they didn’t know.”

As in days of old, the “it works on my machine” dragon was waking up. The user that wrote the prompt was solely responsible for judging the accuracy of output they didn’t fully understand. The person making the wish (giving the prompt) would have had to have the expertise of a software engineer, the experience of a network engineer, and the judgement of a systems engineer to get the prompt just right and know if what was generated was ultimately the right thing.

As the data team scrambled to clean up the mess, the CDO thought, “maybe this GenAI isn’t so helpful after all.”

The Shift to Domain Specificity

Because of that, the CDO began looking for a better way to manage cognitive load. General Purpose Generative AI (GPGenAI) is truly a genie in a bottle: it can be a powerful but unpredictable tool to those without the right vocabulary. They needed the AI to act less like a creative writer and more like a Subject Matter Expert (SME) that could produce reliable, stable, and consistent output.

That’s what a Domain-Specific Generative AI (DSGenAI) does. DSGenAI tools are highly specialized, with embedded capabilities for tasks, such as SQL generation within known data structures or Python-specific environment management.

Because of that, the organization moved away from relying on “general” generative AI for technical tasks. They recognized that for a tool to be useful in a professional data environment, it needed to be familiar with the specific packages and data architectures of the business. DSGenAI was like a genie that has grown up in a culture of hacking SQL, munging Python, and dealing with package management hell.

The New Standard of Data Integrity

Finally, the CDO established a new framework for AI adoption. They now knew that while GPGenAI is excellent for MVPs and brainstorming, production-grade data operations require the precision of DSGenAI. They stopped asking if the AI was “smart” and started asking the people using the tools if the tool was “grounded” in their specific domain.

And ever since, the data team has acted as the ultimate judge of quality. They learned that even with the best DSGenAI, the user is still responsible for verifying that the generated code matches the request. By choosing tools designed for their specific vocabulary, like METIS from DataOps.Live and CoCo (Cortex Code) from Snowflake, they reduced the risk of “non-positive consequences” and ensured that their production environment was built on a foundation of expertise, not just probability.

Liked Liked