<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/stylesheet.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:podcast="https://podcastindex.org/namespace/1.0">
  <channel>
    <atom:link rel="self" type="application/rss+xml" href="https://feeds.transistor.fm/the-workops-podcast" title="MP3 Audio"/>
    <atom:link rel="hub" href="https://pubsubhubbub.appspot.com/"/>
    <podcast:podping usesPodping="true"/>
    <title>The WorkOps Podcast</title>
    <generator>Transistor (https://transistor.fm)</generator>
    <itunes:new-feed-url>https://feeds.transistor.fm/the-workops-podcast</itunes:new-feed-url>
    <description>The WorkOps Podcast is your weekly conversation with HR leaders and People Ops practitioners doing the real work.

In every episode we dig into one story. A process that went sideways, a system that just didn't work, and what someone actually did about it. Packed with practical lessons you'll want to bring back to your team. Whether you're supporting 500 employees or 5,000, this is how the best People leaders are building for what comes next.</description>
    <copyright>© 2026 by Kinfolk</copyright>
    <podcast:guid>ca4f6872-8b4e-57a8-85a7-3a16a1dfe037</podcast:guid>
    <podcast:locked>yes</podcast:locked>
    <language>en</language>
    <pubDate>Fri, 12 Jun 2026 15:54:01 -0600</pubDate>
    <lastBuildDate>Fri, 12 Jun 2026 15:54:11 -0600</lastBuildDate>
    <image>
      <url>https://img.transistorcdn.com/YGXCnixjXbtuEszwNWaJFLGoTDQUclqvAERiQEhdUkg/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lMWNj/OTM3ZjEzMWFkMzQw/NjcwMzQyYTI4MTY3/MGRhMC5wbmc.jpg</url>
      <title>The WorkOps Podcast</title>
    </image>
    <itunes:category text="Business"/>
    <itunes:category text="Society &amp; Culture">
      <itunes:category text="Relationships"/>
    </itunes:category>
    <itunes:type>episodic</itunes:type>
    <itunes:author>by Kinfolk</itunes:author>
    <itunes:image href="https://img.transistorcdn.com/YGXCnixjXbtuEszwNWaJFLGoTDQUclqvAERiQEhdUkg/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9lMWNj/OTM3ZjEzMWFkMzQw/NjcwMzQyYTI4MTY3/MGRhMC5wbmc.jpg"/>
    <itunes:summary>The WorkOps Podcast is your weekly conversation with HR leaders and People Ops practitioners doing the real work.

In every episode we dig into one story. A process that went sideways, a system that just didn't work, and what someone actually did about it. Packed with practical lessons you'll want to bring back to your team. Whether you're supporting 500 employees or 5,000, this is how the best People leaders are building for what comes next.</itunes:summary>
    <itunes:subtitle>The WorkOps Podcast is your weekly conversation with HR leaders and People Ops practitioners doing the real work.</itunes:subtitle>
    <itunes:keywords>people operations,workforce operations,HR leadership,people leadership,HR strategy,AI in HR,future of work,HR transformation,workforce planning,change management,employee experience,employee engagement,talent retention,workplace culture,HR technology,HR automation,employee lifecycle,internal communications,CHRO,VP of people</itunes:keywords>
    <itunes:owner>
      <itunes:name>Tanner Green</itunes:name>
      <itunes:email>tanner@growthwizards.io</itunes:email>
    </itunes:owner>
    <itunes:complete>No</itunes:complete>
    <itunes:explicit>No</itunes:explicit>
    <item>
      <title>The hard truth about setting a budget</title>
      <itunes:episode>11</itunes:episode>
      <podcast:episode>11</podcast:episode>
      <itunes:title>The hard truth about setting a budget</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">479af83b-fb25-484d-800c-36b1f01206c4</guid>
      <link>https://share.transistor.fm/s/949ccad9</link>
      <description>
        <![CDATA[<p><strong>Summary</strong></p><p>In this episode of The WorkOps Podcast, Jeet sits down with Ann Watson, Chief People Officer at Cover Genius, to unpack why pay-for-performance creates a structural integrity problem that no amount of manager training can fix. Ann argues that the annual raise has always been a budget decision dressed in performance language, and that pay transparency didn't create the breakdown — it just made it undeniable. She shares how Cover Genius moved to anniversary-based automatic raises, what happened when managers were freed from the comp conversation entirely, and why she still gives low performers their raise every year.</p><p><br><strong><br>Chapters</strong></p><p>00:00 Ann Watson's path to CPO (starting at Starbucks)<br>02:30 The three routes into people leadership and which one dominates right now<br>08:00 AI as a workforce topic, not just a tooling decision<br>13:30 The dysfunctional process Ann identified at every job she's ever had<br>15:30 The breakdown of integrity inside every review cycle<br>19:30 What the research actually says about pay-for-performance<br>23:00 Pay transparency and the structural problem it exposed<br>27:00 How Cover Genius inherited a comp quirk and leaned into it<br>29:30 Building the anniversary raise system for 700 global employees<br>32:00 The low-performer objection and loading the seat <br>35:00 AI in compensation: the accidental flight risk catch</p><p><strong></strong></p><p>Takeaways</p><ul><li>Pay-for-performance is a budget mechanism, and calling it a performance signal is where the integrity breakdown starts.</li><li>Managers who can't explain the comp process aren't failing — they've been handed something structurally unexplainable.</li><li>Anniversary-based raises remove the manager from a conversation they never should have owned.</li><li>Raising the low performer's salary maintains the market rate of the seat, not the person — so you can hire well when you're ready.</li><li>When a manager objects to a low performer's raise, that objection is often a performance conversation that's overdue.</li></ul><p><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/ann-watson-5404a48/">https://www.linkedin.com/in/ann-watson-5404a48/</a><br>Website: <a href="https://covergenius.com/">https://covergenius.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong></p><p>In this episode of The WorkOps Podcast, Jeet sits down with Ann Watson, Chief People Officer at Cover Genius, to unpack why pay-for-performance creates a structural integrity problem that no amount of manager training can fix. Ann argues that the annual raise has always been a budget decision dressed in performance language, and that pay transparency didn't create the breakdown — it just made it undeniable. She shares how Cover Genius moved to anniversary-based automatic raises, what happened when managers were freed from the comp conversation entirely, and why she still gives low performers their raise every year.</p><p><br><strong><br>Chapters</strong></p><p>00:00 Ann Watson's path to CPO (starting at Starbucks)<br>02:30 The three routes into people leadership and which one dominates right now<br>08:00 AI as a workforce topic, not just a tooling decision<br>13:30 The dysfunctional process Ann identified at every job she's ever had<br>15:30 The breakdown of integrity inside every review cycle<br>19:30 What the research actually says about pay-for-performance<br>23:00 Pay transparency and the structural problem it exposed<br>27:00 How Cover Genius inherited a comp quirk and leaned into it<br>29:30 Building the anniversary raise system for 700 global employees<br>32:00 The low-performer objection and loading the seat <br>35:00 AI in compensation: the accidental flight risk catch</p><p><strong></strong></p><p>Takeaways</p><ul><li>Pay-for-performance is a budget mechanism, and calling it a performance signal is where the integrity breakdown starts.</li><li>Managers who can't explain the comp process aren't failing — they've been handed something structurally unexplainable.</li><li>Anniversary-based raises remove the manager from a conversation they never should have owned.</li><li>Raising the low performer's salary maintains the market rate of the seat, not the person — so you can hire well when you're ready.</li><li>When a manager objects to a low performer's raise, that objection is often a performance conversation that's overdue.</li></ul><p><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/ann-watson-5404a48/">https://www.linkedin.com/in/ann-watson-5404a48/</a><br>Website: <a href="https://covergenius.com/">https://covergenius.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 09 Jun 2026 13:45:33 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/949ccad9/8f889dc6.mp3" length="36702630" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/1ToruIQ47cRXy5PZB6u00KFyOhOp7ClwIadPDoEZyZ8/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hNTlh/ZTEwNjExNjg3MWNh/ZDE4YmRjMGJjMmJm/YTI1NC5wbmc.jpg"/>
      <itunes:duration>2291</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong></p><p>In this episode of The WorkOps Podcast, Jeet sits down with Ann Watson, Chief People Officer at Cover Genius, to unpack why pay-for-performance creates a structural integrity problem that no amount of manager training can fix. Ann argues that the annual raise has always been a budget decision dressed in performance language, and that pay transparency didn't create the breakdown — it just made it undeniable. She shares how Cover Genius moved to anniversary-based automatic raises, what happened when managers were freed from the comp conversation entirely, and why she still gives low performers their raise every year.</p><p><br><strong><br>Chapters</strong></p><p>00:00 Ann Watson's path to CPO (starting at Starbucks)<br>02:30 The three routes into people leadership and which one dominates right now<br>08:00 AI as a workforce topic, not just a tooling decision<br>13:30 The dysfunctional process Ann identified at every job she's ever had<br>15:30 The breakdown of integrity inside every review cycle<br>19:30 What the research actually says about pay-for-performance<br>23:00 Pay transparency and the structural problem it exposed<br>27:00 How Cover Genius inherited a comp quirk and leaned into it<br>29:30 Building the anniversary raise system for 700 global employees<br>32:00 The low-performer objection and loading the seat <br>35:00 AI in compensation: the accidental flight risk catch</p><p><strong></strong></p><p>Takeaways</p><ul><li>Pay-for-performance is a budget mechanism, and calling it a performance signal is where the integrity breakdown starts.</li><li>Managers who can't explain the comp process aren't failing — they've been handed something structurally unexplainable.</li><li>Anniversary-based raises remove the manager from a conversation they never should have owned.</li><li>Raising the low performer's salary maintains the market rate of the seat, not the person — so you can hire well when you're ready.</li><li>When a manager objects to a low performer's raise, that objection is often a performance conversation that's overdue.</li></ul><p><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/ann-watson-5404a48/">https://www.linkedin.com/in/ann-watson-5404a48/</a><br>Website: <a href="https://covergenius.com/">https://covergenius.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations,hr technology,future of work,pay for performance,compensation strategy,anniversary raises,manager compensation,pay transparency,ann watson,cover genius,flight risk detection,ai in hr,global compensation,candor iq,performance management,how to fix pay for performance,pay transparency compliance,should managers own compensation,hr compensation philosophy,ai compensation tools</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/949ccad9/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>What makes AI actually stick at a 750-person company</title>
      <itunes:episode>10</itunes:episode>
      <podcast:episode>10</podcast:episode>
      <itunes:title>What makes AI actually stick at a 750-person company</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">e0b4447a-4095-4b95-9c32-8a1234668cc5</guid>
      <link>https://share.transistor.fm/s/c1a0f525</link>
      <description>
        <![CDATA[<p><strong>Summary</strong></p><p>On The WorkOps Podcast, Jean Parchewsky, VP of People Operations at Vendasta, makes a case most AI conversations miss: whether AI takes hold in your company is decided at the hiring table, not in the tooling budget. She traces it back to a training binder that optimized for terminations over hiring, the "hire slow, fire fast" principle she built in response, and the behavior-first "ideal employee profile" her team uses today. Then she shows how that same hiring discipline is what made AI adoption stick, through a citizen developer program, a searchable build board, and a culture where sharing your failures out loud is the norm. Essential listening for any People leader who has been asked to "roll out AI."</p><p><strong>Chapters</strong></p><p>00:00 Why Jean never planned a career in HR</p><p>03:50 The binder that optimized for firing, not hiring</p><p>06:00 Hire slow, fire fast</p><p>07:30 The bar raiser: never interview hungry</p><p>11:00 The ideal employee profile: hiring for behavior</p><p>13:20 Why AI adoption is a culture problem</p><p>14:10 Citizen developers and the build board</p><p>18:30 Putting AI enablement in People Ops, not IT</p><p>23:00 Pepper and the rise of AI "employees"</p><p>26:00 One piece of advice: just jump in</p><p><strong>Takeaways</strong></p><p>Optimizing HR for legal risk instead of the team can quietly cost you your best people.</p><p>Hire slow and fire fast: spend your effort choosing the right person, and be honest quickly when it isn't working.</p><p>Hiring for behaviors rather than skills builds the culture everything else depends on.</p><p>Stalled AI adoption is usually a culture problem, not a tool problem.</p><p>AI enablement belongs close to the work, in People Ops, where it becomes workflow change instead of better emails.</p><p><br><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/jean-parchewsky/">https://www.linkedin.com/in/jean-parchewsky/</a><br>Website: <a href="https://www.vendasta.com/">https://www.vendasta.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong></p><p>On The WorkOps Podcast, Jean Parchewsky, VP of People Operations at Vendasta, makes a case most AI conversations miss: whether AI takes hold in your company is decided at the hiring table, not in the tooling budget. She traces it back to a training binder that optimized for terminations over hiring, the "hire slow, fire fast" principle she built in response, and the behavior-first "ideal employee profile" her team uses today. Then she shows how that same hiring discipline is what made AI adoption stick, through a citizen developer program, a searchable build board, and a culture where sharing your failures out loud is the norm. Essential listening for any People leader who has been asked to "roll out AI."</p><p><strong>Chapters</strong></p><p>00:00 Why Jean never planned a career in HR</p><p>03:50 The binder that optimized for firing, not hiring</p><p>06:00 Hire slow, fire fast</p><p>07:30 The bar raiser: never interview hungry</p><p>11:00 The ideal employee profile: hiring for behavior</p><p>13:20 Why AI adoption is a culture problem</p><p>14:10 Citizen developers and the build board</p><p>18:30 Putting AI enablement in People Ops, not IT</p><p>23:00 Pepper and the rise of AI "employees"</p><p>26:00 One piece of advice: just jump in</p><p><strong>Takeaways</strong></p><p>Optimizing HR for legal risk instead of the team can quietly cost you your best people.</p><p>Hire slow and fire fast: spend your effort choosing the right person, and be honest quickly when it isn't working.</p><p>Hiring for behaviors rather than skills builds the culture everything else depends on.</p><p>Stalled AI adoption is usually a culture problem, not a tool problem.</p><p>AI enablement belongs close to the work, in People Ops, where it becomes workflow change instead of better emails.</p><p><br><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/jean-parchewsky/">https://www.linkedin.com/in/jean-parchewsky/</a><br>Website: <a href="https://www.vendasta.com/">https://www.vendasta.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Thu, 04 Jun 2026 15:31:49 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/c1a0f525/6dbd07a0.mp3" length="27704272" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/rOcgj5DcMgz3UBFank5V1iNQ6a8wh8SMeFgTqrbCeAk/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS82ZDM2/MmQwZGZmMTgxNWE1/ZmY4NzE0NmIzYmE3/NGIyNy5wbmc.jpg"/>
      <itunes:duration>1729</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong></p><p>On The WorkOps Podcast, Jean Parchewsky, VP of People Operations at Vendasta, makes a case most AI conversations miss: whether AI takes hold in your company is decided at the hiring table, not in the tooling budget. She traces it back to a training binder that optimized for terminations over hiring, the "hire slow, fire fast" principle she built in response, and the behavior-first "ideal employee profile" her team uses today. Then she shows how that same hiring discipline is what made AI adoption stick, through a citizen developer program, a searchable build board, and a culture where sharing your failures out loud is the norm. Essential listening for any People leader who has been asked to "roll out AI."</p><p><strong>Chapters</strong></p><p>00:00 Why Jean never planned a career in HR</p><p>03:50 The binder that optimized for firing, not hiring</p><p>06:00 Hire slow, fire fast</p><p>07:30 The bar raiser: never interview hungry</p><p>11:00 The ideal employee profile: hiring for behavior</p><p>13:20 Why AI adoption is a culture problem</p><p>14:10 Citizen developers and the build board</p><p>18:30 Putting AI enablement in People Ops, not IT</p><p>23:00 Pepper and the rise of AI "employees"</p><p>26:00 One piece of advice: just jump in</p><p><strong>Takeaways</strong></p><p>Optimizing HR for legal risk instead of the team can quietly cost you your best people.</p><p>Hire slow and fire fast: spend your effort choosing the right person, and be honest quickly when it isn't working.</p><p>Hiring for behaviors rather than skills builds the culture everything else depends on.</p><p>Stalled AI adoption is usually a culture problem, not a tool problem.</p><p>AI enablement belongs close to the work, in People Ops, where it becomes workflow change instead of better emails.</p><p><br><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/jean-parchewsky/">https://www.linkedin.com/in/jean-parchewsky/</a><br>Website: <a href="https://www.vendasta.com/">https://www.vendasta.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations,hr operations,ai for hr,workforce operations,hire slow fire fast,ideal employee profile,behavioral hiring,ai adoption,citizen developer program,ai enablement,m-shaped workers,build board,ai employees,hr automation,jean parchewsky,vendasta,how to drive ai adoption,hiring for culture fit,ai vs hr jobs,people ops leadership</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/c1a0f525/transcript.txt" type="text/plain"/>
    </item>
    <item>
      <title>How to Separate the Why From the What in HR</title>
      <itunes:episode>9</itunes:episode>
      <podcast:episode>9</podcast:episode>
      <itunes:title>How to Separate the Why From the What in HR</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">c9666620-87ce-42fd-bdff-ca103acb05b2</guid>
      <link>https://share.transistor.fm/s/e1a1d760</link>
      <description>
        <![CDATA[<p><strong>Summary<br></strong>On this episode of The WorkOps Podcast, Jeet sits down with William West, VP People at Wrapbook, to dig into what happens when HR leaders stop trying to do everything in one place. William shares how a 20-plus-hour calibration process became six hours by separating ratings conversations from development conversations entirely. He also makes the case that HR's distinct job in an AI transformation isn't governing tools — it's owning the human argument for why the change matters. And in his closing remarks, he offers a frame on vulnerability that redefines what effective People leadership looks like right now.</p><p><strong><br>Chapters<br></strong>00:00 William West's path from nonprofit HR to VP People at Wrapbook<br>04:00 How HR changes across sectors: pace, complexity, and scale<br>07:30 The calibration problem: 20-plus hours and still unclear<br>12:30 The fix: reading instead of explaining<br>16:30 Separating calibration from development, permanently<br>21:00 AI and human connection: what the technology is actually for<br>25:00 Who leads AI adoption, and why HR owns the why<br>29:00 Vulnerability as a change management strategy</p><p><strong><br>Takeaways</strong></p><ol><li>Calibration and development are two different conversations with different goals — combining them makes both worse.</li><li>Switching from verbal summaries to a read-and-discuss format cut Wrapbook's calibration from 20-plus hours to around six.</li><li>HR's distinct role in an AI transformation is owning the why, not governing the tooling; technical teams are better positioned for the what.</li><li>Late adopters don't move without context-specific reasons; the leader closest to people in each function is best positioned to provide them.</li><li>Naming openly that you feel behind on AI creates space for others to start learning instead of waiting for certainty.<p></p></li></ol><p><br><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/williamcwest/">https://www.linkedin.com/in/williamcwest/</a><br>Website: <a href="https://www.wrapbook.com/">https://www.wrapbook.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary<br></strong>On this episode of The WorkOps Podcast, Jeet sits down with William West, VP People at Wrapbook, to dig into what happens when HR leaders stop trying to do everything in one place. William shares how a 20-plus-hour calibration process became six hours by separating ratings conversations from development conversations entirely. He also makes the case that HR's distinct job in an AI transformation isn't governing tools — it's owning the human argument for why the change matters. And in his closing remarks, he offers a frame on vulnerability that redefines what effective People leadership looks like right now.</p><p><strong><br>Chapters<br></strong>00:00 William West's path from nonprofit HR to VP People at Wrapbook<br>04:00 How HR changes across sectors: pace, complexity, and scale<br>07:30 The calibration problem: 20-plus hours and still unclear<br>12:30 The fix: reading instead of explaining<br>16:30 Separating calibration from development, permanently<br>21:00 AI and human connection: what the technology is actually for<br>25:00 Who leads AI adoption, and why HR owns the why<br>29:00 Vulnerability as a change management strategy</p><p><strong><br>Takeaways</strong></p><ol><li>Calibration and development are two different conversations with different goals — combining them makes both worse.</li><li>Switching from verbal summaries to a read-and-discuss format cut Wrapbook's calibration from 20-plus hours to around six.</li><li>HR's distinct role in an AI transformation is owning the why, not governing the tooling; technical teams are better positioned for the what.</li><li>Late adopters don't move without context-specific reasons; the leader closest to people in each function is best positioned to provide them.</li><li>Naming openly that you feel behind on AI creates space for others to start learning instead of waiting for certainty.<p></p></li></ol><p><br><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/williamcwest/">https://www.linkedin.com/in/williamcwest/</a><br>Website: <a href="https://www.wrapbook.com/">https://www.wrapbook.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 02 Jun 2026 11:46:14 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/e1a1d760/ea2234a0.mp3" length="30064735" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/CEvCAqygnV9w9dFIDDRT8WcrjS0juRw_55qN-gzjxuI/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8wZDI0/M2M4N2FhNjhjMTE1/ZDI4OGU4YTUyZTE1/OTAzZi5wbmc.jpg"/>
      <itunes:duration>1877</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary<br></strong>On this episode of The WorkOps Podcast, Jeet sits down with William West, VP People at Wrapbook, to dig into what happens when HR leaders stop trying to do everything in one place. William shares how a 20-plus-hour calibration process became six hours by separating ratings conversations from development conversations entirely. He also makes the case that HR's distinct job in an AI transformation isn't governing tools — it's owning the human argument for why the change matters. And in his closing remarks, he offers a frame on vulnerability that redefines what effective People leadership looks like right now.</p><p><strong><br>Chapters<br></strong>00:00 William West's path from nonprofit HR to VP People at Wrapbook<br>04:00 How HR changes across sectors: pace, complexity, and scale<br>07:30 The calibration problem: 20-plus hours and still unclear<br>12:30 The fix: reading instead of explaining<br>16:30 Separating calibration from development, permanently<br>21:00 AI and human connection: what the technology is actually for<br>25:00 Who leads AI adoption, and why HR owns the why<br>29:00 Vulnerability as a change management strategy</p><p><strong><br>Takeaways</strong></p><ol><li>Calibration and development are two different conversations with different goals — combining them makes both worse.</li><li>Switching from verbal summaries to a read-and-discuss format cut Wrapbook's calibration from 20-plus hours to around six.</li><li>HR's distinct role in an AI transformation is owning the why, not governing the tooling; technical teams are better positioned for the what.</li><li>Late adopters don't move without context-specific reasons; the leader closest to people in each function is best positioned to provide them.</li><li>Naming openly that you feel behind on AI creates space for others to start learning instead of waiting for certainty.<p></p></li></ol><p><br><strong>Connect with the Guest<br></strong>LinkedIn: <a href="https://www.linkedin.com/in/williamcwest/">https://www.linkedin.com/in/williamcwest/</a><br>Website: <a href="https://www.wrapbook.com/">https://www.wrapbook.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations,hr leadership,workops,calibration process,performance review calibration,talent review,ai in hr,hr ai adoption,william west,wrapbook,ashby ats,ai notetaker,hr change management,ai transformation,how to run calibration meetings,performance management efficiency,people leader ai strategy,hr team leadership,read-and-discuss calibration,separating calibration from development</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/e1a1d760/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/e1a1d760/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>Context is the new currency for HR</title>
      <itunes:episode>8</itunes:episode>
      <podcast:episode>8</podcast:episode>
      <itunes:title>Context is the new currency for HR</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">8d3388b7-43c3-414c-afb3-b6f35d9fd663</guid>
      <link>https://share.transistor.fm/s/78756c99</link>
      <description>
        <![CDATA[<p><strong>Summary</strong><br>A top performer walks out the door at Qualtrics holding an outside offer for double their salary. Michael MacArthur, then Head of People, has a choice: pretend the market is wrong, or admit the comp process was. His read, years later from the COO seat at Recharge: the 2x counter-offer isn't a market signal. It's an audit finding.</p><p>This is one of the cleanest diagnostics we've heard for whether a comp process is really working. And it's the same logic Michael applies to AI, engagement, and the build-versus-buy questions every HR leader is wrestling with right now. The unifying argument: context, not better tools, is the layer that separates the HR teams winning with AI from the ones spinning cycles.</p><p><br><strong>Timestamps</strong><br>01:00 Michael's path from sales comp to head of people at Qualtrics to COO at Recharge<br>03:00 The Qualtrics dysfunction: forced curves and 18-month time-in-seat gates<br>04:00 The "double their salary" diagnostic signal for a broken comp process<br>06:30 Recharge's fix: 6-month cash cycle, no forced curve, multi-level calibration<br>10:00 Process transparency versus salary transparency<br>13:00 Nectar's anonymous follow-up and the context thesis for AI in HR<br>14:30 Why Anthropic's engagement score doesn't matter to Recharge<br>16:00 Build versus buy on the people side: when trust outweighs context<br>21:30 The CEO move that put Recharge's exec team on terminals<br>23:00 Audit the workflow before you prompt the model</p><p><br><strong>Takeaways</strong><br>- The fastest test that your comp process is broken: a leaving employee getting offered double their current salary at the next job.<br>- Forced curves and time-in-seat promotion gates work at 250 employees. They quietly stop working at 2,500.<br>- AI value in HR shows up in context-gathering, not dashboards. Anonymous follow-up conversations beat static survey scores.<br>- Internal-historical engagement trends beat external benchmarks. Anthropic's engagement score doesn't tell you what's happening on your team.<br>- Audit the workflow before you prompt the model. Most failed AI projects in HR are unmapped-workflow problems, not tooling problems.</p><p><br><strong>Connect with the Guest</strong><br>LinkedIn: <a href="https://www.linkedin.com/in/mimcarthur/">https://www.linkedin.com/in/mimcarthur/</a><br>Recharge: <a href="https://getrecharge.com/about/">https://getrecharge.com/about/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong><br>A top performer walks out the door at Qualtrics holding an outside offer for double their salary. Michael MacArthur, then Head of People, has a choice: pretend the market is wrong, or admit the comp process was. His read, years later from the COO seat at Recharge: the 2x counter-offer isn't a market signal. It's an audit finding.</p><p>This is one of the cleanest diagnostics we've heard for whether a comp process is really working. And it's the same logic Michael applies to AI, engagement, and the build-versus-buy questions every HR leader is wrestling with right now. The unifying argument: context, not better tools, is the layer that separates the HR teams winning with AI from the ones spinning cycles.</p><p><br><strong>Timestamps</strong><br>01:00 Michael's path from sales comp to head of people at Qualtrics to COO at Recharge<br>03:00 The Qualtrics dysfunction: forced curves and 18-month time-in-seat gates<br>04:00 The "double their salary" diagnostic signal for a broken comp process<br>06:30 Recharge's fix: 6-month cash cycle, no forced curve, multi-level calibration<br>10:00 Process transparency versus salary transparency<br>13:00 Nectar's anonymous follow-up and the context thesis for AI in HR<br>14:30 Why Anthropic's engagement score doesn't matter to Recharge<br>16:00 Build versus buy on the people side: when trust outweighs context<br>21:30 The CEO move that put Recharge's exec team on terminals<br>23:00 Audit the workflow before you prompt the model</p><p><br><strong>Takeaways</strong><br>- The fastest test that your comp process is broken: a leaving employee getting offered double their current salary at the next job.<br>- Forced curves and time-in-seat promotion gates work at 250 employees. They quietly stop working at 2,500.<br>- AI value in HR shows up in context-gathering, not dashboards. Anonymous follow-up conversations beat static survey scores.<br>- Internal-historical engagement trends beat external benchmarks. Anthropic's engagement score doesn't tell you what's happening on your team.<br>- Audit the workflow before you prompt the model. Most failed AI projects in HR are unmapped-workflow problems, not tooling problems.</p><p><br><strong>Connect with the Guest</strong><br>LinkedIn: <a href="https://www.linkedin.com/in/mimcarthur/">https://www.linkedin.com/in/mimcarthur/</a><br>Recharge: <a href="https://getrecharge.com/about/">https://getrecharge.com/about/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 26 May 2026 07:52:17 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/78756c99/bc1e3350.mp3" length="25426626" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/_CQUtcU1BFUEZ3uxU9dE_4JlUClH8ODfGpquv_8RmMk/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8xZTc5/NjE4NzRjYmVjY2E1/OTQ0ZGVhMmUzYTE1/NjBhZC5wbmc.jpg"/>
      <itunes:duration>1586</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong><br>A top performer walks out the door at Qualtrics holding an outside offer for double their salary. Michael MacArthur, then Head of People, has a choice: pretend the market is wrong, or admit the comp process was. His read, years later from the COO seat at Recharge: the 2x counter-offer isn't a market signal. It's an audit finding.</p><p>This is one of the cleanest diagnostics we've heard for whether a comp process is really working. And it's the same logic Michael applies to AI, engagement, and the build-versus-buy questions every HR leader is wrestling with right now. The unifying argument: context, not better tools, is the layer that separates the HR teams winning with AI from the ones spinning cycles.</p><p><br><strong>Timestamps</strong><br>01:00 Michael's path from sales comp to head of people at Qualtrics to COO at Recharge<br>03:00 The Qualtrics dysfunction: forced curves and 18-month time-in-seat gates<br>04:00 The "double their salary" diagnostic signal for a broken comp process<br>06:30 Recharge's fix: 6-month cash cycle, no forced curve, multi-level calibration<br>10:00 Process transparency versus salary transparency<br>13:00 Nectar's anonymous follow-up and the context thesis for AI in HR<br>14:30 Why Anthropic's engagement score doesn't matter to Recharge<br>16:00 Build versus buy on the people side: when trust outweighs context<br>21:30 The CEO move that put Recharge's exec team on terminals<br>23:00 Audit the workflow before you prompt the model</p><p><br><strong>Takeaways</strong><br>- The fastest test that your comp process is broken: a leaving employee getting offered double their current salary at the next job.<br>- Forced curves and time-in-seat promotion gates work at 250 employees. They quietly stop working at 2,500.<br>- AI value in HR shows up in context-gathering, not dashboards. Anonymous follow-up conversations beat static survey scores.<br>- Internal-historical engagement trends beat external benchmarks. Anthropic's engagement score doesn't tell you what's happening on your team.<br>- Audit the workflow before you prompt the model. Most failed AI projects in HR are unmapped-workflow problems, not tooling problems.</p><p><br><strong>Connect with the Guest</strong><br>LinkedIn: <a href="https://www.linkedin.com/in/mimcarthur/">https://www.linkedin.com/in/mimcarthur/</a><br>Recharge: <a href="https://getrecharge.com/about/">https://getrecharge.com/about/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>workforce operations,people operations,ai for hr,compensation strategy,comp calibration,forced ratings curve,promotion process,engagement surveys,nectar engagement tool,build versus buy hr tech,people ops to coo,context in hr,hr automation,pay transparency,hr systems,chro,vp people operations,head of people,coo,hr leadership</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/78756c99/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/78756c99/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>How to Fund Your HR Transformation</title>
      <itunes:episode>7</itunes:episode>
      <podcast:episode>7</podcast:episode>
      <itunes:title>How to Fund Your HR Transformation</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">ad2e7ece-6a10-40e5-90f2-c78564132175</guid>
      <link>https://share.transistor.fm/s/b6c873d4</link>
      <description>
        <![CDATA[<p><strong>Summary</strong></p><p>In this episode of The WorkOps Podcast, Jeet sits down with Weston Fillman, Director of People Operations and Employee Relations at 1Password, to unpack what it actually takes to get an HR transformation funded, and what changes when AI enters the room. Wes describes the months of pre-work that won him more executive budget than he asked for at a 10,000-person enterprise tech company, the reframe he'd apply to the same project today (people systems as infrastructure, not engagement), and the role-redesign conversations he's having on his team at 1Password as AI starts to automate the operational layer of HR ops. A field guide for any People leader heading into their next budget cycle.</p><p><br><strong><br>Timestamps</strong></p><p>00:00 Welcome and Wes's career path (TFA kindergarten to 1Password)</p><p>02:45 Inheriting a broken hiring process at a 10,000-person company</p><p>07:00 "You can build a new house, but the floor plan's wrong"</p><p>08:00 The structured plan, executive buy-in, and a budget bigger than expected</p><p>11:00 Sideways socialization: leading without authority across HR peers</p><p>13:30 1Password rolls out org-wide agent-building, and modeling AI as a leader</p><p>17:30 Build vs. buy in 2026 (and why it's really build AND buy)</p><p>22:30 The role redesign conversation: AI rewrites the JD, doesn't cut the role</p><p>26:00 The reframe Wes would apply today: people systems as infrastructure</p><p>30:00 Where People leaders should start their own AI journey</p><p><br><strong><br>Takeaways</strong></p><p>- HR transformation budgets are won in the months of pre-work before the e-staff ask, not in the room itself.</p><p>- The reframe from "employee experience" to "business infrastructure" is the single change that turns the same HR project from nice-to-have into board-level fundable.</p><p>- AI lands well when leaders treat it as a role-redesign conversation, not a layoff conversation. Most operational work was never on the JD anyway.</p><p>- Cross-functional buy-in (sideways across peer HR leaders) matters as much as executive sponsorship for any large People transformation.</p><p>- The best AI on-ramp for an individual contributor is to start with the work they're not great at, not the work they already excel at.</p><p><br><strong><br>Connect with the Guest<br></strong>Weston Fillman on LinkedIn: <a href="https://www.linkedin.com/in/westonfillman/">https://www.linkedin.com/in/westonfillman/</a><br>1Password: <a href="https://1password.com/">https://1password.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong></p><p>In this episode of The WorkOps Podcast, Jeet sits down with Weston Fillman, Director of People Operations and Employee Relations at 1Password, to unpack what it actually takes to get an HR transformation funded, and what changes when AI enters the room. Wes describes the months of pre-work that won him more executive budget than he asked for at a 10,000-person enterprise tech company, the reframe he'd apply to the same project today (people systems as infrastructure, not engagement), and the role-redesign conversations he's having on his team at 1Password as AI starts to automate the operational layer of HR ops. A field guide for any People leader heading into their next budget cycle.</p><p><br><strong><br>Timestamps</strong></p><p>00:00 Welcome and Wes's career path (TFA kindergarten to 1Password)</p><p>02:45 Inheriting a broken hiring process at a 10,000-person company</p><p>07:00 "You can build a new house, but the floor plan's wrong"</p><p>08:00 The structured plan, executive buy-in, and a budget bigger than expected</p><p>11:00 Sideways socialization: leading without authority across HR peers</p><p>13:30 1Password rolls out org-wide agent-building, and modeling AI as a leader</p><p>17:30 Build vs. buy in 2026 (and why it's really build AND buy)</p><p>22:30 The role redesign conversation: AI rewrites the JD, doesn't cut the role</p><p>26:00 The reframe Wes would apply today: people systems as infrastructure</p><p>30:00 Where People leaders should start their own AI journey</p><p><br><strong><br>Takeaways</strong></p><p>- HR transformation budgets are won in the months of pre-work before the e-staff ask, not in the room itself.</p><p>- The reframe from "employee experience" to "business infrastructure" is the single change that turns the same HR project from nice-to-have into board-level fundable.</p><p>- AI lands well when leaders treat it as a role-redesign conversation, not a layoff conversation. Most operational work was never on the JD anyway.</p><p>- Cross-functional buy-in (sideways across peer HR leaders) matters as much as executive sponsorship for any large People transformation.</p><p>- The best AI on-ramp for an individual contributor is to start with the work they're not great at, not the work they already excel at.</p><p><br><strong><br>Connect with the Guest<br></strong>Weston Fillman on LinkedIn: <a href="https://www.linkedin.com/in/westonfillman/">https://www.linkedin.com/in/westonfillman/</a><br>1Password: <a href="https://1password.com/">https://1password.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 19 May 2026 08:00:00 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/b6c873d4/554c53b0.mp3" length="32227154" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/S24yUK3nNXk2MeuppfB004ND73WggzveqQXSlFt7pc0/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9hNTkz/ZWEyMGMyNzJjMWIz/Y2ZmOTczNGNmZmZl/YjZlNi5wbmc.jpg"/>
      <itunes:duration>2011</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong></p><p>In this episode of The WorkOps Podcast, Jeet sits down with Weston Fillman, Director of People Operations and Employee Relations at 1Password, to unpack what it actually takes to get an HR transformation funded, and what changes when AI enters the room. Wes describes the months of pre-work that won him more executive budget than he asked for at a 10,000-person enterprise tech company, the reframe he'd apply to the same project today (people systems as infrastructure, not engagement), and the role-redesign conversations he's having on his team at 1Password as AI starts to automate the operational layer of HR ops. A field guide for any People leader heading into their next budget cycle.</p><p><br><strong><br>Timestamps</strong></p><p>00:00 Welcome and Wes's career path (TFA kindergarten to 1Password)</p><p>02:45 Inheriting a broken hiring process at a 10,000-person company</p><p>07:00 "You can build a new house, but the floor plan's wrong"</p><p>08:00 The structured plan, executive buy-in, and a budget bigger than expected</p><p>11:00 Sideways socialization: leading without authority across HR peers</p><p>13:30 1Password rolls out org-wide agent-building, and modeling AI as a leader</p><p>17:30 Build vs. buy in 2026 (and why it's really build AND buy)</p><p>22:30 The role redesign conversation: AI rewrites the JD, doesn't cut the role</p><p>26:00 The reframe Wes would apply today: people systems as infrastructure</p><p>30:00 Where People leaders should start their own AI journey</p><p><br><strong><br>Takeaways</strong></p><p>- HR transformation budgets are won in the months of pre-work before the e-staff ask, not in the room itself.</p><p>- The reframe from "employee experience" to "business infrastructure" is the single change that turns the same HR project from nice-to-have into board-level fundable.</p><p>- AI lands well when leaders treat it as a role-redesign conversation, not a layoff conversation. Most operational work was never on the JD anyway.</p><p>- Cross-functional buy-in (sideways across peer HR leaders) matters as much as executive sponsorship for any large People transformation.</p><p>- The best AI on-ramp for an individual contributor is to start with the work they're not great at, not the work they already excel at.</p><p><br><strong><br>Connect with the Guest<br></strong>Weston Fillman on LinkedIn: <a href="https://www.linkedin.com/in/westonfillman/">https://www.linkedin.com/in/westonfillman/</a><br>1Password: <a href="https://1password.com/">https://1password.com/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations,hr leadership,modern hr,workforce strategy,hr transformation funding,hr exec staff,people systems infrastructure,ai in hr,contractor program manager,onboarding program manager,hr role redesign,job family architecture,pay equity,agent building hr,1password people operations,weston fillman,how to get hr budget,ai replacing hr jobs,hr business case,chro strategy</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/b6c873d4/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/b6c873d4/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>The "Human API" problem hiding in your onboarding process</title>
      <itunes:episode>6</itunes:episode>
      <podcast:episode>6</podcast:episode>
      <itunes:title>The "Human API" problem hiding in your onboarding process</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">d05ae5dc-0bf2-45ca-9447-e32017331692</guid>
      <link>https://share.transistor.fm/s/06f710c0</link>
      <description>
        <![CDATA[<p><strong>Summary<br></strong><br></p><p>What looks like a warm, boutique onboarding experience on the outside is often powered by something much less glamorous on the inside: a person copy-pasting LinkedIn headshots into slides at midnight. </p><p>In this episode of the WorkOps Podcast, host Jeet sits down with Amie Taylor, Senior Director of People Operations, Rewards and Technology, for a refreshingly honest conversation about the hidden cost of "human API" processes. </p><p><br>Amie walks through a three-year saga at a previous hyper-growth tech consulting company where the entire day-zero-to-day-one new hire experience ran on Google Forms, manual IT tickets, and one very overworked TA coordinator hunting down headshots for the CMO's town hall slides. She shares how she eventually built the business case, the internal politics she had to navigate, why it took a team member filing overtime to finally break through, and the bittersweet twist at the end when she left right after getting the project approved. </p><p><br>She and Jeet also get into how she's applying those lessons today—consolidating HR systems at her current company, using critical thought as the test for what to automate, and why some processes (like leave for someone facing a serious diagnosis) should stay stubbornly human. If you've ever inherited a process held together by goodwill and overtime, this one will hit close to home.</p><p><strong><br>Timestamps</strong></p><ul><li>00:23 Amie's path from psychology to global payroll</li><li>04:46 Inheriting a high-touch onboarding process powered by "human APIs"</li><li>06:12 Google Forms, missed steps, and a candidate experience built on anxiety</li><li>08:23 Hours spent hunting down headshots for town hall slides</li><li>11:00 The three-year fight to get buy-in to automate</li><li>13:00 Getting the project approved, then resigning right after</li><li>15:13 Rebuilding similar processes today with full stakeholder buy-in</li><li>19:47 The "critical thought vs. machine work" test for what to automate</li></ul><p><br><strong>Takeaways</strong></p><ul><li>Audit the hidden labor inside "high-touch" processes before you call them culture</li><li>Quantify manual work in overtime and bottom-line impact, not just employee experience</li><li>Build stakeholder buy-in by making the decision feel like theirs, not yours</li><li>Use "critical thought vs. machine work" as your test for what AI and automation should touch</li><li>Protect the human moments—leave processes, serious diagnoses, tough conversations—no matter how advanced your tooling gets</li><li>Remember: if the process doesn't scale, it's not your culture, it's tech debt</li></ul><p><br><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/amie-taylor-5b99b810/">https://www.linkedin.com/in/amie-taylor-5b99b810/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary<br></strong><br></p><p>What looks like a warm, boutique onboarding experience on the outside is often powered by something much less glamorous on the inside: a person copy-pasting LinkedIn headshots into slides at midnight. </p><p>In this episode of the WorkOps Podcast, host Jeet sits down with Amie Taylor, Senior Director of People Operations, Rewards and Technology, for a refreshingly honest conversation about the hidden cost of "human API" processes. </p><p><br>Amie walks through a three-year saga at a previous hyper-growth tech consulting company where the entire day-zero-to-day-one new hire experience ran on Google Forms, manual IT tickets, and one very overworked TA coordinator hunting down headshots for the CMO's town hall slides. She shares how she eventually built the business case, the internal politics she had to navigate, why it took a team member filing overtime to finally break through, and the bittersweet twist at the end when she left right after getting the project approved. </p><p><br>She and Jeet also get into how she's applying those lessons today—consolidating HR systems at her current company, using critical thought as the test for what to automate, and why some processes (like leave for someone facing a serious diagnosis) should stay stubbornly human. If you've ever inherited a process held together by goodwill and overtime, this one will hit close to home.</p><p><strong><br>Timestamps</strong></p><ul><li>00:23 Amie's path from psychology to global payroll</li><li>04:46 Inheriting a high-touch onboarding process powered by "human APIs"</li><li>06:12 Google Forms, missed steps, and a candidate experience built on anxiety</li><li>08:23 Hours spent hunting down headshots for town hall slides</li><li>11:00 The three-year fight to get buy-in to automate</li><li>13:00 Getting the project approved, then resigning right after</li><li>15:13 Rebuilding similar processes today with full stakeholder buy-in</li><li>19:47 The "critical thought vs. machine work" test for what to automate</li></ul><p><br><strong>Takeaways</strong></p><ul><li>Audit the hidden labor inside "high-touch" processes before you call them culture</li><li>Quantify manual work in overtime and bottom-line impact, not just employee experience</li><li>Build stakeholder buy-in by making the decision feel like theirs, not yours</li><li>Use "critical thought vs. machine work" as your test for what AI and automation should touch</li><li>Protect the human moments—leave processes, serious diagnoses, tough conversations—no matter how advanced your tooling gets</li><li>Remember: if the process doesn't scale, it's not your culture, it's tech debt</li></ul><p><br><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/amie-taylor-5b99b810/">https://www.linkedin.com/in/amie-taylor-5b99b810/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 18:46:53 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/06f710c0/8956c175.mp3" length="22089896" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/w8SPZNfM7vJO-bTB0sr7b8Ou9eBk8E_2ymiqJwLtFAA/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS85ZWMy/N2FjMWU0ODAxZWM3/YmE0MmEwYjgxNWI4/ZDM2MC5wbmc.jpg"/>
      <itunes:duration>1378</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary<br></strong><br></p><p>What looks like a warm, boutique onboarding experience on the outside is often powered by something much less glamorous on the inside: a person copy-pasting LinkedIn headshots into slides at midnight. </p><p>In this episode of the WorkOps Podcast, host Jeet sits down with Amie Taylor, Senior Director of People Operations, Rewards and Technology, for a refreshingly honest conversation about the hidden cost of "human API" processes. </p><p><br>Amie walks through a three-year saga at a previous hyper-growth tech consulting company where the entire day-zero-to-day-one new hire experience ran on Google Forms, manual IT tickets, and one very overworked TA coordinator hunting down headshots for the CMO's town hall slides. She shares how she eventually built the business case, the internal politics she had to navigate, why it took a team member filing overtime to finally break through, and the bittersweet twist at the end when she left right after getting the project approved. </p><p><br>She and Jeet also get into how she's applying those lessons today—consolidating HR systems at her current company, using critical thought as the test for what to automate, and why some processes (like leave for someone facing a serious diagnosis) should stay stubbornly human. If you've ever inherited a process held together by goodwill and overtime, this one will hit close to home.</p><p><strong><br>Timestamps</strong></p><ul><li>00:23 Amie's path from psychology to global payroll</li><li>04:46 Inheriting a high-touch onboarding process powered by "human APIs"</li><li>06:12 Google Forms, missed steps, and a candidate experience built on anxiety</li><li>08:23 Hours spent hunting down headshots for town hall slides</li><li>11:00 The three-year fight to get buy-in to automate</li><li>13:00 Getting the project approved, then resigning right after</li><li>15:13 Rebuilding similar processes today with full stakeholder buy-in</li><li>19:47 The "critical thought vs. machine work" test for what to automate</li></ul><p><br><strong>Takeaways</strong></p><ul><li>Audit the hidden labor inside "high-touch" processes before you call them culture</li><li>Quantify manual work in overtime and bottom-line impact, not just employee experience</li><li>Build stakeholder buy-in by making the decision feel like theirs, not yours</li><li>Use "critical thought vs. machine work" as your test for what AI and automation should touch</li><li>Protect the human moments—leave processes, serious diagnoses, tough conversations—no matter how advanced your tooling gets</li><li>Remember: if the process doesn't scale, it's not your culture, it's tech debt</li></ul><p><br><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/amie-taylor-5b99b810/">https://www.linkedin.com/in/amie-taylor-5b99b810/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations, people operations rewards technology, HR process automation, onboarding automation, HRIS consolidation, UKG implementation, preboarding experience, HR tech debt, human API HR, hyper-growth HR, mergers and acquisitions HR, TA and HR integration, Google forms HR, ATS HRIS integration, HR change management, agentic AI in HR, HR workflow automation, people ops leadership, influencer marketing SaaS, WorkOps podcast</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/06f710c0/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/06f710c0/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>Why you should avoid exit and engagement surveys altogether</title>
      <itunes:episode>5</itunes:episode>
      <podcast:episode>5</podcast:episode>
      <itunes:title>Why you should avoid exit and engagement surveys altogether</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">b6d2ebbe-ed0b-4b6e-9e54-345d7db1275a</guid>
      <link>https://share.transistor.fm/s/5f971d59</link>
      <description>
        <![CDATA[<p><strong>Summary</strong></p><p>What if the most honest feedback about why people leave your company isn't in the exit survey at all—it's in the Slack threads, Zoom transcripts, and emails already happening every day? </p><p><br>In this episode of the WorkOps Podcast, host Jeet sits down with David Hanrahan, SVP of People Success at SolarWinds, for a candid conversation about one of the most broken processes in HR: the exit survey. </p><p><br>David walks through his years-long love-hate relationship with exit surveys, including a moment at Zendesk where he got so frustrated with the bad signal that he actually told the team to stop running them altogether. He and Jeet get into why exit data is so unreliable, how bias from both departing employees and their managers rewrites the real story, and why he believes the future is in predictive signals from real conversations rather than post-hoc questionnaires. </p><p>David also shares a contractor agent pilot that SolarWinds recently shelved, what it taught them about where AI belongs and where it doesn't, and how he's coaching his business partner team through the shift from tactical request-handling to strategic HR. And he closes with a line that stuck with me: in this era, people leaders need to think of themselves a little more as technologists and a little less as psychologists. If you lead people ops, build HR systems, or are just trying to figure out where AI fits, this one's worth an hour.</p><p><strong><br>Timestamps</strong></p><ul><li>00:33 From accidental psychology major to SVP of People Success</li><li>02:13 Why SolarWinds calls it "People Success" instead of HR</li><li>03:02 The exit survey problem at Zendesk and why David shut them down</li><li>06:16 How bias from both employees and managers corrupts exit data</li><li>12:34 Why employees are more comfortable asking AI sensitive questions</li><li>16:16 The contractor agent pilot SolarWinds shelved and what it taught them</li><li>21:05 Freeing up business partners for strategic HR through automation</li><li>23:33 Flipping exit surveys on their head with predictive signals</li></ul><p><strong><br>Takeaways</strong></p><ul><li>Interrogate the data you're treating as gospel; exit surveys carry more bias than most HR teams admit</li><li>Start with one high-impact area when adopting AI instead of trying to flip everything at once</li><li>Understand where a human needs to stay in the loop before building an agent—narrow scope without judgment design usually fails</li><li>Be explicit with your team about why you're automating; relinquishing work requires trust in what comes next</li><li>Look for retention signals in the conversations already happening, not in surveys you have to force people to fill out</li><li>Think of yourself a little more as a technologist and a little less as a psychologist in this era of HR</li></ul><p><br><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/davidhanrahan/">https://www.linkedin.com/in/davidhanrahan/</a></p><p><strong>Company website:</strong> <a href="https://www.solarwinds.com">https://www.solarwinds.com</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong></p><p>What if the most honest feedback about why people leave your company isn't in the exit survey at all—it's in the Slack threads, Zoom transcripts, and emails already happening every day? </p><p><br>In this episode of the WorkOps Podcast, host Jeet sits down with David Hanrahan, SVP of People Success at SolarWinds, for a candid conversation about one of the most broken processes in HR: the exit survey. </p><p><br>David walks through his years-long love-hate relationship with exit surveys, including a moment at Zendesk where he got so frustrated with the bad signal that he actually told the team to stop running them altogether. He and Jeet get into why exit data is so unreliable, how bias from both departing employees and their managers rewrites the real story, and why he believes the future is in predictive signals from real conversations rather than post-hoc questionnaires. </p><p>David also shares a contractor agent pilot that SolarWinds recently shelved, what it taught them about where AI belongs and where it doesn't, and how he's coaching his business partner team through the shift from tactical request-handling to strategic HR. And he closes with a line that stuck with me: in this era, people leaders need to think of themselves a little more as technologists and a little less as psychologists. If you lead people ops, build HR systems, or are just trying to figure out where AI fits, this one's worth an hour.</p><p><strong><br>Timestamps</strong></p><ul><li>00:33 From accidental psychology major to SVP of People Success</li><li>02:13 Why SolarWinds calls it "People Success" instead of HR</li><li>03:02 The exit survey problem at Zendesk and why David shut them down</li><li>06:16 How bias from both employees and managers corrupts exit data</li><li>12:34 Why employees are more comfortable asking AI sensitive questions</li><li>16:16 The contractor agent pilot SolarWinds shelved and what it taught them</li><li>21:05 Freeing up business partners for strategic HR through automation</li><li>23:33 Flipping exit surveys on their head with predictive signals</li></ul><p><strong><br>Takeaways</strong></p><ul><li>Interrogate the data you're treating as gospel; exit surveys carry more bias than most HR teams admit</li><li>Start with one high-impact area when adopting AI instead of trying to flip everything at once</li><li>Understand where a human needs to stay in the loop before building an agent—narrow scope without judgment design usually fails</li><li>Be explicit with your team about why you're automating; relinquishing work requires trust in what comes next</li><li>Look for retention signals in the conversations already happening, not in surveys you have to force people to fill out</li><li>Think of yourself a little more as a technologist and a little less as a psychologist in this era of HR</li></ul><p><br><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/davidhanrahan/">https://www.linkedin.com/in/davidhanrahan/</a></p><p><strong>Company website:</strong> <a href="https://www.solarwinds.com">https://www.solarwinds.com</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 18:46:46 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/5f971d59/152a4106.mp3" length="28027731" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/-jwAy5mkBOE_bOVqllQD_KRZtVDlOT2cy_SELHu9RdM/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yNTE3/ZWU5ODBkYmZjYzFj/NWExNGVlYmE4NjM4/ODljNy5wbmc.jpg"/>
      <itunes:duration>1749</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong></p><p>What if the most honest feedback about why people leave your company isn't in the exit survey at all—it's in the Slack threads, Zoom transcripts, and emails already happening every day? </p><p><br>In this episode of the WorkOps Podcast, host Jeet sits down with David Hanrahan, SVP of People Success at SolarWinds, for a candid conversation about one of the most broken processes in HR: the exit survey. </p><p><br>David walks through his years-long love-hate relationship with exit surveys, including a moment at Zendesk where he got so frustrated with the bad signal that he actually told the team to stop running them altogether. He and Jeet get into why exit data is so unreliable, how bias from both departing employees and their managers rewrites the real story, and why he believes the future is in predictive signals from real conversations rather than post-hoc questionnaires. </p><p>David also shares a contractor agent pilot that SolarWinds recently shelved, what it taught them about where AI belongs and where it doesn't, and how he's coaching his business partner team through the shift from tactical request-handling to strategic HR. And he closes with a line that stuck with me: in this era, people leaders need to think of themselves a little more as technologists and a little less as psychologists. If you lead people ops, build HR systems, or are just trying to figure out where AI fits, this one's worth an hour.</p><p><strong><br>Timestamps</strong></p><ul><li>00:33 From accidental psychology major to SVP of People Success</li><li>02:13 Why SolarWinds calls it "People Success" instead of HR</li><li>03:02 The exit survey problem at Zendesk and why David shut them down</li><li>06:16 How bias from both employees and managers corrupts exit data</li><li>12:34 Why employees are more comfortable asking AI sensitive questions</li><li>16:16 The contractor agent pilot SolarWinds shelved and what it taught them</li><li>21:05 Freeing up business partners for strategic HR through automation</li><li>23:33 Flipping exit surveys on their head with predictive signals</li></ul><p><strong><br>Takeaways</strong></p><ul><li>Interrogate the data you're treating as gospel; exit surveys carry more bias than most HR teams admit</li><li>Start with one high-impact area when adopting AI instead of trying to flip everything at once</li><li>Understand where a human needs to stay in the loop before building an agent—narrow scope without judgment design usually fails</li><li>Be explicit with your team about why you're automating; relinquishing work requires trust in what comes next</li><li>Look for retention signals in the conversations already happening, not in surveys you have to force people to fill out</li><li>Think of yourself a little more as a technologist and a little less as a psychologist in this era of HR</li></ul><p><br><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/davidhanrahan/">https://www.linkedin.com/in/davidhanrahan/</a></p><p><strong>Company website:</strong> <a href="https://www.solarwinds.com">https://www.solarwinds.com</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people success, HR exit surveys, exit interview bias, predictive attrition, AI in HR, agentic HR, HR business partner strategy, HR automation, employee engagement surveys, HRIS AI agents, retention risk modeling, HR process redesign, Zendesk HR, enterprise AI HR, people operations leadership, strategic HR, HR technology adoption, HR change management, WorkOps podcast</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/5f971d59/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/5f971d59/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>How to tell if you have a people problem or a process problem</title>
      <itunes:episode>4</itunes:episode>
      <podcast:episode>4</podcast:episode>
      <itunes:title>How to tell if you have a people problem or a process problem</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">323d1d95-5d68-4065-8469-a90c3781cf9c</guid>
      <link>https://share.transistor.fm/s/1b3b7023</link>
      <description>
        <![CDATA[<p><strong>Summary</strong></p><p>A CEO signs off on a new compensation philosophy. Two months later, when HR starts rolling it out, that same CEO tells the executive team it was never approved—and blames the HR leader for pushing it. </p><p><br>Sound impossible? It happened. </p><p><br>In this episode of the WorkOps Podcast, host Jeet sits down with Kelsey Browning, VP of People Operations, for a candid and detailed story about what happens when leadership alignment breaks down in the middle of a comp cycle at a Series B-to-C startup. </p><p><br>Kelsey was the first professional HR hire at the company and had to navigate a conflict-averse CEO, an emotionally flooded VP, and a compensation philosophy that was suddenly orphaned—all while protecting employees from the chaos happening above them. She walks through how she de-escalated heated executive conversations, rebuilt the philosophy for the next cycle, and what she'd do differently if she could go back. </p><p><br>She and Jeet also get into the framework she uses to decide what AI can solve (process problems) versus what still needs a human (people problems), why she builds employee journeys the same way product teams build customer journeys, and her prediction that HR is about to consolidate back into generalists—powered by AI. If you've ever been the HR person caught between a founder who changed their mind and an executive team that needs answers, this one will hit close to home.</p><p><strong><br>Timestamps</strong></p><ul><li>00:22 Kelsey's unusual path into HR: customer service, supply chain, and FP&amp;A</li><li>01:43 The scenario: first professional HR hire walks into a compensation philosophy mess</li><li>05:31 Discovering the CEO was no longer aligned with what they'd approved</li><li>08:25 De-escalating an emotionally flooded executive mid-conversation</li><li>12:39 Redesigning the compensation philosophy for the next cycle</li><li>17:39 Protecting employees from executive-level dysfunction</li><li>24:10 The "people problem vs. process problem" framework for AI</li><li>28:38 Automate all you can so you can spend time on the moments that matter<p></p></li></ul><p><strong>Takeaways</strong></p><ul><li>Reconfirm executive alignment right before executing—sign-off two months ago doesn't mean sign-off today</li><li>Learn to name emotional flooding in the moment; asking "would you like to reschedule?" usually resets the conversation</li><li>Script your CEO on what they need to say to the executive team instead of assuming they'll represent the decision correctly</li><li>Separate people problems from process problems before deciding where AI fits—AI solves process problems well today, people problems not yet</li><li>Build employee journeys the same way you'd build customer journeys, mapping output expectations around key lifecycle moments</li><li>Automate everything you can within the employee lifecycle so your team has time for the moments that actually matter<p></p></li></ul><p><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/kelseybrowning/">https://www.linkedin.com/in/kelseybrowning/</a></p><p><strong>Company website:</strong> <a href="https://invisibletech.ai/">https://invisibletech.ai/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong></p><p>A CEO signs off on a new compensation philosophy. Two months later, when HR starts rolling it out, that same CEO tells the executive team it was never approved—and blames the HR leader for pushing it. </p><p><br>Sound impossible? It happened. </p><p><br>In this episode of the WorkOps Podcast, host Jeet sits down with Kelsey Browning, VP of People Operations, for a candid and detailed story about what happens when leadership alignment breaks down in the middle of a comp cycle at a Series B-to-C startup. </p><p><br>Kelsey was the first professional HR hire at the company and had to navigate a conflict-averse CEO, an emotionally flooded VP, and a compensation philosophy that was suddenly orphaned—all while protecting employees from the chaos happening above them. She walks through how she de-escalated heated executive conversations, rebuilt the philosophy for the next cycle, and what she'd do differently if she could go back. </p><p><br>She and Jeet also get into the framework she uses to decide what AI can solve (process problems) versus what still needs a human (people problems), why she builds employee journeys the same way product teams build customer journeys, and her prediction that HR is about to consolidate back into generalists—powered by AI. If you've ever been the HR person caught between a founder who changed their mind and an executive team that needs answers, this one will hit close to home.</p><p><strong><br>Timestamps</strong></p><ul><li>00:22 Kelsey's unusual path into HR: customer service, supply chain, and FP&amp;A</li><li>01:43 The scenario: first professional HR hire walks into a compensation philosophy mess</li><li>05:31 Discovering the CEO was no longer aligned with what they'd approved</li><li>08:25 De-escalating an emotionally flooded executive mid-conversation</li><li>12:39 Redesigning the compensation philosophy for the next cycle</li><li>17:39 Protecting employees from executive-level dysfunction</li><li>24:10 The "people problem vs. process problem" framework for AI</li><li>28:38 Automate all you can so you can spend time on the moments that matter<p></p></li></ul><p><strong>Takeaways</strong></p><ul><li>Reconfirm executive alignment right before executing—sign-off two months ago doesn't mean sign-off today</li><li>Learn to name emotional flooding in the moment; asking "would you like to reschedule?" usually resets the conversation</li><li>Script your CEO on what they need to say to the executive team instead of assuming they'll represent the decision correctly</li><li>Separate people problems from process problems before deciding where AI fits—AI solves process problems well today, people problems not yet</li><li>Build employee journeys the same way you'd build customer journeys, mapping output expectations around key lifecycle moments</li><li>Automate everything you can within the employee lifecycle so your team has time for the moments that actually matter<p></p></li></ul><p><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/kelseybrowning/">https://www.linkedin.com/in/kelseybrowning/</a></p><p><strong>Company website:</strong> <a href="https://invisibletech.ai/">https://invisibletech.ai/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 18:46:39 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/1b3b7023/6bd9341b.mp3" length="32125890" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/cUgd-vgKGHPjtWNuvEUiPfFrvYYK9QPNy71yd11FtB0/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9mMjE2/NzEyZTU3MTVlOThl/MmNjNTgwYjYwOTY4/NGM4Yy5wbmc.jpg"/>
      <itunes:duration>2005</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong></p><p>A CEO signs off on a new compensation philosophy. Two months later, when HR starts rolling it out, that same CEO tells the executive team it was never approved—and blames the HR leader for pushing it. </p><p><br>Sound impossible? It happened. </p><p><br>In this episode of the WorkOps Podcast, host Jeet sits down with Kelsey Browning, VP of People Operations, for a candid and detailed story about what happens when leadership alignment breaks down in the middle of a comp cycle at a Series B-to-C startup. </p><p><br>Kelsey was the first professional HR hire at the company and had to navigate a conflict-averse CEO, an emotionally flooded VP, and a compensation philosophy that was suddenly orphaned—all while protecting employees from the chaos happening above them. She walks through how she de-escalated heated executive conversations, rebuilt the philosophy for the next cycle, and what she'd do differently if she could go back. </p><p><br>She and Jeet also get into the framework she uses to decide what AI can solve (process problems) versus what still needs a human (people problems), why she builds employee journeys the same way product teams build customer journeys, and her prediction that HR is about to consolidate back into generalists—powered by AI. If you've ever been the HR person caught between a founder who changed their mind and an executive team that needs answers, this one will hit close to home.</p><p><strong><br>Timestamps</strong></p><ul><li>00:22 Kelsey's unusual path into HR: customer service, supply chain, and FP&amp;A</li><li>01:43 The scenario: first professional HR hire walks into a compensation philosophy mess</li><li>05:31 Discovering the CEO was no longer aligned with what they'd approved</li><li>08:25 De-escalating an emotionally flooded executive mid-conversation</li><li>12:39 Redesigning the compensation philosophy for the next cycle</li><li>17:39 Protecting employees from executive-level dysfunction</li><li>24:10 The "people problem vs. process problem" framework for AI</li><li>28:38 Automate all you can so you can spend time on the moments that matter<p></p></li></ul><p><strong>Takeaways</strong></p><ul><li>Reconfirm executive alignment right before executing—sign-off two months ago doesn't mean sign-off today</li><li>Learn to name emotional flooding in the moment; asking "would you like to reschedule?" usually resets the conversation</li><li>Script your CEO on what they need to say to the executive team instead of assuming they'll represent the decision correctly</li><li>Separate people problems from process problems before deciding where AI fits—AI solves process problems well today, people problems not yet</li><li>Build employee journeys the same way you'd build customer journeys, mapping output expectations around key lifecycle moments</li><li>Automate everything you can within the employee lifecycle so your team has time for the moments that actually matter<p></p></li></ul><p><strong>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/kelseybrowning/">https://www.linkedin.com/in/kelseybrowning/</a></p><p><strong>Company website:</strong> <a href="https://invisibletech.ai/">https://invisibletech.ai/</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations,hr tech,workplace culture,compensation philosophy,compensation consultants,merit cycle,employee journey,employee lifecycle,employee advocacy,difficult conversations,ai in hr,process problems,people problems,hr business partner,workplace challenges,hr automation,executive alignment,startup hr,remote work policy,hr strategy</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/1b3b7023/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/1b3b7023/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>Automating HR admin to solve a $400k mess</title>
      <itunes:episode>3</itunes:episode>
      <podcast:episode>3</podcast:episode>
      <itunes:title>Automating HR admin to solve a $400k mess</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">53ac42f6-76c1-4909-ab83-f53673b91c1d</guid>
      <link>https://share.transistor.fm/s/2afb8190</link>
      <description>
        <![CDATA[<p><strong>Summary</strong><br>When the sole operator of a global company’s immigration process left, a critical workflow supporting 10% of the workforce imploded. What remained was an undocumented, email-based system, causing widespread employee anxiety about work authorization and threatening the company’s ability to retain essential US-based talent. This created a strategic nightmare: a global healthcare data analytics firm, where much of its data could not be sent offshore, faced losing critical personnel due to a broken internal process.</p><p>Chesney Woodall, an HR Director initially unfamiliar with immigration, inherited this mess. She quickly found herself managing 25 simultaneous immigration cases while <strong><em>operating as a key contributor</em></strong> on a three-person US HR team for a 1,000-employee company. This "messy middle" between top-down goals and bottom-up work created an accountability gap that put talent retention and business continuity at risk. To systematize the process, Chesney leaned on cross-functional collaboration and existing tools, transforming a manual, fear-inducing workflow into a more transparent system. Now, Chesney uses AI as a personal learning assistant, democratizing complex knowledge and freeing up strategic time to focus on people-centric HR.</p><p><br></p><p><strong>Timestamps</strong></p><ul><li>00:10 The undocumented immigration process creating a single point of failure</li><li>03:29 10% of the company's global workforce impacted by visa uncertainty</li><li>04:35 "If it touches the employee, it comes to HR": Navigating process ownership</li><li>06:07 The Excel spreadsheet chaos and undocumented immigration tracking</li><li>07:47 Employee fear: Losing work authorization and business continuity risk</li><li>09:22 How ChatGPT became Chesney's accidental immigration SME</li><li>10:46 Automating admin: Unlocking strategic time for people-centric HR</li><li>16:40 Building an internal operating system for immigration with Jira</li><li>18:46 The manual gaps: Jira’s limitations and the need for further automation</li><li>22:56 AI's role in improving employee experience and information discoverability</li></ul><p><br><strong>Takeaways</strong></p><ul><li>Standardize critical processes to avoid a single point of failure, especially when they directly impact talent retention and business continuity.</li><li>Utilize existing internal tools and cross-functional teams to build solutions, leveraging institutional knowledge before investing in new software.</li><li>Systematize administrative tasks to free up HR for strategic initiatives like proactive talent management and improving employee experience.</li></ul><p><br><strong>Connect with the guest</strong></p><p>LinkedIn: <a href="https://www.linkedin.com/in/chesney-woodall/">https://www.linkedin.com/in/chesney-woodall/</a></p><p>Learn more about Cedar Gate: <a href="https://www.cedargate.com/">https://www.cedargate.com/</a> <a href="https://www.kinfolkhq.com/"><br></a><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong><br>When the sole operator of a global company’s immigration process left, a critical workflow supporting 10% of the workforce imploded. What remained was an undocumented, email-based system, causing widespread employee anxiety about work authorization and threatening the company’s ability to retain essential US-based talent. This created a strategic nightmare: a global healthcare data analytics firm, where much of its data could not be sent offshore, faced losing critical personnel due to a broken internal process.</p><p>Chesney Woodall, an HR Director initially unfamiliar with immigration, inherited this mess. She quickly found herself managing 25 simultaneous immigration cases while <strong><em>operating as a key contributor</em></strong> on a three-person US HR team for a 1,000-employee company. This "messy middle" between top-down goals and bottom-up work created an accountability gap that put talent retention and business continuity at risk. To systematize the process, Chesney leaned on cross-functional collaboration and existing tools, transforming a manual, fear-inducing workflow into a more transparent system. Now, Chesney uses AI as a personal learning assistant, democratizing complex knowledge and freeing up strategic time to focus on people-centric HR.</p><p><br></p><p><strong>Timestamps</strong></p><ul><li>00:10 The undocumented immigration process creating a single point of failure</li><li>03:29 10% of the company's global workforce impacted by visa uncertainty</li><li>04:35 "If it touches the employee, it comes to HR": Navigating process ownership</li><li>06:07 The Excel spreadsheet chaos and undocumented immigration tracking</li><li>07:47 Employee fear: Losing work authorization and business continuity risk</li><li>09:22 How ChatGPT became Chesney's accidental immigration SME</li><li>10:46 Automating admin: Unlocking strategic time for people-centric HR</li><li>16:40 Building an internal operating system for immigration with Jira</li><li>18:46 The manual gaps: Jira’s limitations and the need for further automation</li><li>22:56 AI's role in improving employee experience and information discoverability</li></ul><p><br><strong>Takeaways</strong></p><ul><li>Standardize critical processes to avoid a single point of failure, especially when they directly impact talent retention and business continuity.</li><li>Utilize existing internal tools and cross-functional teams to build solutions, leveraging institutional knowledge before investing in new software.</li><li>Systematize administrative tasks to free up HR for strategic initiatives like proactive talent management and improving employee experience.</li></ul><p><br><strong>Connect with the guest</strong></p><p>LinkedIn: <a href="https://www.linkedin.com/in/chesney-woodall/">https://www.linkedin.com/in/chesney-woodall/</a></p><p>Learn more about Cedar Gate: <a href="https://www.cedargate.com/">https://www.cedargate.com/</a> <a href="https://www.kinfolkhq.com/"><br></a><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 18:46:32 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/2afb8190/209f61ea.mp3" length="26242572" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/xxqKbIus7YQ4Hftz3CxowFzDMFWCspwB8TQ2qQFr_-c/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8zYTJh/MTFmYTA0MTljMTEy/NzY0MTJjYzBkNjU2/ZjAyNS5wbmc.jpg"/>
      <itunes:duration>1637</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong><br>When the sole operator of a global company’s immigration process left, a critical workflow supporting 10% of the workforce imploded. What remained was an undocumented, email-based system, causing widespread employee anxiety about work authorization and threatening the company’s ability to retain essential US-based talent. This created a strategic nightmare: a global healthcare data analytics firm, where much of its data could not be sent offshore, faced losing critical personnel due to a broken internal process.</p><p>Chesney Woodall, an HR Director initially unfamiliar with immigration, inherited this mess. She quickly found herself managing 25 simultaneous immigration cases while <strong><em>operating as a key contributor</em></strong> on a three-person US HR team for a 1,000-employee company. This "messy middle" between top-down goals and bottom-up work created an accountability gap that put talent retention and business continuity at risk. To systematize the process, Chesney leaned on cross-functional collaboration and existing tools, transforming a manual, fear-inducing workflow into a more transparent system. Now, Chesney uses AI as a personal learning assistant, democratizing complex knowledge and freeing up strategic time to focus on people-centric HR.</p><p><br></p><p><strong>Timestamps</strong></p><ul><li>00:10 The undocumented immigration process creating a single point of failure</li><li>03:29 10% of the company's global workforce impacted by visa uncertainty</li><li>04:35 "If it touches the employee, it comes to HR": Navigating process ownership</li><li>06:07 The Excel spreadsheet chaos and undocumented immigration tracking</li><li>07:47 Employee fear: Losing work authorization and business continuity risk</li><li>09:22 How ChatGPT became Chesney's accidental immigration SME</li><li>10:46 Automating admin: Unlocking strategic time for people-centric HR</li><li>16:40 Building an internal operating system for immigration with Jira</li><li>18:46 The manual gaps: Jira’s limitations and the need for further automation</li><li>22:56 AI's role in improving employee experience and information discoverability</li></ul><p><br><strong>Takeaways</strong></p><ul><li>Standardize critical processes to avoid a single point of failure, especially when they directly impact talent retention and business continuity.</li><li>Utilize existing internal tools and cross-functional teams to build solutions, leveraging institutional knowledge before investing in new software.</li><li>Systematize administrative tasks to free up HR for strategic initiatives like proactive talent management and improving employee experience.</li></ul><p><br><strong>Connect with the guest</strong></p><p>LinkedIn: <a href="https://www.linkedin.com/in/chesney-woodall/">https://www.linkedin.com/in/chesney-woodall/</a></p><p>Learn more about Cedar Gate: <a href="https://www.cedargate.com/">https://www.cedargate.com/</a> <a href="https://www.kinfolkhq.com/"><br></a><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>workops podcast,people operations,hr tech,workplace culture,immigration process,human single point of failure,centralized immigration management,visa expiration tracking,hr burden,employee anxiety,strategic time,jira for hr,ai in hr,copilot,ai for process improvement,ai for employee experience,hr generalist,hr director,people leader,people analytics</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/2afb8190/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/2afb8190/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>Why your HR process is actually chaos</title>
      <itunes:episode>2</itunes:episode>
      <podcast:episode>2</podcast:episode>
      <itunes:title>Why your HR process is actually chaos</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">2af78a06-77be-44cf-8db7-0f8c6e1f19ae</guid>
      <link>https://share.transistor.fm/s/55b2cfe1</link>
      <description>
        <![CDATA[<p><strong>Summary</strong></p><p>Most companies have an offer process that looks clean on a whiteboard and turns into chaos in practice. The recruiter fights for more money. The comp team says no. Finance says it's too expensive. The business leader just wants it done. </p><p><br>Everyone's working off different information, and by the time a decision is made, it's conflict resolution—not a hiring process. In this episode of the WorkOps Podcast, host Jeet sits down with Tony Castellanos, EVP of People at Nextdoor, for a sharp conversation about what happens when you replace serial decision-making with shared context. </p><p>Tony has spent his career watching offer processes break down because every stakeholder applies their own lens in isolation—and nobody has the full picture. He walks through how Nextdoor rebuilt the process to bring all parties into the room at the beginning instead of passing decisions down a chain, why the proudest moments in his career are when a recruiter says no to a hire they could have closed, and how the shift from "HR" to "people" isn't just branding—it changes the scope and responsibility of the entire function. </p><p><br>Tony and Jeet also get into why information architecture is the unsexy foundation that makes AI-first people operations possible, how Nextdoor runs a dedicated build day once a month for AI experimentation, and why the biggest thing leaders can do right now is create space for their teams to be "courageously creative." If you lead a people function, run a recruiting team, or are trying to figure out where AI fits, Tony's framework of context over control will change how you think about the work.</p><p><strong><br>Timestamps</strong></p><ul><li>00:18 Tony's path from recruiting agency to EVP of People</li><li>02:16 The evolution from HR to People—and why it's intentional, not just branding</li><li>07:35 The offer process: why the blueprint breaks in practice</li><li>10:16 Solving for context over control: bringing all stakeholders in upfront</li><li>13:11 The proudest moment: when a recruiter says no to a hire they could have closed</li><li>16:07 Who makes the final call when there's a deadlock</li><li>19:20 Building AI on top of solid information architecture</li><li>23:00 A day a month for AI experimentation and the "courageously creative" mindset<p></p></li></ul><p><strong>Takeaways</strong></p><ul><li>Replace serial offer approvals with a shared context model where TA, comp, finance, and the hiring leader are all in the room from the start</li><li>Celebrate when recruiters say no to a hire based on long-term team impact—that's the shift from closing at all costs to creating long-term value</li><li>Invest in information architecture before building AI services on top; your underlying data has to be rock solid</li><li>Create dedicated time for AI experimentation—a half hour between meetings isn't enough, context switching kills it</li><li>Embrace "context over control" as a design principle across your people function, not just in comp decisions</li><li>Trust your leaders to own the trade-offs; the people team that's always the blanket "no" disempowers the organization<p></p></li></ul><p><strong><br>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/tcastellanos/">https://www.linkedin.com/in/tcastellanos/</a></p><p><strong>Company website:</strong> <a href="https://about.nextdoor.com">https://about.nextdoor.com</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong></p><p>Most companies have an offer process that looks clean on a whiteboard and turns into chaos in practice. The recruiter fights for more money. The comp team says no. Finance says it's too expensive. The business leader just wants it done. </p><p><br>Everyone's working off different information, and by the time a decision is made, it's conflict resolution—not a hiring process. In this episode of the WorkOps Podcast, host Jeet sits down with Tony Castellanos, EVP of People at Nextdoor, for a sharp conversation about what happens when you replace serial decision-making with shared context. </p><p>Tony has spent his career watching offer processes break down because every stakeholder applies their own lens in isolation—and nobody has the full picture. He walks through how Nextdoor rebuilt the process to bring all parties into the room at the beginning instead of passing decisions down a chain, why the proudest moments in his career are when a recruiter says no to a hire they could have closed, and how the shift from "HR" to "people" isn't just branding—it changes the scope and responsibility of the entire function. </p><p><br>Tony and Jeet also get into why information architecture is the unsexy foundation that makes AI-first people operations possible, how Nextdoor runs a dedicated build day once a month for AI experimentation, and why the biggest thing leaders can do right now is create space for their teams to be "courageously creative." If you lead a people function, run a recruiting team, or are trying to figure out where AI fits, Tony's framework of context over control will change how you think about the work.</p><p><strong><br>Timestamps</strong></p><ul><li>00:18 Tony's path from recruiting agency to EVP of People</li><li>02:16 The evolution from HR to People—and why it's intentional, not just branding</li><li>07:35 The offer process: why the blueprint breaks in practice</li><li>10:16 Solving for context over control: bringing all stakeholders in upfront</li><li>13:11 The proudest moment: when a recruiter says no to a hire they could have closed</li><li>16:07 Who makes the final call when there's a deadlock</li><li>19:20 Building AI on top of solid information architecture</li><li>23:00 A day a month for AI experimentation and the "courageously creative" mindset<p></p></li></ul><p><strong>Takeaways</strong></p><ul><li>Replace serial offer approvals with a shared context model where TA, comp, finance, and the hiring leader are all in the room from the start</li><li>Celebrate when recruiters say no to a hire based on long-term team impact—that's the shift from closing at all costs to creating long-term value</li><li>Invest in information architecture before building AI services on top; your underlying data has to be rock solid</li><li>Create dedicated time for AI experimentation—a half hour between meetings isn't enough, context switching kills it</li><li>Embrace "context over control" as a design principle across your people function, not just in comp decisions</li><li>Trust your leaders to own the trade-offs; the people team that's always the blanket "no" disempowers the organization<p></p></li></ul><p><strong><br>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/tcastellanos/">https://www.linkedin.com/in/tcastellanos/</a></p><p><strong>Company website:</strong> <a href="https://about.nextdoor.com">https://about.nextdoor.com</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 18:46:24 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/55b2cfe1/3c2c410b.mp3" length="28162577" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/oVnLMvM-fe4M7TV68alkdiTHY5NOvM8rvCsomb5V5ig/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS9mZmQx/M2NkM2YxNzVjZGZh/M2ZjMDZjMTllODdm/MDEyYy5wbmc.jpg"/>
      <itunes:duration>1758</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong></p><p>Most companies have an offer process that looks clean on a whiteboard and turns into chaos in practice. The recruiter fights for more money. The comp team says no. Finance says it's too expensive. The business leader just wants it done. </p><p><br>Everyone's working off different information, and by the time a decision is made, it's conflict resolution—not a hiring process. In this episode of the WorkOps Podcast, host Jeet sits down with Tony Castellanos, EVP of People at Nextdoor, for a sharp conversation about what happens when you replace serial decision-making with shared context. </p><p>Tony has spent his career watching offer processes break down because every stakeholder applies their own lens in isolation—and nobody has the full picture. He walks through how Nextdoor rebuilt the process to bring all parties into the room at the beginning instead of passing decisions down a chain, why the proudest moments in his career are when a recruiter says no to a hire they could have closed, and how the shift from "HR" to "people" isn't just branding—it changes the scope and responsibility of the entire function. </p><p><br>Tony and Jeet also get into why information architecture is the unsexy foundation that makes AI-first people operations possible, how Nextdoor runs a dedicated build day once a month for AI experimentation, and why the biggest thing leaders can do right now is create space for their teams to be "courageously creative." If you lead a people function, run a recruiting team, or are trying to figure out where AI fits, Tony's framework of context over control will change how you think about the work.</p><p><strong><br>Timestamps</strong></p><ul><li>00:18 Tony's path from recruiting agency to EVP of People</li><li>02:16 The evolution from HR to People—and why it's intentional, not just branding</li><li>07:35 The offer process: why the blueprint breaks in practice</li><li>10:16 Solving for context over control: bringing all stakeholders in upfront</li><li>13:11 The proudest moment: when a recruiter says no to a hire they could have closed</li><li>16:07 Who makes the final call when there's a deadlock</li><li>19:20 Building AI on top of solid information architecture</li><li>23:00 A day a month for AI experimentation and the "courageously creative" mindset<p></p></li></ul><p><strong>Takeaways</strong></p><ul><li>Replace serial offer approvals with a shared context model where TA, comp, finance, and the hiring leader are all in the room from the start</li><li>Celebrate when recruiters say no to a hire based on long-term team impact—that's the shift from closing at all costs to creating long-term value</li><li>Invest in information architecture before building AI services on top; your underlying data has to be rock solid</li><li>Create dedicated time for AI experimentation—a half hour between meetings isn't enough, context switching kills it</li><li>Embrace "context over control" as a design principle across your people function, not just in comp decisions</li><li>Trust your leaders to own the trade-offs; the people team that's always the blanket "no" disempowers the organization<p></p></li></ul><p><strong><br>Guest LinkedIn:</strong> <a href="https://www.linkedin.com/in/tcastellanos/">https://www.linkedin.com/in/tcastellanos/</a></p><p><strong>Company website:</strong> <a href="https://about.nextdoor.com">https://about.nextdoor.com</a></p><p><br><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>people operations,workplace culture,employee experience,hr operations,ai in hr,dysfunctional hr processes,offer process,compensation team,talent acquisition,candidate experience,hr tech,hr leaders,nextdoor,context over control,system thinking,ai services,information architecture,recruiter,people teams,hr strategy</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/55b2cfe1/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/55b2cfe1/chapters.json" type="application/json+chapters"/>
    </item>
    <item>
      <title>Building a performance management system in five minutes with Claude</title>
      <itunes:episode>1</itunes:episode>
      <podcast:episode>1</podcast:episode>
      <itunes:title>Building a performance management system in five minutes with Claude</itunes:title>
      <itunes:episodeType>full</itunes:episodeType>
      <guid isPermaLink="false">48423711-7e09-4b0a-bd51-ef6143733db8</guid>
      <link>https://share.transistor.fm/s/c747c9f1</link>
      <description>
        <![CDATA[<p><strong>Summary</strong><br>Vidyard's performance system was broken. Managers placed employees in nine-box grids with no clear expectations, no career framework, and no two-way conversation. Decisions on compensation and promotions happened in silos, riddled with bias. Employees felt the process was opaque and unfair — yet Sarika Lamont, Vidyard's Chief People Officer, had no technology, no team bandwidth, and a business contracting through a SaaS downturn.</p><p>Three and a half years later, she's rebuilt the entire system — career frameworks, competencies, performance reviews, and now an AI-powered interactive tool that took five minutes to prototype. What once required two quarters and a team of specialists now happens in a week. In this episode, Sarika walks through how she dismantled a one-sided performance process, designed for scale during contraction, and used Claude to compress months of work into days — all while solving for what employees and managers actually need, not what HR traditionally builds.</p><p><strong>Timestamps</strong><br>00:01 How Sarika fell into HR from management consulting at a federal contracting startup  <br>05:59 The broken nine-box system she inherited: no expectations, no framework, pure manager bias  <br>11:28 Why cross-functional partnerships with finance and business leaders matter more than HR credentials  <br>17:22 Building a career framework from scratch: IC paths, management tracks, and leveling for scale  <br>23:35 The SaaS downturn, AI disruption, and why the system went stagnant  <br>28:19 Using Claude to redesign competencies in days instead of quarters  <br>33:55 What replaces the time saved: ongoing enablement, adoption, and human-to-human coaching  <br>38:12 Where to start if you're overwhelmed: validate the real problem first, then ask AI where to begin</p><p><strong>Takeaways</strong><br>- Build your performance system from the business problem backward — not from what HR traditionally designs — or you'll solve for process instead of outcomes.<br>- Career frameworks need differentiation level-to-level so employees see the gap between "intermediate" and "senior" in concrete, actionable terms, not themes.<br>- AI compresses iteration cycles from quarters to days, but the time saved goes to enablement and adoption — the work HR has always neglected because building took too long.<br>- Start by validating what employees and managers actually need through exit data, engagement surveys, and one-on-ones — then use AI as a thought partner to fill the gaps you can't solve manually.<br>- Performance transparency isn't about revealing ratings — it's about documenting expectations, competencies, and decision-making frameworks so people understand how to grow.</p><p><strong>Connect with the Guest</strong><br>LinkedIn: <a href="https://www.linkedin.com/in/sarikal/">https://www.linkedin.com/in/sarikal/</a><br>Learn more about Vidyard: <a href="https://www.vidyard.com/">https://www.vidyard.com/</a></p><p><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </description>
      <content:encoded>
        <![CDATA[<p><strong>Summary</strong><br>Vidyard's performance system was broken. Managers placed employees in nine-box grids with no clear expectations, no career framework, and no two-way conversation. Decisions on compensation and promotions happened in silos, riddled with bias. Employees felt the process was opaque and unfair — yet Sarika Lamont, Vidyard's Chief People Officer, had no technology, no team bandwidth, and a business contracting through a SaaS downturn.</p><p>Three and a half years later, she's rebuilt the entire system — career frameworks, competencies, performance reviews, and now an AI-powered interactive tool that took five minutes to prototype. What once required two quarters and a team of specialists now happens in a week. In this episode, Sarika walks through how she dismantled a one-sided performance process, designed for scale during contraction, and used Claude to compress months of work into days — all while solving for what employees and managers actually need, not what HR traditionally builds.</p><p><strong>Timestamps</strong><br>00:01 How Sarika fell into HR from management consulting at a federal contracting startup  <br>05:59 The broken nine-box system she inherited: no expectations, no framework, pure manager bias  <br>11:28 Why cross-functional partnerships with finance and business leaders matter more than HR credentials  <br>17:22 Building a career framework from scratch: IC paths, management tracks, and leveling for scale  <br>23:35 The SaaS downturn, AI disruption, and why the system went stagnant  <br>28:19 Using Claude to redesign competencies in days instead of quarters  <br>33:55 What replaces the time saved: ongoing enablement, adoption, and human-to-human coaching  <br>38:12 Where to start if you're overwhelmed: validate the real problem first, then ask AI where to begin</p><p><strong>Takeaways</strong><br>- Build your performance system from the business problem backward — not from what HR traditionally designs — or you'll solve for process instead of outcomes.<br>- Career frameworks need differentiation level-to-level so employees see the gap between "intermediate" and "senior" in concrete, actionable terms, not themes.<br>- AI compresses iteration cycles from quarters to days, but the time saved goes to enablement and adoption — the work HR has always neglected because building took too long.<br>- Start by validating what employees and managers actually need through exit data, engagement surveys, and one-on-ones — then use AI as a thought partner to fill the gaps you can't solve manually.<br>- Performance transparency isn't about revealing ratings — it's about documenting expectations, competencies, and decision-making frameworks so people understand how to grow.</p><p><strong>Connect with the Guest</strong><br>LinkedIn: <a href="https://www.linkedin.com/in/sarikal/">https://www.linkedin.com/in/sarikal/</a><br>Learn more about Vidyard: <a href="https://www.vidyard.com/">https://www.vidyard.com/</a></p><p><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </content:encoded>
      <pubDate>Tue, 12 May 2026 18:46:16 -0600</pubDate>
      <author>by Kinfolk</author>
      <enclosure url="https://media.transistor.fm/c747c9f1/c59c4cb7.mp3" length="39990873" type="audio/mpeg"/>
      <itunes:author>by Kinfolk</itunes:author>
      <itunes:image href="https://img.transistorcdn.com/0jsk4YUgaKroBqZGiPB5kz4MWxe3g40tNDWJFy0gotI/rs:fill:0:0:1/w:1400/h:1400/q:60/mb:500000/aHR0cHM6Ly9pbWct/dXBsb2FkLXByb2R1/Y3Rpb24udHJhbnNp/c3Rvci5mbS8yNTVi/OThlMmRiZjU2YjM4/YzA5Mjk5MDExYjNl/NzVhZS5wbmc.jpg"/>
      <itunes:duration>2497</itunes:duration>
      <itunes:summary>
        <![CDATA[<p><strong>Summary</strong><br>Vidyard's performance system was broken. Managers placed employees in nine-box grids with no clear expectations, no career framework, and no two-way conversation. Decisions on compensation and promotions happened in silos, riddled with bias. Employees felt the process was opaque and unfair — yet Sarika Lamont, Vidyard's Chief People Officer, had no technology, no team bandwidth, and a business contracting through a SaaS downturn.</p><p>Three and a half years later, she's rebuilt the entire system — career frameworks, competencies, performance reviews, and now an AI-powered interactive tool that took five minutes to prototype. What once required two quarters and a team of specialists now happens in a week. In this episode, Sarika walks through how she dismantled a one-sided performance process, designed for scale during contraction, and used Claude to compress months of work into days — all while solving for what employees and managers actually need, not what HR traditionally builds.</p><p><strong>Timestamps</strong><br>00:01 How Sarika fell into HR from management consulting at a federal contracting startup  <br>05:59 The broken nine-box system she inherited: no expectations, no framework, pure manager bias  <br>11:28 Why cross-functional partnerships with finance and business leaders matter more than HR credentials  <br>17:22 Building a career framework from scratch: IC paths, management tracks, and leveling for scale  <br>23:35 The SaaS downturn, AI disruption, and why the system went stagnant  <br>28:19 Using Claude to redesign competencies in days instead of quarters  <br>33:55 What replaces the time saved: ongoing enablement, adoption, and human-to-human coaching  <br>38:12 Where to start if you're overwhelmed: validate the real problem first, then ask AI where to begin</p><p><strong>Takeaways</strong><br>- Build your performance system from the business problem backward — not from what HR traditionally designs — or you'll solve for process instead of outcomes.<br>- Career frameworks need differentiation level-to-level so employees see the gap between "intermediate" and "senior" in concrete, actionable terms, not themes.<br>- AI compresses iteration cycles from quarters to days, but the time saved goes to enablement and adoption — the work HR has always neglected because building took too long.<br>- Start by validating what employees and managers actually need through exit data, engagement surveys, and one-on-ones — then use AI as a thought partner to fill the gaps you can't solve manually.<br>- Performance transparency isn't about revealing ratings — it's about documenting expectations, competencies, and decision-making frameworks so people understand how to grow.</p><p><strong>Connect with the Guest</strong><br>LinkedIn: <a href="https://www.linkedin.com/in/sarikal/">https://www.linkedin.com/in/sarikal/</a><br>Learn more about Vidyard: <a href="https://www.vidyard.com/">https://www.vidyard.com/</a></p><p><strong>Sponsor</strong><br>This episode is brought to you by Kinfolk, the AI service desk built for HR.</p><p>See more at <a href="http://kinfolkhq.com/">kinfolkhq.com</a></p>]]>
      </itunes:summary>
      <itunes:keywords>employee experience,people operations,performance management,career framework,competency framework,performance reviews,HR tech,manager enablement,employee development,AI in HR,Claude AI,HR transformation,people leader,performance calibration,career development,continuous feedback,skills development,employee engagement,HR strategy,talent development</itunes:keywords>
      <itunes:explicit>No</itunes:explicit>
      <podcast:transcript url="https://share.transistor.fm/s/c747c9f1/transcript.txt" type="text/plain"/>
      <podcast:chapters url="https://share.transistor.fm/s/c747c9f1/chapters.json" type="application/json+chapters"/>
    </item>
  </channel>
</rss>
