Matthew Kelliher-Gibson, MBA’s Post

View profile for Matthew Kelliher-Gibson, MBA, graphic

AI/ML | Data | Strategy | Product | Cynical Data Guy @ The Data Stack Show

This started as a normal blog post but by the end was more personal. This post outlines the basic strategies I used to go from first time Data Science Manager to Sr Director in 3.5 years. ⭐️ You need to split out ad hoc support work from data development work 📵 Funnel all requests to centralized channels and away from individuals 📊 Capture, prioritize, and track all requests 📑 Create formal or informal SLA for requests and deliveries Once you start to get your hands around the whirlwind 🌪️ go and find data use cases. They are not going to come to use in the beginning. It is hard work but rewarding to get off the treadmill and start getting work with long term bottom line value done.

View organization page for RudderStack, graphic

56,984 followers

🥵 Data professionals are burnt out. Often, the burnout stems from the tension created by a one-size-fits-all approach to data work. When one function tries to balance long-term strategic initiatives with urgent data support, stress is inevitable. In this piece, we look to the past for answers. We examine how IT and software development teams created clear edges that enable them to do their best work. Then we provide a roadmap to help you apply this principle to data work but separating two high-level workflows: 🔹Data support 🔹Data development Go deeper 👇 https://bit.ly/3P0JnU9

Why data teams must separate support work from development work

Why data teams must separate support work from development work

rudderstack.com

Jessi Smith

Healthcare analytics professional

8mo

Loved this article. Articulated the exact issues I am seeing in my team. Explanations make sense and the advice is good.

To view or add a comment, sign in

Explore topics