“Most data teams apparently operate like service teams, and apparently they hate this model (I disagree, but whatever).”
fwiw I am seated for a post about this if you have one in you! Maybe to clarify first: do you disagree that the model is wrong/bad or that most data teams hate it?
i just don't think the model is wrong or bad depending on the business. not every business is gonna have data as good and golden as spotify's, and not every business is gonna be able to churn out cool data products like the one i list. either not ever, or not for the first several years of the data team's existence. i think a service desk model makes a lot of sense and is a good, necessary maturation stage, and for some teams, it might be permanent and there shouldn't be anything wrong with that. just feels like cheap marketing tactics to be like "Service desk always wrong and bad" when to me, the reality is 'service desk sometimes wrong, sometimes exactly what the business needs'.
will add it to the backlog ;) where do you land on this one?
As I suspected, I’m with you :) I have a possibly spicier take about gender and perceptions of “service” vs. “product (engineering)” work; that’s probably enough for you to guess what it is. FWIW, I’ve served (and burned out) on service teams and understand how frustration with it can build—it takes skillful leadership/management to make it work well and retain people over an extended period. But I don’t think a “product” model can fully replace it in most environments, finding a blend is probably the (only?) way, with the balance shifting back and forth over time as the org and its data org evolve. Not a great sound bite.
“Most data teams apparently operate like service teams, and apparently they hate this model (I disagree, but whatever).”
fwiw I am seated for a post about this if you have one in you! Maybe to clarify first: do you disagree that the model is wrong/bad or that most data teams hate it?
i just don't think the model is wrong or bad depending on the business. not every business is gonna have data as good and golden as spotify's, and not every business is gonna be able to churn out cool data products like the one i list. either not ever, or not for the first several years of the data team's existence. i think a service desk model makes a lot of sense and is a good, necessary maturation stage, and for some teams, it might be permanent and there shouldn't be anything wrong with that. just feels like cheap marketing tactics to be like "Service desk always wrong and bad" when to me, the reality is 'service desk sometimes wrong, sometimes exactly what the business needs'.
will add it to the backlog ;) where do you land on this one?
As I suspected, I’m with you :) I have a possibly spicier take about gender and perceptions of “service” vs. “product (engineering)” work; that’s probably enough for you to guess what it is. FWIW, I’ve served (and burned out) on service teams and understand how frustration with it can build—it takes skillful leadership/management to make it work well and retain people over an extended period. But I don’t think a “product” model can fully replace it in most environments, finding a blend is probably the (only?) way, with the balance shifting back and forth over time as the org and its data org evolve. Not a great sound bite.