Twice weekly, I share proven strategies to help data scientists get noticed, promoted, and valued. No theory — just practical steps to transform your technical expertise into business impact and the freedom to call your own shots.
The Day My Expertise Finally Got Noticed
|
While working as a data scientist in a large organisation, I was once called on to attend a meeting with representatives of a big tech company and multiple senior leaders from my business area. The tech reps were there to sell us a new product. The data scientists had been invited because we were the intended users. Although there were a dozen or more people in the room, I was the only person who came prepared with any questions - 2 1/2 pages of them, to be precise. I let everyone else have their turn, then systematically worked through the questions I'd previously prepared. By the end of the meeting, the tech reps' attention was fully focused on me. I wasn't doing this to show off. I saw it as a part of my job - and I was genuinely interested in the product. But what happened next has stayed with me ever since. I had no financial delegation at that time. But after that meeting, the tech reps treated me as though I did. The executives started asking for my thoughts on whether they should buy the product. In the space of less than an hour, I had gone from being just another back room nerd to one of the key decision-makers for a major purchase. That meeting had minimal impact on my actual level of expertise. But it had a massive impact on how my expertise was perceived by those around me. For the first time, my stakeholders had a public demonstration of my expertise in action. And because they lacked the technical knowledge to evaluate the product themselves, they deferred to the person in the room who clearly did. This is what expert power looks like in practice. Friend-of-the-list Dr Russell Walker recently posted on LinkedIn about the six sources of power within organisations. Expert power, he argues, comes not just from having knowledge and skill, but from "showing your expertise matters for what your stakeholders care about." That's the part that most data scientists miss. The expertise is there, but the demonstration isn't. Preparation and genuine curiosity did more for my organisational influence that day than months of technical work had done before. Not because I suddenly knew more, but because, for the first time, my stakeholders could see exactly how my expertise connected to a decision they needed to make. Expert power isn't about what you know. It's about making sure the right people can see your knowledge at work. Talk again soon, Dr Genevieve Hayes |
Data Science Impact Algorithm
Twice weekly, I share proven strategies to help data scientists get noticed, promoted, and valued. No theory — just practical steps to transform your technical expertise into business impact and the freedom to call your own shots.
When I’m looking for guests for my podcast, the first place I turn is invariably my bookcase. The authors of data science books have already demonstrated their authority in the field to the point of developing their own original IP. That makes them ideally suited to a podcast about data science expertise. And it’s no coincidence that many of those authors started off by writing blogs. It turns out conference organisers do something similar. When Cynthia Dunlop, who helps organise two major...
A couple of years back, I watched a TV series called The Fear Index. The series focused on a hedge-fund manager who had developed an AI system to optimise fund profits. Of course, as you would expect for a TV show - 🚨Spoiler Alert🚨 - everything falls apart when the AI starts taking highly illegal and frequently fatal actions in order to drive the market and achieve its goals. I enjoyed the show immensely, but at the time, felt it was far-fetched. However, recent reports of an OpenAI agent...
It’s no secret that many data scientists chose this profession in part because they enjoyed maths and wanted to avoid writing essays. When I was managing a data team, my team members would happily spend hours writing code. But ask them to write up what they’d done and suddenly everyone was too busy. Getting them to document their results in the form of a report was a lot like pulling teeth. And I understood why - to them, writing felt like a distraction from the “real” work. But over time, I...