<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Mehar Khanna on Medium]]></title>
        <description><![CDATA[Stories by Mehar Khanna on Medium]]></description>
        <link>https://medium.com/@meharkhanna.mk?source=rss-0bad774f2601------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ZnpsUx2UUu3J4txOvzYyDw.png</url>
            <title>Stories by Mehar Khanna on Medium</title>
            <link>https://medium.com/@meharkhanna.mk?source=rss-0bad774f2601------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:34:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@meharkhanna.mk/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[AI in HR Isn’t a Technology Challenge — It’s a Human One]]></title>
            <link>https://medium.com/@meharkhanna.mk/ai-in-hr-isnt-a-technology-challenge-it-s-a-human-one-8145fe63c8a1?source=rss-0bad774f2601------2</link>
            <guid isPermaLink="false">https://medium.com/p/8145fe63c8a1</guid>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[workforce-planning]]></category>
            <category><![CDATA[ai-in-workplace]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Mehar Khanna]]></dc:creator>
            <pubDate>Mon, 19 Jan 2026 10:36:51 GMT</pubDate>
            <atom:updated>2026-01-19T10:36:51.870Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI in HR Isn’t a Technology Challenge — It’s a Human One</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cKGjuvZGh6GD10pY" /><figcaption>Photo by <a href="https://unsplash.com/@hoianphotographer?utm_source=medium&amp;utm_medium=referral">Hoi An and Da Nang Photographer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>During my MSc in Human Resources Management, I spent a significant amount of time studying AI in HR — automation, people analytics, algorithmic decision-making, and ethics.</p><p>On paper, it all made sense.</p><p>AI promised efficiency, objectivity, and better workforce decisions. Case studies showed faster hiring, smarter talent insights, and reduced bias. The frameworks were logical, the tools impressive, and the future seemed clear.</p><p>But when I began seeing AI-enabled tools discussed — and gradually introduced — in real organisations, something felt different.</p><p>The technology wasn’t the hard part.</p><p><strong>People were.</strong></p><h3>Where AI Actually Starts to Struggle</h3><p>Across different organisational contexts, I noticed similar patterns emerging.</p><p>Managers were unsure how to trust insights they hadn’t “built” themselves. Employees were anxious about what AI meant for their roles, progression, and relevance. HR teams were expected to explain systems they had limited influence in shaping.</p><p>The resistance wasn’t loud or dramatic. It was subtle — hesitation, scepticism, quiet disengagement.</p><p>What struck me most was that these reactions had very little to do with the sophistication of the algorithm. They had everything to do with change, capability, and confidence.</p><h3>AI Doesn’t Replace HR Judgment — It Exposes It</h3><p>One of the biggest misconceptions I see is the idea that AI automatically makes HR processes “smarter”.</p><p>Workforce planning doesn’t become strategic just because a dashboard exists. Succession planning doesn’t improve simply because predictions are automated. Learning strategies don’t become future-ready because content is personalised by an algorithm.</p><p>These areas only become effective when HR can translate technology into human decisions — decisions leaders trust, employees understand, and organisations can stand behind.</p><p>In many ways, AI doesn’t replace judgment. It exposes gaps in it.</p><p>It forces organisations to confront uncomfortable questions:</p><ul><li>Do we really understand our critical roles and skills?</li><li>Are our talent decisions consistent and defensible?</li><li>Have we built the capability to interpret insights, not just receive them?</li></ul><h3>Where I Believe HR’s Future Influence Sits</h3><p>From what I’ve observed so far, HR’s future influence won’t come from being the owner of AI tools.</p><p>It will come from being the translator, challenger, and steward of how AI is used.</p><p>Not replacing judgment with AI — but helping organisations use AI:</p><ul><li><strong>Responsibly</strong>, with ethical and governance considerations</li><li><strong>Realistically</strong>, grounded in actual organisational readiness</li><li><strong>Humanely</strong>, with empathy for how change lands on people</li></ul><p>That requires strong foundations in workforce planning, succession, learning, and change adoption — not just technical understanding.</p><h3>Still Learning, Still Questioning</h3><p>I’m still learning, questioning, and unlearning a lot in this space.<br> And I suspect many HR professionals are too.</p><p>AI in HR doesn’t arrive as a finished solution. It arrives as a mirror — reflecting how prepared we truly are to lead change, not just implement tools.</p><p><strong>Curious — how are you seeing AI land in HR teams today?</strong><br>As an enabler?<br>A threat?<br>Or something that still feels unclear?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8145fe63c8a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>