Foundations of Data Teams
summary
Claims a 85% fail rate for data projects and argues failures come from missing specifics not wrong vendors; recommends staffing where a data scientist has 1:2 minimum ratio of data engineers (sometimes 1:5–1:10), expects a 10x ROI target, and prioritizes a singular focus of one to three use cases. Calls out pitfalls: choosing Snowflake/Databricks/Spark/Airflow for buzz, unclear where pieces run, optimistic timelines, missing operational staff, and the need for organizational change and clear architecture before buying tools.
AI-written summary · about
chapters (16)
- 0:00Data team foundations
- 1:37Why data projects fail
- 4:46Team roles and ratios
- 8:43Business value needed
- 11:08Realistic timelines
- 14:58Data processing architecture
- 17:25Executing data plan
- 20:14ROI justification
- 23:42Organizational change
- 25:55External help needed
- 27:44Case studies
- 29:10ROI and stakeholders
- 32:22Data governance
- 34:30Data scientist skills
- 37:20Culture and collaboration
- 38:23Q&A
related talks
29mBuilding successful data teams in the realities of 2023
53mThe State of Data Engineering
55mBuilding The Data Dream Team
38mBuilding Effective Data Teams: Strategies for Success
33mManaging Stakeholders: The Key to Successful Data Science for Business
23mHow to Build a Data-Intelligence Startup within your Organization
41mProficiency + Creativity = Happy Data Practitioners
40mBuilding Successful Data Science Projects