Proficiency + Creativity = Happy Data Practitioners
summary
Argues that data teams must hold proficiency and creativity in balance and gives concrete practices: adopt analytics-engineering standards like testing and monitoring plus code review and dbt refactors, embed analysts in stakeholder meetings, measure user trust via surveys, and run time-boxed explorations and hack weeks. Shares a failure case: a campaign-risk model proved no-better-than-chance (a coin flip), which didn’t work but produced actionable next steps (capture new inputs, build creator tools) rather than more modeling.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:02Speaker and talk overview
- 2:28Proficiency vs creativity
- 6:02Why both matter
- 9:31Balanced data team culture
- 16:22Engineering for proficiency
- 19:33Empowerment and trust
- 24:59Reliability vs innovation
- 28:08Actionable takeaways
- 30:58Closing vision
- 31:41Q&A
related talks
25mThriving & Winning – Beyond Knowing The Why Of Data Management:
47mData Analytics: Realizing the Full Potential
21mBuilding a Data Driven Culture
14mBuilding a Data-Driven Culture: An Anthology of Strategies and Insights
26mData & Analytics Strategy: 5 Overlooked Components
39mFoundations of Data Teams
38mBuilding Effective Data Teams: Strategies for Success
37mData Poker not Data Chess - thinking in Bets for Data Teams