|
Why do stakeholders keep asking data scientists for the wrong analysis? They don't. They're telling you their symptoms, not their problems.
These aren't problems - they're symptoms of deeper issues. But most data scientists take these requests at face value and build solutions that address the symptom, not the root cause. Then they wonder why their technically perfect models sit unused. Decision scientist Prof Jeff Camm has a different approach. He treats business requests like detective work. He starts by asking: "What's disturbing you? What's giving you heartburn?" Then comes the game-changing question: "What do you control that could alleviate those symptoms?" Whatever they can control - that's your real problem to solve. But that's just the beginning. In the latest Value Boost episode of Value Driven Data Science, Jeff walks me through his complete problem-framing framework and reveals advanced techniques for ensuring your analysis addresses real business needs. You'll discover:
11 minutes that could transform how you approach every future project. Listen now on Apple Podcasts or Spotify, or click the link below: 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.
The number one piece of advice I give to data professionals is to have more conversations. Conversations lead to good things. Things like job offers and stronger relationships. But more importantly, the opportunity to deepen your knowledge through learning from the wisdom of others. I owe many of the best opportunities I’ve encountered in my career to proactively seeking them out wherever I can. My podcast is a weekly example of the power of conversation. But if there’s one thing all these...
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...
Like many readers of this newsletter, I identify as a data expert. It took me years of study and hard work to build this expertise, and it’s something that I’m not willing to lose. This is not just because of everything it took to get here, but because my expertise forms an integral part of my identity. And the idea of losing it feels, in many ways, akin to losing a part of who I am. So, when I recently started hearing from data professionals who spoke of slowly losing skills as they...