>A more organic approach would be for teams to start picking up tools and skills for basic data analysis. We used to call it "stats". Doesn't have to be cutting

>A more organic approach would be for teams to start picking up tools and skills for basic data analysis. We used to call it "stats". Doesn't have to be cutting-edge ML stuff to provide value and new opportunities for the practitioners. Of course whatever they start doing, HR and management will pump it up: mining a few hundred megs of csv files all of sudden will get called "big data". Here's my one caveat to this based on personal experience. This happens to be why an entire data science team in one division of a large company quit over the course of a year. If middle/upper management is purely focused on "show value on day one", it's very easy to get stuck in a position where basic stats and building Dashboards for simple data mining becomes the gold standard for what a Data Science team is for. Management develops an addiction to fast data mining projects that look good in PowerPoint, but don't actually deliver much business value because nobody is actually measuring business impact outside of how impressive it sounds. When the Data Science team tries to focus on projects that require more work that deliver more value, they're shot down because they don't fit into the "monthly management update" mentality. You need a good management structure that realizes that quick data mining exercises are a stepping stone to delivering longer term value. They are not the ultimate goal.