deploying a data sciences team -- the promise and the pitfalls
Post on 18-Oct-2014
1.818 views
DESCRIPTION
Intuit formed its first Data Sciences group in 2008. From inception until 2012, Intuit’s data scientists operated from a central organization and leveraged their unique expertise like “consultants” assigned to a specific project and “client” from the business unit. In October, 2012, Intuit began piloting an “embedding” strategy that places a data scientist deep within a business unit product team to use their expertise as part of the team rather than just “consulting” on a project. Since then, the embedding program has grown and currently 6 data scientists/analysts from the central organization have joined product teams across the company. Success has been mixed and in this talk we will describe the pros and cons of the two ways of deploying data scientists within the organization, as well as the key ingredients we found are necessary for great outcomes.TRANSCRIPT
Deploying a Data Sciences Team: The Promise and the Pitfalls
Diane Chang, PhD Senior Data Scientist
Simplify the business of life
2
… or
Why I love embedding
3
4
You’ve hired them, now how do you deploy them?
5
• Centralized team
• Resident in the business
• Embedded in business
6
Data Science
7
My Intuit experience
• 5 years as a data scientist
• First 4 years in “centralized team” mode
• Last year I was embedded for 10 months
… and I loved it!
8
My concerns with centralization
• Single point of contact
• Few direct interactions
• Single source for context
• Feel less a part of the team
9
The first embedding experiment
• Big Data for the Little Guy
• First volunteer
4
+4
+4
3 months
+4
+4
+4
3 months
+4
+4
+4
+4
4 months
The result: A new business with data in its DNA!
10
Being one of the team
• Direct communications
– No “geek speak”
Plus:
• Maintained connection with data science team
• Hallway conversations
• Flash mob
• Extra context -> better product
11
Why I love embedding
• New data “believers”
• Significant impact on a new product
• Learned a lot
• Made new friends
12
And what I learned…
• It’s easy to get disconnected
• Enter with an exit strategy
• Demand can be overwhelming
• Two homes can feel like no home
13
Hey product team - are you ready?
• Well-defined problem with significant business value
• Data is available
• Committed bandwidth from team
• Welcoming – have a buddy
14
Data scientist - do you have what it takes?
• Open to change
• Value learning
• Easily develop personal relationships
• Adaptable
• Translate technical to business terms
∑ ≈ ∏
15
Since the first experiment…
• We are growing the program
– A dozen embedding rotations
• We are still experimenting
– Pods: a team not an individual
• Can play a larger strategic role
• Can offer a variety of skills
16
And me?
• Doing a rotation back in the center
• Improving tools and products that benefit many product teams
• Increasing my skills and knowledge