<?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 Umesh Uttamchandani on Medium]]></title>
        <description><![CDATA[Stories by Umesh Uttamchandani on Medium]]></description>
        <link>https://medium.com/@umesh.u?source=rss-5de20c233305------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XivH-befNMl1N-3-Vt5EBg.png</url>
            <title>Stories by Umesh Uttamchandani on Medium</title>
            <link>https://medium.com/@umesh.u?source=rss-5de20c233305------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:35:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@umesh.u/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[The Reason Your Best People Keep Leaving Has Nothing to Do With HR]]></title>
            <link>https://medium.com/@umesh.u/the-reason-your-best-people-keep-leaving-has-nothing-to-do-with-hr-cacfaf5edb53?source=rss-5de20c233305------2</link>
            <guid isPermaLink="false">https://medium.com/p/cacfaf5edb53</guid>
            <category><![CDATA[talent-acquisition]]></category>
            <category><![CDATA[employee-retention]]></category>
            <category><![CDATA[talent-management]]></category>
            <category><![CDATA[human-resources]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Umesh Uttamchandani]]></dc:creator>
            <pubDate>Wed, 08 Jul 2026 04:31:04 GMT</pubDate>
            <atom:updated>2026-07-08T04:31:04.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*N_Lg1o78L87EDvKva3UY-w.png" /></figure><p><em>HR manages programmes. A talent system manages conditions. Most companies have not figured out the difference yet.</em></p><p><strong>TLDR</strong></p><p>HR as a function was designed to manage people processes. Hiring, compliance, payroll, performance reviews. What companies now need is different. A talent system is the integrated set of conditions that determines whether people join, stay, grow, and do their best work. It includes the city you are in, the office you offer, the career architecture you have built, and the management quality people experience every day. HR manages programmes. A talent system manages conditions. Most companies are still doing the first and wondering why the second is not happening.</p><p>I had a conversation in Ahmedabad two years ago that I keep coming back to.</p><p>A founder had just lost his third senior hire in six months. All three had joined with genuine enthusiasm. All three had left within a year. All three had cited career growth in their exit interviews. The founder had responded by redesigning the appraisal process and launching a learning and development programme.</p><p>I asked him one question. What does a five-year career path look like for someone who joins your company today?</p><p>He could not answer it.</p><p>Not because he had not thought about it. Because the organisation had not built the infrastructure for that path to exist. There was no architecture. There was a job description and a salary band and a manager who was figuring it out alongside everyone else.</p><p>The HR programmes were running. The talent system did not exist.</p><p>This is the distinction I want to talk about. Because I have watched it play out in enough cities, enough companies, and enough stages of growth to know that it is the most important thing most companies are not working on.</p><h3>What HR Was Built For</h3><p>Human resources as a function was designed for a specific era of work. An era where companies were relatively stable, teams were co-located, careers followed predictable paths, and the primary talent challenge was process efficiency. Hire the right people. Manage their performance. Keep them compliant. Pay them correctly. Repeat.</p><p>These are real and necessary things. They are not sufficient for what companies now face.</p><p>The talent market in India in 2026 looks nothing like the talent market HR was designed to manage. India is rewriting the rules of work at a pace most organisational systems were not built for. Companies are scaling across multiple cities simultaneously. Global capability centres are building teams in Pune and Ahmedabad and Coimbatore doing work that used to happen in London and Singapore. Younger workforces are evaluating employers on criteria that did not exist in the frameworks HR has been using.</p><p>The conventional talent management literature describes this challenge in terms of programmes. Better onboarding. More frequent feedback. Stronger learning and development. These are improvements to the HR function. They are not a talent system.</p><h3>What a Talent System Actually Is</h3><p>A talent system is the integrated set of decisions, infrastructure, and operating conditions that determine how a company attracts, develops, retains, and deploys its people.</p><p>It includes the physical environment they work in. The tools they use. The career architecture available to them. The management quality they experience. The city and location decisions that shape their daily life. The operating conditions that either make their work easier or harder every day.</p><p>HR manages programmes. A talent system manages conditions.</p><p>The difference is not semantic. Programmes are initiatives HR designs and delivers. Conditions are the sum of every decision the organisation makes about how work happens. From the city it chooses for a new office to how it structures career progression to the reliability of the infrastructure it provides.</p><p>A company can run excellent HR programmes inside poor conditions and still lose the people it needs to keep. The recognition programme cannot compensate for a career architecture with no visible path beyond eighteen months. The onboarding experience cannot offset a city choice that requires a two-hour commute. The learning and development budget cannot fix a management layer that is figuring out leadership at the same time it is managing delivery.</p><p>When I think about what we have built at DevX across Tier-2 cities, the argument becomes very clear. The companies winning the talent conversation in Ahmedabad, Surat, and Jaipur are not the ones with the best HR programmes. They are the ones that have thought carefully about the conditions they are creating and made the whole organisation responsible for those conditions, not just the HR team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVVPweVkx7a4r1Dv0sw2kg.png" /></figure><h3>What the Talent Market Is Actually Asking For</h3><p>Here is what I have observed across the cities we operate in, and it challenges assumptions that still shape how companies think about talent.</p><p>The talent in Tier-2 cities is not asking for less than the talent in Bengaluru or Mumbai. They are asking for the same quality of conditions. A workspace that signals the company is serious. A career architecture that makes the next three years legible. A management layer that has been developed rather than just promoted. An operating environment that reduces friction rather than creating it.</p><p>When a senior engineer in Pune declines an offer, it is rarely because the salary was insufficient. It is because something in the conditions signalled that the company had not thought carefully about what it was asking this person to commit to. The workspace. The team structure. The clarity of the role. The answer to what five years here actually looks like.</p><p>The exit interview rarely captures this accurately. People say career growth because it is the most acceptable reason to give. What they mean is that the conditions were not good enough to justify staying when something better appeared.</p><p>What employee experience actually means in the fullest sense is the sum of all these conditions operating together. That is what a talent system is responsible for creating. Not the HR function alone. The whole organisation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PU1QSrUdirEJNqJGd3XIcA.png" /></figure><h3>Why This Requires the Whole Organisation</h3><p>The reason most companies have not made the shift from HR programmes to talent systems is ownership.</p><p>HR owns the programmes. Nobody owns the conditions.</p><p>The conditions are distributed across every function. Finance decides the city based on cost. Operations decides the office based on lease terms. IT decides the tools based on security requirements. Management quality is determined by who gets promoted and how they are developed. Career architecture is built, or not built, depending on whether anyone has formally thought about what progression looks like.</p><p>Each of these decisions shapes the talent system. None of them are owned by HR. And because none of them are connected through a shared understanding of what conditions the organisation is trying to create, they produce a talent system by accident rather than by design.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mSWBPiu1CCcwwQ-AkdYZVA.png" /></figure><p>The organisations making the shift have answered one question every company should ask before opening a new office, hiring its next hundred people, or promoting its next layer of managers.</p><p>What are the conditions we are creating for the people who will work here. And is the whole organisation accountable for those conditions, or just the HR team.</p><p>Workplace experience is now a retention strategy rather than a culture initiative precisely because that question has started to be answered differently. The companies that understand retention as a whole-organisation responsibility are the ones building talent systems rather than HR programmes.</p><h3>The Shift That Is Already Happening</h3><p>The companies getting this right are not the largest or most sophisticated. They are the ones where leadership has accepted that talent is an operating condition, not a department output.</p><p>They measure different things. Not just attrition rates but the retention rate of people at the eighteen-month mark, where the gap between conditions promised and conditions delivered typically becomes decisive. Not just engagement scores but whether the career architecture they have built is legible to the people inside it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IRG5MtfhuN6EU2KvGheWGA.png" /></figure><p>They own it differently. The talent conversation sits at the leadership table, not just in the HR meeting. City decisions, office decisions, management development decisions, and career architecture decisions are all understood as talent decisions.</p><p>And they ask the question I asked that founder in Ahmedabad two years ago. What does a five-year career path look like for someone who joins your company today.</p><p>The companies that can answer it clearly are the ones building talent systems. The ones that cannot are still running HR programmes and wondering why the conditions are not improving.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cacfaf5edb53" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>