Getting Data Done with a Pragmatic Data Team
summary
Team builds datasets, APIs and integrations across varied domains, uses Python and Git for code‑based work, and balances ad‑hoc fixes with quarterly roadmaps; hiring and onboarding hinge on set expectations honestly about pipelines, domain work and support obligations. Annual goals pair portfolio projects (market model, supply chain, platform rebuild) with skills targets so people learn while delivering. A monthly visibility forum showcases wins, creates stakeholder buy‑in, and prevents burnout by distributing operational load.
AI-written summary · about
chapters (7)
- 0:00Annapurna to pragmatic teams
- 3:19Harmful value continuum
- 6:59Honest expectations for roles
- 10:54Balancing business and growth
- 14:14Pragmatism without ambition
- 16:27Visibility for team success
- 18:14Q&A
related talks
26mData, It’s a People Problem: Understanding the Sociotechnical Elements of a Data-Driven Organization
31mProductionalizing a Data Science Team
38mBuilding Effective Data Teams: Strategies for Success
24mSecuring Executive Buy-In for Data Strategies
23mData engineering team leads
23mData Team as an Optimisation Problem
16mRedefining Agile for Data Science: A Team First Approach
29mBuilding successful data teams in the realities of 2023