1 year ago
This is the second part of the Data Strategy series. The topic of building a successful Data Science Team is so important, that we decided to expand it into a whole post. In the first part of the series, we explored key points that define a successful data strategy. Now we are going to focus on the elements that make a data team succeed.
Why building a Data Science Team? Companies are realizing that the dream of finding the elusive Data Science Unicorn the candidate that has it all - is impossible or not feasible - they are just too expensive. With growing complexity, it is getting impossible to be good at all that is needed to take the most advantage of the field. It is much more productive to build Data Science Teams with people that have different profiles.
This guide has several audiences in mind:
What Does a Data Science Team Do?
A Data Science Team is the group of people within the company that is in charge of the Data Science Process, from beginning to end. This includes:
Depending on the structure, the size and the capacities of the company, these functions will be performed by one or more individuals. There are no formulas of what is best, it depends on each situation to determine the right mix of people that will maximize results while optimizing the scarce resources that every company has.
Data Analytics vs Data Science Team: what are the roles and responsibilities?
One of the first questions to answer as part of a successful data strategy is whether the focus is going to be on Data Analytics or Data Science. Data Science is a bigger field that encompasses Data Analytics but does not have it as the focus. Hiring Data Scientists to exclusively do the job of a Data Analyst might lead to frustration and inefficient use of resources since in general, Data Scientists' salaries tend to be higher. So here a quick test that will point you in the right direction.
If the answer is no to these questions, your company likely needs to first focus on building a Data Analytics Team. A deep understanding of the status quo from a company is a necessary base for guiding new, more complex models, that should add value. This also manifests in the type of data that is taken as input for the analysis. If your company has a bunch of unmined data, usually in the form of databases, then it is a good idea to start there.
Like anything in life, it does not need to be black or white. Your company might be in a middle stage on its data path, seeking to expand from a purely descriptive type of analysis to a predictive focus or seeking to develop new strategies to gather data. For these situations, it is useful to understand how different data job profiles differ. Creating a mix of these will ensure that you attack the data needs that your company has from different fronts. Here (link to part 1 of Data Ecosystem post) and here (link to part 2 of Data Ecosystem) is a two-part series that we prepared to help you make sense of the Data Science Job Ecosystem.
Setting up a Data Science Team - Where should it be nested within the company?
One of the key determinants of the success of Data Science teams is the right design of their structure within the company. This implies much more than determining where the the team of Data Scientists physically sit. What is at stake is the design of dynamics and interactions both within the Data Science team and with the rest of the members of the company. Accenture developed a very useful scheme of different ways that companies use to organize their Data Science activities within their ecosystems. They accurately describe that three main factors will determine which model is more appropriate, namely the maturity that the Data Analytics teams have, the priorities that companies have and the way of balancing the supply and demand of data analytics capabilities. Each model will foster different characteristics for these three key factors.
Overview of the main organizational models for Data Science Teams:
It is evident that some of these organizational models for Data Science teams just work when the company has a certain size. The strategy chosen needs to be aligned with the dynamics and structure that works for other types of activities. The last two models are a new trend that allows for a lot of flexibility and innovation. There is a centralized team that can help with the implementation with cross-functional complex projects while each unit can also have the flexibility of having their inner strategy without always consulting or depending on other units. The advantage is also that Data Scientists have a centralized body that prevents them from a feeling of isolation.
Managing and retaining the dream team
Once you managed to build a data science team that can deliver data projects from beginning to end, the challenge is to retain them. Having a solid data strategy, as described in the first part of this series, definitely helps. Data Scientist recognize the difficulty of setting a whole strategy that allows for constant innovation. Important points are therefor to prove to have a plan that is truly motivated by the business strategy, backed up with the technological structure that allows for the agility that Data Science requires and with clarity about roles and responsibilities. Moreover, Data Scientists are also motivated by curiosity and engagement. Make everything to ensure a general culture of data within your company and organize events like hackathons or Data Science conferences that give them the opportunity to present their work to the Data Science scene.
No matter how far you are in your data strategy path, we have the experience to help you. Contact us to find the right candidate(s) that will be the perfect fit for your needs.
We took a look at the top skills needed for leadership in the AI age