I took very different roles and responsibilities while I was doing my corporate data science jobs. They not only gave me a lot of exposure about data science, but also taught me how to manage my managers.
I remember one of the roles very vividly. I was reporting to a person who had never done a data science project or led a data science team before. He was a good person and a good manager in other set-ups, but in a wrong place for leading a data science team (at least temporarily). Majority of his experience before taking up this role was in Sales. Some of the ways of managing people which worked for him in past where not going to work in this setup.
For example, we used to have 2 team meetings in a week, where each one of us updating the rest of the team on what we are working on and what is the plan for rest of the week. Over and above these were individual catch-ups and project related catch-ups. Most of us failed to understand the objectives of those weekly chores.
The situation I have described is definitely not unique. This would be happening in every Organization trying to set up a data science team or trying to move some of their good performers in other roles to lead data science units. Hence, I thought of sharing a few tips for people making these transitions. These tips should help you become a better data science manager, if you have not been in a data science setup before.
Nothing beats this piece of advice. No matter of research can give you the experience you get by being part of the team doing the project. You will understand why selling analytics to a potential can be difficult at times and can take months before the customer gives you a fair chance. It will also help you understand why data cleaning can take, what seems like ages from the outside. Further, implementing an analytics solution can give you its own share of learning – what are the hurdles you can come across? Why do you need to be paranoid about getting the implementation right?
If there is one tip you want to take away from this article – just take this. You can’t lead a data science team effectively until you have spent time (preferably hands-on) working on a project yourself.
While the first tip helps you gain depth into the subject, you also need to understand the breadth of the subject. That is what differentiates an good manager from a brilliant analyst. As a manager, you need to understand which tool and solution is best for what kind of problem.
Does the data demand a big data solution? Or a traditional data science method does the job? Do you continue to automate reporting on Excel or move on to tools like QlikView or Tableau? These are some of the questions, you will face as a manager and the decisions you take, will impact your team members and how they spend their time.
This article might be a good starting point
This is almost a given – you can’t be a good analytics manager, if you are not good at structured thinking. As an analyst, you are expected to put structure to unstructured problems. As a manager, you are expected to excel at putting the structure in place – with in minutes. You would enter into meetings which would lack structure and can only benefit from them, if you are able to put a structure to the discussion.
These articles might help you become better at structured thinking: The art of structured thinking, Tools for improving structured thinking
As a data science manager, you will be expected to tell data based stories. The base expectation is to be good at communicating your thoughts. A good manager should be able to visualize data effectively and present it in a manner that it narrates a coherent story. Here are a couple of examples to get your brain thinking:
The better you get at story telling, the better it would be for your team to sell the solutions.
If you are getting into a data science manager role, you have a lot to learn in coming days. The best way to do this is to create a learning plan and share it with your team. This will not only help them understand what you already know and what you don’t, but also communicate that you are willing to learn the subject.
You can also ask the team members to create their learning plan and share it with the group and have weekly knowledge sharing sessions with in the teams to share your learning / experience.
What do you think about these tips? Do they prepare you to become better at managing a team of analysts or data scientists? If you have any more tips from your experience, please feel free to share them through comments below.
Image Source: iNostix blog
Kunal Jain is the Founder and CEO of Analytics Vidhya, one of the world's leading communities of Al professionals. With over 17 years of experience in the field, Kunal has been instrumental in shaping the global Al landscape. His expertise spans diverse markets, from developed economies like the UK to emerging ones like India, where he has successfully led and delivered complex data-driven solutions. As a recognized thought leader, Kunal has empowered countless individuals to realize their Al ambitions through his visionary approach to Al education and community building. Before founding Analytics Vidhya, Kunal earned both his undergraduate and postgraduate degrees from IIT Bombay and held key roles at Capital One and Aviva Life Insurance across multiple geographies. His passion lies at the intersection of analytics, Al, and fostering a thriving community of data science professionals.
Top 10 Data Analytics Projects with Source Codes
Nikhil Mishra’s Journey to Becoming a Kag...
9 best practices for analytics talent management
How to create a High performance Analytics team?
13 Tips to make you awesome in Data Science / A...
How to become an analytics rockstar?
The art of structured thinking and analyzing
Starting your First Data Science Project? Here ...
Busted! 11 Data Science Myths You Should Avoid ...
DataHack Radio Episode #6: Exploring Techniques...
We use cookies essential for this site to function well. Please click to help us improve its usefulness with additional cookies. Learn about our use of cookies in our Privacy Policy & Cookies Policy.
Show details
This site uses cookies to ensure that you get the best experience possible. To learn more about how we use cookies, please refer to our Privacy Policy & Cookies Policy.
It is needed for personalizing the website.
Expiry: Session
Type: HTTP
This cookie is used to prevent Cross-site request forgery (often abbreviated as CSRF) attacks of the website
Expiry: Session
Type: HTTPS
Preserves the login/logout state of users across the whole site.
Expiry: Session
Type: HTTPS
Preserves users' states across page requests.
Expiry: Session
Type: HTTPS
Google One-Tap login adds this g_state cookie to set the user status on how they interact with the One-Tap modal.
Expiry: 365 days
Type: HTTP
Used by Microsoft Clarity, to store and track visits across websites.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Persists the Clarity User ID and preferences, unique to that site, on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
Expiry: 1 Year
Type: HTTP
Used by Microsoft Clarity, Connects multiple page views by a user into a single Clarity session recording.
Expiry: 1 Day
Type: HTTP
Collects user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Years
Type: HTTP
Use to measure the use of the website for internal analytics
Expiry: 1 Years
Type: HTTP
The cookie is set by embedded Microsoft Clarity scripts. The purpose of this cookie is for heatmap and session recording.
Expiry: 1 Year
Type: HTTP
Collected user data is specifically adapted to the user or device. The user can also be followed outside of the loaded website, creating a picture of the visitor's behavior.
Expiry: 2 Months
Type: HTTP
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected includes the number of visitors, the source where they have come from, and the pages visited in an anonymous form.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics, to store and count pageviews.
Expiry: 399 Days
Type: HTTP
Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit.
Expiry: 1 Day
Type: HTTP
Used to send data to Google Analytics about the visitor's device and behavior. Tracks the visitor across devices and marketing channels.
Expiry: Session
Type: PIXEL
cookies ensure that requests within a browsing session are made by the user, and not by other sites.
Expiry: 6 Months
Type: HTTP
use the cookie when customers want to make a referral from their gmail contacts; it helps auth the gmail account.
Expiry: 2 Years
Type: HTTP
This cookie is set by DoubleClick (which is owned by Google) to determine if the website visitor's browser supports cookies.
Expiry: 1 Year
Type: HTTP
this is used to send push notification using webengage.
Expiry: 1 Year
Type: HTTP
used by webenage to track auth of webenagage.
Expiry: Session
Type: HTTP
Linkedin sets this cookie to registers statistical data on users' behavior on the website for internal analytics.
Expiry: 1 Day
Type: HTTP
Use to maintain an anonymous user session by the server.
Expiry: 1 Year
Type: HTTP
Used as part of the LinkedIn Remember Me feature and is set when a user clicks Remember Me on the device to make it easier for him or her to sign in to that device.
Expiry: 1 Year
Type: HTTP
Used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Used to store information about the time a sync with the AnalyticsSyncHistory cookie took place for users in the Designated Countries.
Expiry: 6 Months
Type: HTTP
Cookie used for Sign-in with Linkedin and/or to allow for the Linkedin follow feature.
Expiry: 6 Months
Type: HTTP
allow for the Linkedin follow feature.
Expiry: 1 Year
Type: HTTP
often used to identify you, including your name, interests, and previous activity.
Expiry: 2 Months
Type: HTTP
Tracks the time that the previous page took to load
Expiry: Session
Type: HTTP
Used to remember a user's language setting to ensure LinkedIn.com displays in the language selected by the user in their settings
Expiry: Session
Type: HTTP
Tracks percent of page viewed
Expiry: Session
Type: HTTP
Indicates the start of a session for Adobe Experience Cloud
Expiry: Session
Type: HTTP
Provides page name value (URL) for use by Adobe Analytics
Expiry: Session
Type: HTTP
Used to retain and fetch time since last visit in Adobe Analytics
Expiry: 6 Months
Type: HTTP
Remembers a user's display preference/theme setting
Expiry: 6 Months
Type: HTTP
Remembers which users have updated their display / theme preferences
Expiry: 6 Months
Type: HTTP
Used by Google Adsense, to store and track conversions.
Expiry: 3 Months
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
Save certain preferences, for example the number of search results per page or activation of the SafeSearch Filter. Adjusts the ads that appear in Google Search.
Expiry: 2 Years
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 6 Hours
Type: HTTP
These cookies are used for the purpose of targeted advertising.
Expiry: 1 Month
Type: HTTP
These cookies are used to gather website statistics, and track conversion rates.
Expiry: 1 Month
Type: HTTP
Aggregate analysis of website visitors
Expiry: 6 Months
Type: HTTP
This cookie is set by Facebook to deliver advertisements when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
Expiry: 4 Months
Type: HTTP
Contains a unique browser and user ID, used for targeted advertising.
Expiry: 2 Months
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 1 Year
Type: HTTP
Used by LinkedIn for tracking the use of embedded services.
Expiry: 1 Day
Type: HTTP
Used by LinkedIn to track the use of embedded services.
Expiry: 6 Months
Type: HTTP
Use these cookies to assign a unique ID when users visit a website.
Expiry: 6 Months
Type: HTTP
These cookies are set by LinkedIn for advertising purposes, including: tracking visitors so that more relevant ads can be presented, allowing users to use the 'Apply with LinkedIn' or the 'Sign-in with LinkedIn' functions, collecting information about how visitors use the site, etc.
Expiry: 6 Months
Type: HTTP
Used to make a probabilistic match of a user's identity outside the Designated Countries
Expiry: 90 Days
Type: HTTP
Used to collect information for analytics purposes.
Expiry: 1 year
Type: HTTP
Used to store session ID for a users session to ensure that clicks from adverts on the Bing search engine are verified for reporting purposes and for personalisation
Expiry: 1 Day
Type: HTTP
Cookie declaration last updated on 24/03/2023 by Analytics Vidhya.
Cookies are small text files that can be used by websites to make a user's experience more efficient. The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies, we need your permission. This site uses different types of cookies. Some cookies are placed by third-party services that appear on our pages. Learn more about who we are, how you can contact us, and how we process personal data in our Privacy Policy.
Edit
Resend OTP
Resend OTP in 45s
Dear Gunal, Excellent tips who can thinking like me to get in to the managerial role in analytics domain. Will follow the tips and update you. Regards kv
Awesome tips - adding to the above - have a customer centric mindset and help in simplifying output assuming every user is a novice
Excellent tips for top jobs for Data scientist. I'm research for data generated by big player e.g. Google , IBM , Facebook etc. what are benefits in the data ecology . When we talk about big data , are these are prominent player or it's just the notion the date been created. Bal