|
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 |
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.
In a recent blog post, CFO advisor and friend of the list Lauren Pearl discussed the impact of AI on the age-old software “build vs buy” decision. In short, Lauren argued that AI-driven vibe coding has made building software in-house far more appealing when the stakes are low, but when stakes are high, buying is still the way to go. To quote Lauren: “When you buy software, you don’t just buy the code. You buy a support team, expert-derived flows, tested features, platform trust, regular...
Ten years ago, everyone wanted to be doing machine learning. Go to a data conference - someone was presenting on ML. Advertising a data role - just mention ML and applications would 10X. It was the promise of machine learning that inspired an entire generation of data scientists. I know. I was one of them. And then came the statistic that revealed what many data scientists knew but few wanted to admit: around 90% of ML initiatives never made it to deployment. The ideas were there. The...
Last week, I stepped on the fancy scales at my gym for the first time in four months. You know the ones. They don’t just tell you your weight. They tell you your muscle mass, bone density, basal metabolic rate… Basically, everything short of your star sign. The results were horrifying. Everything had gone backwards. I’d even managed to lose 400 grams of muscle. I’d been training five days a week and made no major changes to my diet. I was lifting heavier weights than ever before. None of it...