Hi ,
Before we begin: Next month, I'm teaching 3-5 data scientists my complete process for creating your own high-value data science opportunities in the Data Science Impact Sprint - a 4-week, 1-on-1 coaching
program that will boost your strategic influence and help position you for career advancement. Scroll down to learn more...
They say you should start the job you want before you have it.
Back in 2015, I wanted to be a data science manager.
The problem? Data science was new. Data science managers were virtually unheard of in Melbourne, Australia. And even if a role were advertised, there was no guarantee it would be mine.
So, I took the only option that was left to me. I started the job where I was.
At the time, I was managing a successful BI and Actuarial team.
However, I could see that data science was the future of the business. The question wasn't whether our organisation needed data science capabilities - it was whether my team would build them or another team would.
Instead of waiting for someone to create a data science "dream team" in the future, I created a business case for why my team should start doing data science right now.
I started thinking like a strategic data scientist should. This wasn't theoretical - I actually
implemented the process I now teach:
1. Understand the Business Context
I mapped the key players, business priorities and decisions. The organisation was developing a 5-year plan at that time, so I made sure I knew every detail.
2. Identify High-Value Areas for Business Improvement that Data Science Can Address
Rather than treating data science as a "toy", I sought to identify high-impact business problems only data science could solve. Before writing a single line of code, I identified over 5 specific
areas where data science could create measurable business value.
3. Create a Business-Centric Project Blueprint
I created a comprehensive plan that outlined my ideas, capturing everything the business decision-makers needed to know - from expected outcomes, to resource
requirements and a timeline.
4. Pitch the Blueprint to Management Using the Language of Business
I pitched that plan to the executive team, focusing on business impact, rather than technical details. I spoke their language, not data science jargon, making the strategic value
abundantly clear.