Data Science Hangout | Ian Anderson, Philadelphia Flyers | Moving into Leadership & Managing a Team
The Data Science Hangout is a weekly, free-to-join open conversation for current and aspiring data science leaders. posit.co/data-science-hangout We were recently joined by Ian Anderson, Director of Hockey Analytics at the Philadelphia Flyers, to discuss the most important things going in data science leadership. One of the topics that there were a lot of thoughts on during this hangout was balancing that shift into leadership and maintaining technical skills. Question: 𝐀𝐬 𝐲𝐨𝐮 𝐦𝐨𝐯𝐞 𝐮𝐩 𝐭𝐡𝐞 𝐥𝐚𝐝𝐝𝐞𝐫 𝐢𝐧𝐭𝐨 𝐥𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩 𝐚𝐧𝐝 𝐦𝐚𝐧𝐚𝐠𝐢𝐧𝐠 𝐚 𝐭𝐞𝐚𝐦, 𝐚𝐫𝐞 𝐲𝐨𝐮 𝐰𝐨𝐫𝐫𝐢𝐞𝐝 𝐚𝐛𝐨𝐮𝐭 𝐥𝐨𝐬𝐢𝐧𝐠 𝐲𝐨𝐮𝐫 𝐭𝐞𝐜𝐡𝐧𝐢𝐜𝐚𝐥 𝐜𝐨𝐝𝐢𝐧𝐠 𝐬𝐤𝐢𝐥𝐥𝐬? Here are a few of the thoughts shared live from Ian and the community: * You make time for things that are important to you. If exercise and health is important to you, you make time for it. If coding is something that you want to continue to maintain, you can find the time for that. * Think about blocking designated focus time to do your individual work * Be curious. Office hours as a manager to answer questions from your group can also be an opportunity to learn new things/packages/methods together * Organize opportunities for the team to share any topics that they would like (coding, techniques, etc.) In sharing topics, you can also try limiting the time to ~4min to share. Two benefits of this fast moving, high energy meeting: 1. People will inspire each other with passion and creativity 2. The team gets to practice communicating their ideas with precision. * Becoming more comfortable with what it means to lead people, it's about enabling them to be really successful. If you measure your success by other people's success, it can also help rationalize that. If you can chop down barriers for them, then they will be more successful so that means the technical time I sacrifice enables them further. * It's still very relevant to keep your skills at some type of level just for street cred in your team. Bringing in new people, if you can talk that language it just really helps your team and you can have those conversations." ► Subscribe to Our Channel Here: https://bit.ly/2TzgcOu Follow Us Here: Website: https://www.rstudio.com LinkedIn: https://www.linkedin.com/company/rstu... Twitter: https://twitter.com/rstudio
image: thumbnail.jpg
Transcript#
This transcript was generated automatically and may contain errors.
Thank you all so much for joining today and welcome back to the Data Science Hangout. Happy New Year to everyone. I'm so excited to kick off the first one of 2022 with you all and to have Ian Anderson joining us here for his first time as well. But just to introduce the Data Science Hangout for anyone who's joining us for the first time.
The Data Science Hangout is an open space for the whole data science community to connect and chat about data science leadership, questions you're facing, and really just what's going on in the world of data science. So if you ever want to go back and re-watch these or some of the ones that we had in 2021 or share with someone who's missed it, they'll be recorded and shared up to YouTube as well. We really want this to be a space where everybody can participate and we want to hear from everyone. So there's a few different ways you can ask questions during the session today. So you can jump in live, you can raise your hand on Zoom, put questions in the Zoom chat. Feel free to put a little star next to your question too if you want me to read it out loud. Otherwise I can just call on you to introduce yourself and jump in.
But we'll also have a Slido link too where you can ask questions anonymously and I think Tyler will share that in the chat in just a second here. But without all that I'm so happy to be joined by my co-host for today, Ian Anderson. Ian's the Director of Hockey Analytics at the Philadelphia Flyers. And Ian, I'd love to start by maybe having you jump in and introduce yourself and share a bit about your team and the work that you do.
Ian's background and the growth of hockey analytics
Hello everybody, first of all, and thank you for having me. I've been with the Flyers now since 2014. I started as a kind of team of one. I was the third full-time analytics staff member in our sport hired at that time. And then there was a rash of hirings during the 2014 summer. But now that's widespread across the sport. So I'm expanding my team currently. We'll be a team of six very soon.
I was working for the Washington Capitals in the NHL in a different role starting in around 2007. I was in more of an operations role embedded within the team. And I just kind of noticed that we didn't have anybody at that time during those years doing this type of work. And it was being done in other sports. And I just kind of realized, like, maybe this is something we should be doing. And I kind of asked. They said, sure, you want to do it kind of thing. And I was like, well, I don't know anything about this, like, technically speaking, right, how to code, or I didn't go to school for that. So another piece I'll share is I'm a self-taught programmer. I got my master's through Northwestern's Master's of Predictive Analytics, it was called at the time.
Back in 2014, there weren't a lot of programs, too. And one thing that's amazing to me about this industry, and especially about sports analytics in general, is like, it wasn't that long ago. Like, we all lose track of how fast this is moving. And eight years is not a huge amount of time. And so to see kind of how things have expanded and going through the hiring process now, seeing the applicants and the level of their skills over the eight-year period is like, it's exponential growth.
Starting a data science program from scratch
What I will say is I have a lot of experience on this. Again, I got dropped into an organization with no infrastructure, no data pipeline, no anything, right? It was just like, here you go. You figure this all out, one person, right? And so what you realize very quickly, as I'm sure everybody here can attest to, is you can't do this by yourself. It's a team. This is all done by a team of people.
What has worked for me is just creating a very small reproducible example of work or starting very small with a project that you can deliver, right? Just give people something that they can see and touch and feel, right? And then they get to start using or seeing how it improves their lives. Like sometimes the products that we make is just making our coworkers' lives easier and automating some tasks or things like that, right? So do something that people could see that makes their life better that they enjoy. And then they say, wow, this is awesome, great work. And then you say, okay, you like that. Like here's where we want to go next. And here's why we need to expand the team because we could be doing more in XYZ, these areas, right? So instead of trying to do like everything all at once is just like start with one small thing and then build on that, like kind of like taking a long-term approach, I guess would be the best.
Breaking into sports analytics
The piece of advice I would offer people today, and the benefit that they have today, is that there are all these great programs like Big Data Bowl, Big Data Cup, Kaggle, expanding, obviously. There's so many different platforms, even RStudio, all the different tools that have been developed for people to showcase their work. Shiny apps, you name it. There's so many tables, GT table contests. There's so many ways to build a portfolio today that there wasn't even a few years ago. So it's all out there for you to build your own portfolio. And like I said, this is, I'm passionate about this because I'm literally in the middle of hiring right now, and there's just no excuse not to have a portfolio now. So I would just tell people, do the job you want, and that starts now. Like, you could be doing the job now, and it's going to require some extra attention outside of work hours, maybe, and things like that, but it's all doable.
I would just tell people, do the job you want, and that starts now. Like, you could be doing the job now, and it's going to require some extra attention outside of work hours, maybe, and things like that, but it's all doable.
Hiring and building a portfolio
I think it's both, you know what I mean? If you want to take that a step further, and like a lot of people have done, put some of that stuff out in the public sphere, then people will find it. If it's good enough, people will find it. We're always constantly looking, and people love to share good work, and it's amazing the network effects of Twitter and LinkedIn or whatever it might be. I was actively reading a paper I saw on LinkedIn from a connection from years ago who's doing some work in the Bundesliga soccer, right? He did something on passing, modeling passing efficiency and stuff like that. So I'm like, I'm reading that paper right now. Like, that could be your paper. You know what I mean? I could be reading it right now.
You'd be surprised how many people just don't take the time to like customize their resume. Like if there is some sort of like prompt, like I ask questions and they don't fill them out or they don't take time, they don't answer the questions that I'm asking. So I can't even evaluate you because you're not doing what I'm asking you to do off the hop. And then the next thing I would say is really lead with what work you have done that will be most relevant to the position you're applying to.
I just did an interview this morning, a second round technical interview with one of my candidates. And she has great experience. Obviously, I'm moving her along. I think she can do the work. And she dropped something on me. And I'm like, wait a second, this is nowhere in your resume. And we've had, this is our second conversation. This is super relevant to the job you're trying to get with me. And you left it completely off. Like why? And if I didn't ask the right question, I would have never learned that about her. You need to put this somewhere very, very high if it's not with me, the next person, because this is so crucial.
In 2014, when I started, there was a couple of data science programs. And now the applicants I'm getting is everybody has skills, because there's so many great programs. So how do I differentiate those people now, right? There used to be like, I would get 100 applicants and five had skills. So now I'm getting 100 applicants and 40 have skills. Okay, so now that gap is like, there's still how do we differentiate amongst the 40 now should be your question. And the question and the answers I have to that are like projects and things that showcase specific to the our industry, which is sports, right? Show me something that you could apply there. And then now we're going to get into like people that have domain knowledge.
Moving into leadership and managing a team
My 2022 goal for myself is like, and I'm being vulnerable and honest here when I say this is like, I started as a team of one. And to be honest, like I'm learning the management side of things. As I'm going, I'm doing it on the fly kind of thing. And I do believe I need to get better at managing a team, a data science team. So that's what I'm going to focus on this year is going, how do I go from three to six people that are a part of my group, including myself, right? How do we organize ourselves and optimize our group, right?
My progression has been like going from an individual contributor to now going to like a manager, right? And what that entails. And then I'm also part of like a management team that is doing more strategic type work and like, you know, long, short, medium, long-term planning, like things like that. So it's like distinguishing those roles. That's where I get split in two is like, it's not just the contributing data science work. It's the managerial strategic work as well.
Balancing coding skills with leadership
As you go up the ladder of moving from executing day-to-day projects to actually managing a team, it's just something that lingers in my mind because in your current situation, that's how it is, but next year it could be different. So I've always wondered if I moved so far away from the code, so far away from managing, actually executing projects, do I lose my coding skills? And when I'm in the next environment where I need that skillset, is that going to be a difficult process to refresh myself?
Nervous? No, I mean, I think you make time for things that are important to you, right? We all do that on our daily basis. So if exercise and health is important to you, you make time for it. You make time for it. You just do, right? So for me, if coding is something that I want to continue to maintain, I'm going to do it because I enjoy doing it. I'm going to find the time, whether that's at night, that's in the morning. I have two young kids. I mean, I'm juggling a lot of things, right? So it's just time management. And when you have a staff, it's, you know, I've talked to my, with my staff also about maybe having like, toying around with the idea of like office hours, like, okay, 9am to 12pm, I'm like blocked off. Like I'm, that's where I'm going to do my work, my individual work, right? And everybody's going to do their individual work. And then 12 to 1.30 office hours, come with me to any questions you might have, anything we need, we need a decision on or like there's, it's not a clear path, we need to, we need to choose the best way to go.
If I could just give a little piece to Trevor's question and add on to a bit of what Ian has said in the comment from Frank in there. This was top of mind for me like 12 years ago. It's when I really start to transition from a heavy technical role into management. It was geospatial, but technical is technical. It kind of doesn't really matter if it's engineering, if it's coding, if it's whatever. And I struggled with it for about two years. And I think it was because I was comfortable at it. And when you're really comfortable and you're successful or anything like that, but when you're good at something, it's kind of hard to want to leave it behind. But as I matured into my role and I became comfortable of what does it mean to be a manager? What does it mean to lead? I have a bit of a philosophy that I like to carry around. It's the shield and spear. My role becomes less of tactfully putting out widgets. It's more enabling the people to be really successful. So if I try to measure my success by other people's success, and I know that might sound selfish, but it helps rationalize in my head. So if I can chop down and break down all the barriers for them, then they will be more successful. So I sacrifice that technical to enable them to be further. However, I think it's still very relevant to keep your skills at some type of level just for street cred in your team, bringing new people on, having other people within there. If you can talk that language and they see you're like, oh, that's not just some dude in a suit. The barriers come down and you can have those conversations and your communication goes up in a field that is technical.
I like to expand upon that too. I think my approach also is to use a little bit of humility with my team and just go to them and say like, hey, what are you doing here? I see you've done something here, teach me that. I want to learn that. And I tell people that actively that the guys on my team right now and people that I'm interviewing, I'm saying, I said this briefly earlier and I mean it, I want to hire people smarter than me because if I'm hiring people below my skill level all the time, then I'm constantly having to be the teacher where I'm trying to lift up six people myself. Whereas if I'm constantly hiring somebody that's an expert at something above me, then they're lifting me and my group up, the other people in that one domain. And then the next person's doing that in their domain. And so we're spreading the expertise across and we're teaching each other and working collaboratively as a group. The buck still stops with me and I'm still responsible for, like you said, being the shield, as you said, for management or moving obstacles out of their way. And sometimes the obstacles that are in people's way, I've realized is like me or processes.
I want to hire people smarter than me because if I'm hiring people below my skill level all the time, then I'm constantly having to be the teacher where I'm trying to lift up six people myself. Whereas if I'm constantly hiring somebody that's an expert at something above me, then they're lifting me and my group up.
Technical interviews and coding challenges
What I boil it down to is like, can you do what you say you can do, right? I need to have some sort of test that shows me that you can do what you say you can do. So not this time, but last time I hired, I got to a second interview with a group of people and I had a coding challenge that I gave people, I don't know, 24 or 36 hours or something to do, return it back to me. I got down to the time I was supposed to speak with this individual and he, the person sent me an email one hour in advance and just said, I have nothing. I could not do the exercise. I told you I could do X, Y, Z, and either I overestimated myself or I, you know, he didn't say he was lying, but he basically couldn't do what he said he could do. So I avoided a very large and costly mistake.
I just want to see the depth of your work. Like how far do you take things down? And then the third component of that is there's no perfect candidate and everybody's going to come in with their different strengths and weaknesses. And by doing this coding challenge, I'm learning about you as a candidate to say, where do I need to upscale this person? Where do I need to spend time with this person on day one, prior to this person starting, I'm going to have a plan.
I've read the, you know, the tech world is in the whiteboarding and all that stuff and putting people. The whole idea of practice in sport is to simulate things that you will see in a game, because that's your job, to play games. If I'm having you do something in practice that you're not doing in a game, why is that relevant? Why should we be spending our time doing that? So I kind of see the idea of making somebody code something on a whiteboard while I see some benefits to it. At what point in the game, in this game as you working on my team, are you ever going to stand in front of a whiteboard and do something like that? That's just not how we work. So why would I make somebody do that? Just one man's opinion.
But in saying that, when I do give them a coding challenge, I do put them under a time limit and I do tell them it's coming ahead of time, because that is the job. The job is, it's Friday night and we're playing Saturday and our coach says, hey, I'm struggling with lineup combination or some problem he might have. I'm wondering who should be going. This person's hurt. I'm struggling on who I should put in or lineup decision. What can you give me on that? I have 12 hours to get him that information, the best of my ability. So that is the job.
Influencing decisions and working with scouts
What I've arrived at as my own mental model is like people are people. This is like still a people's business. You're still interacting with team members. So whether you're in the sports or you work at Target or Walmart or whatever Fortune 500 company, the people are still have the same motivations. They still have the same personality traits. It's teamwork. It's getting people, making people in the group feel like they're heard and that their input is is valued, even when that decision might go against what you're recommending.
When we build a model, what does everybody know is that we have things that are in the model. So there's like the known knowns and there's the known unknowns. So there's things that we know exist, but they're not in the model, right? And no model accounts for everything. So something like that might be saying, hey, here's this player. We want to acquire him. He has all these great results. He's going to project out nicely. And then my GM goes down and gets the guy's medical file from the team that he's currently playing on. And he has some sort of degenerative issue and that there's a high likelihood that this person's going to have health problems, you know, and that might affect his performance. So like, that's not in my model. That's not in my report. That's not in my evaluation. It's a known unknown. And when you come to me and say, hey, we're worried about this, I'm not upset about that. I'm like, oh, I didn't know. I don't have that information. Otherwise I can model it, right?
Closing thoughts and resources
You shared that awesome blog post, which I realized is from Alex Gold from the RStudio team as well. I forgot it was too. I was not plugging RStudio. No, I appreciate it because I didn't see it. Now I have to reach out to Alex about that. But I was just curious, are there other resources or if it's books or podcasts or things that you'd recommend to us all?
There's obviously a lot of great work in the public domain too. It's amazing the work people do, again, showcasing their skills or doing blog posts kind of things like Ryan was talking about is just show how data can be fun and how can it be useful and things like that. Showcase your thinking too. That stuff is interesting for people to see. And those are obviously, like I said, the missing components. When you get down to everybody has the skills, what's going to differentiate people?
Well, thank you so much, Ian, for chatting with us. And if people ever have follow-up questions or just want to connect with you, is LinkedIn the best place? Sure. Yeah, you could do that. I think I have all my stuff on there. Another piece of advice too, for maybe the younger people on this call is if you're going to reach out to somebody, just be direct about what you're asking. Sometimes I can't figure out even what people contact me and I just move past it because I don't know what they're asking. Take some time to think about what you're asking. Be direct, be clear, and then I can answer you quickly. You might think you're one person emailing, why isn't this person responding? But if I get a hundred of them, it's hard to get back to a hundred people. The more direct you could be, the quicker I can get back to you and you could be one of the ones out of those hundred that I actually can try to help. I do want to help, trust me, but I need to know how and without having to weed through innuendo, I guess.
Well, thank you so much, Ian, for chatting with us. We really appreciate it and good luck today. I know, or I think you have a game. Yeah, we do. Yeah. Thank you very much. I appreciate it.