Author: Will Robins

You may not have heard the term data downtime, but I’m willing to bet you’ve experienced it and the cost of bad data firsthand.

Urgent ping from your CEO about “missing data” in a critical report? Duplicate tables wreaking havoc in your Snowflake warehouse, all titled some variation of “Mikes_Table_GOOD-V3.”? Or, perhaps you’ve unintentionally made a decision based on bad data from last year’s forecasts?  

Data trust starts and ends with communication. Here’s how best-in-class data teams proactively certify tables as approved for use across their organizations.

Say it with me: data engineers are not data catalogs.