As the name suggests, speakers and audiences of the summit are the leaders of data division within a company such as Head of Data and CDO, who are in a decision-making role, and it was a great opportunity to identify the difference between data leaders and data "players" (e.g., data scientist, analyst, ML engineer), and rethink their responsibilities.
In the sessions, there were two particularly important topics:
- How to build data organization(s) within a company, in consideration of diversity.
- How to make real-world data project successful.
Good Data Scientist != Good Data Leader
First of all, a key responsibility of data leaders is to translate business needs into data requirements, and successful data organization and project must be led by those who are capable to accomplish it.
On that point, it is important that good data scientists cannot always be good data leaders; a data scientist is a person who is working on data itself to make the outcomes, whereas a leader is in charge of the more strategic decision-making process before aggregating data and playing with it.
To give an example, in a panel session "How can you organize your data office," Head of Customer Insight, Analytics and Reporting at AXA Investment Managers mentioned that, the biggest challenge at the very initial phase of their data efforts was gathering multiple data sources across the company. We can easily imagine it does require someone to strategically communicate with a variety of stakeholders and carefully plan the whole implementation process.
Meanwhile, Global Head of Data, Analytics & AI at Volkswagen Financial Services emphasized the importance of end-to-end automation of data science and machine learning workflow. Making sure company-wide business requirements is a crucial first step that has to be done by the leaders.
Thus, for the reasons that I heard from the panel, a leader's role is different from what we normally talk about data science.
Enabling Data Scientists to Make Actionable Insights
Once the business problems and data requirements become clear, it's time to pass the baton to the "players" to move forward, and the ultimate goal of data science is to make actionable recommendations for the business personnel.
Importantly, most real-world data-related business problems can be solvable by a combination of simple mathematical formulas and ML models; as Head of Data and Insights at Virgin Atlantic stated in the panel, 99% of data scientists in an organization do not necessarily have to hold a Ph.D. to achieve their goal.
1% of Ph.D.-grade data scientists could help to resolve unique, challenging problems, but we need to consider the balance between model complexity, explainability, and prediction accuracy. Here, an optimal choice should be derived as a consequence of the leader's Biz/Data translation process.
Therefore, data leader's responsibility differs from data scientist's one, and their work helps data scientists perform to the best of their potential for making the value.
As a real-world story, my favorite session at Data Leaders Summit 2019 was "F1 journey to build its own Business Data Analytics capabilities". Since F1 has re-branded in 2017/2018 and changed from a motorsport company to a comprehensive entertainment brand, providing not only the races but online media and gaming content, many data challenges had arisen. Their Senior Analytics Director demonstrated how they overcome the situation, and it was a good example of showing the power of successful data organization and project.
Overall, even though I'm not actually a "data leader", the summit was highly informative and insightful to see the data problems from the business perspective. I can confidently say the inputs become valuable when I think about my career.
Support (Thank you!)
Note that, as an Amazon Associate, I earn from qualifying purchases on amazon.ca.
- Data Are Created, Collected, and Processed by People
- Validate, Validate, and Validate Data. But, in terms of what?
- What Makes a Good Dashboard: The Rise of Augmented Analytics
Last updated: 2022-09-02
Author: Takuya Kitazawa
Takuya Kitazawa is a freelance software developer, minimalistic traveler, ultralight hiker & runner, and craft beer enthusiast. While my area of specialty is in data & AI ethics and machine learning productization, I have worked full-stack throughout the career e.g., as a frontend/backend engineer, OSS developer, technical evangelist, solution architect, data scientist, and product manager. You can find what I am doing lately at my "now" page, and your inquiry is always welcome at [email protected], including comments on my blog posts.
- Opinions are my own and do not represent the views of organizations I am/was belonging to.
- I am doing my best to ensure the accuracy and fair use of the information. However, there might be some errors or biased subjective statements because the main purpose of this blog is to jot down my personal thoughts as soon as possible before conducting an extensive investigation. Visitors understand the limitations and rely on any information at their own risk.
- That said, if there is any issue with the content, please contact me so I can take the necessary action.