Taking the blame out of our data transformation
summary
Two case studies show a practical technique called the three frenemies (judgments, assumptions, expectations) used over five years to stop blame and share data: one recounts a 15‑second API response and planned downtimes that forced digital to buy its own tool and later sync data; the other uses data as a product on a serverless platform with SQL pipelines, pairing engineers across departments to reduce tension, surface a surprising cellby date edge case, and tighten data contracts so consumers get usable, accountable datasets.
AI-written summary · about
chapters (9)
- 0:00Data transformation intro
- 2:49Blaming others hinders progress
- 5:56No-blame culture in high-risk
- 9:27Three collaboration frenemies
- 14:06Case study: Digital vs enterprise
- 22:14Case study: Data transformation
- 27:52Case study: Digital meets digital
- 30:42Recap and takeaways
- 33:10Further reading and closing
related talks
39mBREAKING YOUR DATA TEAM OUT OF THE SERVICE TRAP
44mPreventing, Diagnosing & Curing Bad Data
38mLesson learned implementing a large-scale data mesh transformation
18mData quality: the key to long term happiness
29mManaging your Data Assets: The interview
27mData team strategies: unleashing your team
31mWhen the data levee breaks: Managing cognitive load in data-intensive projects
31mFrom Raw Data to Real Impact: Lessons from Real-World Transformations