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.
Do What You're NOT Told (But Someone Should Have Asked)
|
Before any important meeting, I put myself in my stakeholders’ shoes and ask:
Then I have it ready when they ask. I started doing this in my graduate days, as a way to avoid staying back late for last-minute requests. But the career benefits soon became clear: anticipating what stakeholders need - before they ask - creates far greater impact than simply doing what you’re told. Which brings me to a question I was recently asked on LinkedIn: “What do you do if you want to create opportunities through your work, but management isn’t open to innovation and discourages exploratory analysis?” It’s a fair concern. Bad bosses exist. Some organisations actively discourage initiative. But here’s what I’ve learned: even the worst managers rarely discourage staff from making their job easier. The problem isn’t that you’re taking initiative. It’s what kind of initiative you’re taking. Exploratory analysis for its own sake? That’s risky. Your manager sees it as wasted time on work that might not matter. But analysis that solves a problem they’re already worried about? That’s gold. Here’s the difference: “I spent two days exploring our customer data and found some interesting patterns” = initiative without direction “I noticed you’ve been asking about customer retention a lot lately, so I pulled together some analysis that might help” = doing what should have been asked One makes you look like you’re going rogue. The other makes you look indispensable. The key to creating valuable opportunities isn’t doing analysis for its own sake. It’s understanding what your stakeholders actually need and creating work that aligns with those needs - even if they haven’t explicitly asked yet. That’s what my pre-meeting preparation habit taught me: value isn’t created by being clever with data. It’s created by being useful to the people who depend on that data. So, try this before your next meeting: Ask yourself:
Then show up with answers to questions they should have asked. That’s not just good preparation. That’s how you do the work you’re not told to do - but someone should have probably asked for. 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 was 9, I didn’t want to be a data scientist. I wanted to be a radio host. My favourite “game” involved recording episodes of my radio show using an old cassette recorder and blank audio tapes. I would bring on my family and stuffed animals for interviews, then cut to my favourite songs - sometimes sung (badly) by me. So, when I launched Value Driven Data Science three years ago, I saw it as a great way to learn from data scientists I admired, while living out my childhood dream. What I...
“So this is Christmas and what have you done?” - John Lennon It’s that time of year again. The time when work grinds to a halt and everyone tells themselves they’ll “figure it out in the new year.” Then January hits. Nothing changes. Before you know it, another year’s over and you’re scratching your head, wondering how you got so little done. It’s not that you can’t achieve big things in a year. It’s that most people never actually start. Maybe you’ve spent years building technical skills and...
If you think the best use of LLMs in data science is coding, then you’re missing some of the most powerful opportunities. Late last year, I had an important conversation coming up with a key stakeholder who I’d known for years. And when I say important, I mean the sort of conversation that could make or break a career. Let’s just say that this person had a very particular way of responding to situations, and I knew from experience that if I made one false step, the conversation could go...