And even if you are the right manager archetype to match a team or IC's situation, you might be spread across more business areas than you have time to meaningfully engage with
-
Show this thread
-
Having overlap (beyond technical skillset overlap) between the areas your ICs work in reduces some of the pressure on you as the DS manager because means they have more ability to support each other. But it doesn't stop you from getting pulled between the breadth and depth poles
1 reply 0 retweets 1 likeShow this thread -
You can only do so many things at once. Or at least, you can only do so many things WELL at once. Which is to say: I'm not inclined to believe that thinly spread matrixed orgs generate the best outcomes unless all the ICs are pretty senior
1 reply 0 retweets 5 likesShow this thread -
And even then, this is another situation where a lot of pressure is being placed on a single person or too few people. Teams are guardrails that allow folks to take vacation, get sick, or move on to something else without leaving everyone else in a lurch
1 reply 0 retweets 4 likesShow this thread -
Maybe the real takeaway here is that DS teams are usually understaffed. Matrix orgs are an attempt to make the most of a difficult situation, but IMO they require a lot of skill and humility to manage well. The fact that they're so common for DS teams is nuts
4 replies 0 retweets 12 likesShow this thread -
Replying to @imightbemary
I feel like professional settings are missing ways to provide some of these services without attaching 'lead' or 'manager' to the job title.
1 reply 0 retweets 1 like -
Replying to @RussellSPierce
One thing that might help would be identifying the “design patterns” of DS work. There are a lot of canonical ways to build production-grade software, but I don’t know that those have been identified for DS
1 reply 0 retweets 3 likes -
Replying to @imightbemary
That's a hard one. The impostor stuff doesn't help, because people are compelled to try to put a data foot into a production shoe... and data feet seem to be way more heterogeneous than production feet.
1 reply 0 retweets 3 likes -
Replying to @RussellSPierce
While that's true, I can't help but think there have to be SOME common frameworks. The specific data will always be different, but I do find myself constantly reaching for mental models like funnel analyses. It can be extended to a lot of situations
2 replies 0 retweets 2 likes -
Replying to @imightbemary
For better, and worse, it seems like there is at least a cottage industry of turning very common patterns, like funnel analysis, into products.
1 reply 0 retweets 2 likes
For sure. That's why I've been trying to think of them as design patterns rather than products. Productization makes the analysis framework to rigid to fit the proverbial heterogenous data feet
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

