Mason: Data projects must prove immediate relevance to business goals
Hilary Mason · Hilary Mason // Data Driven NYC 20 // Nov 2013 · Dec 5, 2013 · at 11:43
Hilary Mason, data scientist and former Chief Scientist at bitly, shares her framework for prioritizing data projects at Data Driven NYC.
0:00 / 0:20exact quote · 20.0s
▶ Watch the full episode on YouTube → 720p mp4 · rendered on demand · StarZero watermark
“Assuming we can solve this perfectly, what is the first thing we'll do with it that makes sure it has immediate relevance to the product, or the business, or the system you're building? Because there are a lot of super cool ideas that do not tie directly to the goals of your company, and this one makes sure that there is at least one obvious, good, compelling reason to put your time into this thing.”
quote is from the automated transcript, cleaned for reading: filler sounds and stutters are removed, nothing is rephrased. names can be misheard (the analysis reads context, assessments check outside sources). how →
More from Hilary Mason
Hilary Mason: Startups must understand how their machine learning models work
“Won't speak for the large companies or people who are working on very specific problems, but when you're generally building systems that in a startup environment, it's really important to understand why your system is doing the thing it's doing, or else it's g…”
Mason: Deep learning completely removes the need for domain feature engineering
“In deep learning, you're not doing feature engineering anymore. Nobody cares about what you know about the domain.”
Mason: Sentiment analysis remains fundamentally unsolved due to lacking ground truth
“I think there are a couple of things that everyone thinks are solved problems that are absolutely not, and so something like sentiment analysis is something where we sort of take for granted that you can just plug into an API and get a number back, but this is…”
Hilary Mason: Separating R&D from product rarely works for tech companies
“I have seen companies that successfully separate, ah, research and development as long as everyone still eats lunch together but generally that doesn't seem to be a great approach in that you eventually end up with a research department off in the corner publi…”