I was recently speaking to some data science friends on Slack, and we were discussing projects and war stories. Something that came across was that ‘data science’ projects aren’t always successful.
Somewhere around this discussion a lightbulb went off in my head about some of the problems we have with embarking on data science projects. There’s a certain amount of Cargo cult Data Science and so collectively we as a community – of business people, technologists and executives don’t think deeply enough about the risks and opportunities of projects.
So I had my lightbulb moment and now I share it with everyone.
The one weird trick is to write down risks before embarking on a project.
Here’s some questions you should ask you start a project – preferably gather all data .
- What happens if we don’t do this project? What is the worse case scenario?
- What legal, ethical or reputational risks are there involved if we successfully deliver results with this project?
- What engineering risks are there in the project? Is it possible this could turn into a 2 year engineering project as opposed to a quick win?
- What data risks are there? What kinds of data do we have, and what are we not sure we have? What risks are there in terms of privacy and legal/ ethics?
I’ve found that gathering stakeholders around helps a lot with this, you hear different perspectives and it can help you figure out what the key risks in your project are. I’ve found for instance in the past that ‘lack of data’ killed certain projects. It’s good to clarify that before you spend 3 months on a project.
Try this out and let me know how it works for you! Share your stories with me at myfullname[at]google[dot]com.