Directionally Correct, A People Analytics Podcast

The episode contains genuinely useful concepts around business partnering (translator role, audience analysis, communication principles), data quality challenges, and the tension between speed and intentionality. However, there is substantial filler: lengthy personal anecdotes (cow herding, modeling, orchids), rapid-fire questions about favorite destinations, and extended riffing on manifesto philosophy that doesn't add operational depth. The core insights - audience segmentation, co-creation with HRBPs, data governance challenges - are valuable but scattered amid conversational padding.

“it's kind of that like you, you essentially live in both worlds in order to be effective, right?”

“being able to then bring back to the people analytics team to say, like this number one thing that the business cares about right now, we need to pivot and we need to find ways to answer it”

Sasha articulates competent framing around business partnering as translation work and emphasizes communication/audience analysis, which are somewhat fresh applications to people analytics. However, the core ideas - HR as change management, AI ethics concerns, importance of data quality - are circulating widely in HR tech discourse. The discussion of attractiveness bias and spouse conscientiousness are borrowed research pieces, not original thinking. There is limited contrarian positioning or first-principles rethinking beyond standard business partnering wisdom.

“communication is a two way street. And if the message is not landing with your audience or particular segments of your audience, you have a lot to do with it.”

“you put AI on top of data that is not clean data that's not good”

Sasha is a Director of Analytics Business Partnering at Adobe (a major enterprise), sits on the board of HR Strategy Forum, has published research backgrounds (master's and doctorate in communication), and is actively shipping work at scale. She has genuine practitioner credibility and real operational responsibility. However, she is not a founder or C-suite operator with full P&L accountability, and the episode does not establish whether her specific Adobe initiatives drove measurable business outcomes, limiting the ceiling here.

“my role at Adobe is in analytics business partnering with, restructuring the team”

“I joined the board of, uh, HR Strategy Forum. It's nonprofit professional association that's been around for about 30 years”

The episode lacks concrete numbers, named metrics, and specific business outcomes. Sasha discusses general approaches (co-creation, audience analysis, data governance) but provides minimal named examples of what Adobe actually shipped, how impact was measured, or what specific changes resulted from her work. The discussion of AI and attractiveness bias references research but not proprietary data. The Sanjeev article discussion mentions 70 skills in Claude but is borrowed. Most claims are illustrative but not evidenced with specific timelines, dollar figures, or measurable results.

“we've done that and that's been really successful because we're getting very direct user input”

“so there is tremendous level of insights driven by data engineering, data science, research”

Cole asks reasonable setup questions and attempts genuine follow-ups (the business partner translation question, impact measurement, forward-looking vs. backward-looking), but the conversation often drifts into personal anecdotes and abstract philosophy rather than pressing for specifics. Cole does challenge Sasha lightly on the manifesto and dashboard debate, but mostly allows her to roam. The host could have pushed harder on: what specific metrics changed, how long business partner relationships took to build trust, concrete examples of decisions influenced by her analysis, or friction points she actually encountered. Some opportunities for productive disagreement are left on the table.

“How do you navigate the subject matter expertise part of it, which is you have to be, um, in the data and in the products that you guys have”

“what exactly difference that it made. So I think that's certainly one um, layer”